Home » HP Manuals » Servers » HP ProLiant ML350p » Manual Viewer

HP ProLiant ML350p HP Insight Server Migration Software for ProLiant User Guid - Page 93

Virtual-to-ProLiant (V2P) migrations, Preparing for a V2P migration, Source physical machine

Add to My Manuals
Save this manual to your list of manuals

Page 93 highlights

[boot loader] default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS timeout=30 [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /sos /bootlog /noexecute=optout /fastdetect multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="HP SMP Preserved: Windows Server 2003, Enterprise" /userva=3030 /3gb /noexecute=optout /fastdetect Virtual-to-ProLiant (V2P) migrations A virtual-to-ProLiant (V2P) migration enables migration of a virtual machine guest to a physical ProLiant server. Preparing for a V2P migration The following sections list prerequisites for a V2P migration. If you use a firewall, see the Configuring SMP with a firewall section in this guide. Source physical machine prerequisites CAUTION: If the SMP application station shuts down or fails during any migration, then the migration being performed fails. Availability of application station during complete migration cycle is required for successful migration. • Because the SMP application does not migrate virtual machine guests with the following disk types, verify that these disk types do not exist on the source virtual machine. The following table details the prerequisites for the source virtual machine. Table 5-3 Unsupported disk types Virtualization technology Disk type Microsoft Virtual Server 2005 VMware ESX VMware ESX VMware Server Linked disk Differencing disk Append disk Undoable disk Nonpersistent disk Physical (RAW) disk • A valid network connection must exist between the source and destination server. • The source server must contain an active boot partition to be migrated. • To prevent interrupting the migration process, complete any pending reboots and software installations on the source machine before initiating a migration. • Temporarily disable any antivirus software autoscans on the source machine to prevent interrupting the migration process. Re-enable the antivirus software after the migration. • Verify that the disks are not corrupted by running CHKDSK and disk defragmenter on the source physical machine before initiating a V2P migration. Verify that all hard drives on the source physical machine are correctly initialized (disk signature written). If Windows 2000 or Windows Server 2003 is installed, then verify initialization by selecting Computer Management→ Disk Management. Verify that the latest hard drive configuration is saved. • Verify that all partitions on the source physical machine have a valid file system and are in a healthy state. Virtual-to-ProLiant (V2P) migrations 93

Section	Page
HP Insight Server Migration software for ProLiant	1
Table of Contents	3
About this document	11
Document organization	11
New and changed information in this edition	11
Related documents	11
1 Introduction	13
HP Insight Server Migration software for ProLiant	13
SMP benefits	13
SMP platform support	13
SMP components	13
Planning a migration strategy	13
Upgrading to SMP from SMP or P2P	13
Downgrading to SMP or P2P from SMP	14
Hardware and operating system support	14
Configuration planning	14
License verification	14
Schedule preparation	15
Memory and CPU resources on the application station	15
Critical or hardware-dependent application preparation	15
Virtual machine guest tools	15
Domain controllers	15
Microsoft Small Business Server	16
Firewalls	16
Antivirus software	17
Dual-boot	17
Resizing NTFS volumes for Windows migration	17
File system selection for a Linux source server	18
ProLiant Support Pack	18
Linux Support Pack	18
Related HP products	18
2 SMP installation and configuration requirements	19
HP SMP application station and HP SIM Central Management Server (CMS)	19
Windows source servers	20
Linux source servers	20
Physical destination servers	20
Virtual machine hosts	20
Installing SMP on the application station	21
Changing the default SMP application station service port number	24
Accessing the product documentation on the SMP Boot CD	24
3 Deploying SMP Agents	27
Deploying SMP Source Agents	27
SMP Agents	27
SMP supported Windows migrations	28
Agent-less hypervisors	28
Agent-based hypervisors	28
SMP supported Linux migrations	28
Operating system	28
Linux operating system requirements	28
SMP Boot CDs	29
Using the HP SIM CMS to deploy SMP Agent	29
Deploying SMP Agent through the HP SIM CMS menu if SMP and HP SIM 5.3 are installed	29
Deploying SMP Agent through the HP SIM CMS Quick Launch feature	30
Using the application station to deploy SMP Agent	30
Deploying SMP Agent using the Deploy Agent tab of the wizard on the application station	30
Deploying SMP Source Agent directly from the Migration Wizard on the application station	31
Manually running SMP Source Agent on the source server	31
Deploying Windows SMP Source Agent locally on the source server	31
Deploying Linux SMP Source Agent locally on the source server	32
Installing SMP Source Agent on a Windows 2008 Server	34
Restarting the SMP Agent	35
Booting the destination server for P2P, V2P, and X2V (agent-less) migrations	35
Manually booting a physical destination server using the SMP Boot CD for P2P and V2P	35
Booting a destination server using the SMP Migration Wizard	35
Manually creating and booting a virtual machine destination server for P2V and V2V (agent-less)	36
Manually creating and booting a virtual machine for SMP	36
Prerequisites for manually creating and booting a destination virtual machine	36
Hyper-V migration	36
VMware ESX migration	36
HP integrated Citrix XenServer migration	37
Automatically creating and booting a virtual destination server using the SMP Migration Wizard for P2V or V2V	37
Configure Boot CD to launch destination agent	37
SMP Overview screen	41
4 Licensing SMP	43
Licensing SMP	43
SMP licensing keys	43
Licensing requirements	43
Licensing options	43
Adding licenses	44
SMP 2.x and P2P license conversion	44
Migrating P2P licenses using License Migration Tool	45
Migrating SMP 2.x licenses using License Migration Tool	45
5 Using SMP for server migration	47
Concurrent and queued migrations	47
Migration Wizard page	48
Physical-to-ProLiant (P2P) migrations for Windows	49
Preparing for a P2P migration	49
Source physical machine prerequisites	58
SMP application station prerequisites	58
Destination physical machine prerequisites	58
Source physical machine prerequisites	58
SMP application station prerequisites	58
Destination physical machine prerequisites	58
Performing a P2P migration	58
P2P post-migration tasks	66
Physical-to-virtual (P2V) migrations	67
Preparing for a P2V migration	67
Source physical machine prerequisites	67
SMP application station prerequisites	67
Destination virtual machine host or virtual machine prerequisites	68
Performing a P2V migration	68
P2V post-migration tasks	79
Virtual-to-virtual (V2V) migrations	80
Preparing for a V2V migration	80
Source physical machine prerequisites	81
SMP application station prerequisites	81
Destination virtual machine host or virtual machine prerequisites	82
Performing a V2V migration	82
V2V post-migration tasks	92
Virtual-to-ProLiant (V2P) migrations	93
Preparing for a V2P migration	93
Source physical machine prerequisites	93
SMP application station prerequisites	94
Destination physical machine prerequisites	94
Performing a V2P migration	94
V2P post-migration tasks	102
SAN migrations	103
SMP application integration to HP SIM	104
HP SIM integration	104
Launching SMP migration through HP SIM	106
Quick Launch details	109
Performing post-migration steps for Windows 2000, Windows 2003, and Windows 2008	110
Windows 2000 post-migration steps	110
Windows 2003 and Windows 2008 post-migration steps	113
6 Viewing migration logs	117
Viewing migration logs	117
7 Uploading drivers	119
8 Troubleshooting	121
Troubleshooting	121
Installation	121
When launching the SMP wizard immediately after installation, the message Unable to communicate with the SMP service displays on the wizard page	121
SMP installation displays The SMP cannot be installed on a machine with an empty or invalid credentials error	121
SMP related menus missing after installing HP SIM on SMP	121
SMP-related menus missing	121
Support for older versions of stand-alone P2P application	121
Configuration	122
Ports required for SMP are not available	122
For Microsoft Windows Server 2003 systems	122
For Windows 2000 Server systems	122
Configuring SMP with a firewall	122
Microsoft DNS Server might not map the host name to DHCP-generated IP addresses	123
Source preparation	123
Corrective action is required before migrating some preinstalled HP Microsoft Windows Server 2003 operating systems	123
Corrective action is required for some source servers with HP iLO Management Channel Interface Drivers	123
Source server identification fails	124
Deploy Agent task to Windows fails	124
SMP Agent deployment fails	125
Linux SMP Source Agent deployment fails	125
SMP Source Agent deployment fails remotely from a Windows 2003 Application Station	125
SMP Source Agent installation takes longer than usual	126
Destination preparation	126
Destination server displays a blank screen when SMP Boot CD is used to boot the server	126
Destination server identification fails	126
Application station fails to connect to the destination server	126
IP address configuration fails on a manually booted virtual machine in Hyper-V for a P2V or a V2V migration	126
Kernel Panic when booting a virtual machine to the SMP Virtual Boot CD	126
Manual boot of HP integrated Citrix XenServer fails	126
Mouse does not work on a virtual machine booted with the SMP VM Boot CD for virtual machines	127
Primary array controller does not have logical drives defined	127
Primary controller configured in the system does not have drives attached	127
Primary controller in system is not supported by this version of SMP	127
SMP Boot CD might stop responding when exiting the Array Configuration Utility	127
Some storage volumes on the destination server are not available for selection	127
Static IP address cannot be assigned on the destination server while booting using the Boot CD	128
Supported storage controllers display Unknown on the Boot CD	128
Auto booting destination server using iLO fails	128
SMP might not detect virtual machines on mapped network drives	128
Deploy Agent task to Windows fails	128
Windows SMP Agent deployment fails	128
Destination server boots from the SMP boot CD on a manual boot	129
Migration process	129
Drivers cannot be installed or injected onto boot disk	129
Large volumes fail with server thread error	129
For Windows 2003	129
For Windows 2000	130
Migration fails if certain Update Rollup versions exist	130
Migration fails to terminate if source server is shut down	130
NTFS partitions cannot be resized from a Windows 2008 application station	130
NTFS resize error message	130
SMP migration fails during the disk cloning phase	130
SMP cannot perform V2V migrations on virtual machine guests with certain disk types	131
Starting a new migration after a current migration is stopped	131
Unrecoverable sector-read errors on the source server hard drive are not supported and fail a Windows P2P or P2V migration	131
Source agent fails to launch when source server reboots in SMP Agent Mode	131
Error during data copy of Linux migration	132
Destination server reboots continuously with a blue screen	132
SAN-connected destination server displays blue screen	132
Post-migration	132
A PSP installation after an X2P migration of Windows 2000 to a server with the Emulex LPe1105-HP 4Gb FC HBA might cause a blue screen on the destination server	132
Error message appears during P2P installation	133
Migration does not start after confirmation. The event log continuously displays Operation Migration waiting for connection to source	133
AdapterMismatch message appears	133
Destination server mouse and keyboard do not work	134
DNS error appears in the destination server after migration of domain controller	134
Drive letters are not the same in the migrated virtual machine guest after migration	134
Drives do not display on the migrated operating system	134
Mouse and keyboard do not work after migrating a Hyper-V virtual machine to a ProLiant server	134
Static IP address cannot be assigned on the destination server after migration	134
Virtual machine hosts Integrated Components do not install on the destination virtual machine following SMP migration	135
Yellow bang (!) appears on the NIC adapter in Device Manager on the migrated virtual machine	135
Uninstallation	135
Unable to uninstall an older version of the SMP application	135
Uninstalling SMP using the uninstaller shortcut menu	135
9 HP support and contact information	137
HP Software Technical Support and Update Service	137
Support and information	138
HP contact information	138
A Portable Images Network Tool (PINT)	139
Glossary	141

Match case Limit results 1 per page

[boot loader]

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

timeout=30

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=

”

Windows Server 2003, Enterprise

”

/sos /bootlog

/noexecute=optout /fastdetect

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=

”

HP SMP Preserved: Windows Server 2003, Enterprise

”

/userva=3030 /3gb /noexecute=optout /fastdetect

Virtual-to-ProLiant (V2P) migrations

A virtual-to-ProLiant (V2P) migration enables migration of a virtual machine guest to a physical ProLiant

server.

Preparing for a V2P migration

The following sections list prerequisites for a V2P migration.

If you use a firewall, see the

Configuring SMP with a firewall

section in this guide.

Source physical machine prerequisites

CAUTION:

If the SMP application station shuts down or fails during any migration, then the migration

being performed fails. Availability of application station during complete migration cycle is required for

successful migration.

•

Because the SMP application does not migrate virtual machine guests with the following disk types,

verify that these disk types do not exist on the source virtual machine.

The following table details the prerequisites for the source virtual machine.

Table 5-3 Unsupported disk types

Disk type

Virtualization technology

Linked disk

Microsoft Virtual Server 2005

Differencing disk

Append disk

VMware ESX

Undoable disk

Nonpersistent disk

Physical (RAW) disk

VMware ESX

VMware Server

•

A valid network connection must exist between the source and destination server.

•

The source server must contain an active boot partition to be migrated.

•

To prevent interrupting the migration process, complete any pending reboots and software installations

on the source machine before initiating a migration.

•

Temporarily disable any antivirus software autoscans on the source machine to prevent interrupting the

migration process. Re-enable the antivirus software after the migration.

•

Verify that the disks are not corrupted by running CHKDSK and disk defragmenter on the source physical

machine before initiating a V2P migration.

Verify that all hard drives on the source physical machine are correctly initialized (disk signature written).

If Windows 2000 or Windows Server 2003 is installed, then verify initialization by selecting

Computer

Management

→

Disk Management.

Verify that the latest hard drive configuration is saved.

•

Verify that all partitions on the source physical machine have a valid file system and are in a healthy

state.

Virtual-to-ProLiant (V2P) migrations