HP PART NUMBER: 461487-401A manual Prerequisites for VMware ESX migration

Page 33

The boot virtual disk is connected to the 0th channel of the first IDE controller.

The Insight Control server migration Virtual Machine Boot CD ISO is attached to the destination virtual machine.

Prerequisites for VMware ESX migration

Make sure that the following parameters are met:

The virtual machine has at least 1024 MB of memory.

You have created the virtual machine by selecting the correct operating system being migrated.

You have created the virtual machine with at least one flexible network adapter.

The network adapter is connected to a virtual network switch that is connected to an external network.

The Insight Control server migration Virtual Machine Boot CD ISO is attached to a virtual CD-ROM device.

You have discovered and configured VMware vCenter Server settings through Systems Insight Manager. For more information, see HP Insight Management Installation and Configuration Guide.

Manually creating and booting a virtual machine destination server for X2V

1.Access the management console for the virtual machine host, as provided by VMware ESX or Microsoft Hyper-V.

2.Create a new virtual machine that has sufficient disk space for migration.

3.Boot the virtual machine to the Insight Control server migration Virtual Machine Boot CD ISO file. You can find the Virtual Machine Boot CD ISO file at <Insight Control server migration Installation Folder>\Agents\SMP\smpbootcd-v-[version #].iso.

4.After the destination server or virtual machine is booted to the proper Boot CD ISO file, use the Boot CD ISO application to configure the destination server and launch the destination agent. From the Boot CD ISO application, click Help for instructions.

Automatically creating and booting a virtual destination server

To automatically create and boot a destination virtual machine by using the migration wizard:

1.Run the migration wizard and complete steps 1 and 2 (select the source server and select the volumes to migrate). In step 3 of the P2V and V2V migration wizard, identify the VM host and then select the appropriate virtualization layer.

2.Select Auto Boot — Automatically have VM created through server migration wizard.

3.Enter the logon credentials for the virtual machine host (for Microsoft Hyper-V host only).

4.Configure the destination server networking by entering the static IP address, subnet mask, and default gateway (optional). If the network has a gateway, enter it here to ensure connectivity. When you are finished, click Next. Optionally, you can also select the Duplex Settings.

5.Insight Control server migration verifies that the virtual machine host is licensed and then moves to the next step, where you must enter the name of the virtual machine configuration and map the source disks to the destination disks. When you are finished, click Next.

The Insight Control server migration application then connects to the virtual machine host, creates the virtual machine, and boots the virtual machine by using the Insight Control server migration Virtual Machine Boot CD ISO.

After the Boot CD agent is launched on the provided IP address, the application station connects to the agent on the Boot CD, and the next page of the wizard appears.

Booting the destination server

33

Image 33
Contents HP Insight Control Server Migration 7.2 User Guide Legal Notices Contents IV Troubleshooting and support Migrating the serversPostmigration tasks Contents CD ISO Contents Support and other resources Glossary Index Part I Overview and concepts Server migration introduction Installing and configuring server migration softwareOverview Related productsRight configuration Server migration concepts Migration checklistServer migration components Overview of migrating a serverMigration screen HP Insight Control server migration software tabsHP Insight Control server migration software tabs Part II Premigration tasks Preparing hardware for migration Verifying hardware and operating system supportVerifying system requirements for the application station Planning the migration Resizing Linux file systems Verifying licenses for software to be migrated Preparing software for migrationMigration security Disabling firewallsInstalling Service Pack for ProLiant Installing ProLiant Support PacksDisabling antivirus software Generating static or dynamic certificatesPreparing software for migration Part III Migration Verifying Windows source server requirements Preparing the source server and deploying the Source AgentVerifying Linux source server requirements Preparing a Microsoft Hyper-V source serverChoosing server migration Agents Removing guest toolsDeploying server migration Agents Deploying AgentsNavigate to server migration Source Agent Server migration agent install screen Navigate to server migration Source Agent Linux Source Agent screen Linux destination size requirement PrerequisitesPhysical destination servers Virtual machine hostsBooting the destination server ILO boot prerequisites Manually creating and booting a virtual destination serverPrerequisites for VMware ESX migration Page Minimum source server prerequisites for all migrations Migrating the serversIf you use a firewall, see Disabling firewalls Preparing for a Windows server migrationSource virtual machine prerequisites Preparing for a Linux server migrationSource physical server prerequisites SAN migrations in Windows Starting the migration wizard Launching server migration by using the Deploy menuIdentify the source server Launching server migration by using Quick LaunchQuick Launch Starting the migration wizard Installing Service Pack for ProLiant after migration Installing ProLiant Support Packs after migrationPostmigration tasks X2P postmigration tasks WindowsX2V postmigration tasks Windows Edit the boot.ini file to activate a graphical boot processX2V postmigration tasks Linux X2P postmigration tasks LinuxValidating the migration Viewing migration logsValidating Linux migrations Validating Windows migrationsPart IV Troubleshooting and support Troubleshooting User interfaceServer migration wizard hangs HP SIM Source server identification fails Source preparationLinux Source Agent window does not appear on Rhel 64-bit Migration Agent deployment failsPerform any one of the following on the source server Incorrect LUN size is detected in of the migration wizardUnable to boot Windows due to unsigned or corrupt drivers Destination preparationDestination server identification fails Migration might appear If expected volumes do not appear, try one of the following Automatic booting of the destination physical server fails Suggested action Drivers cannot be installed or injected onto a boot disk Large volumes fail with a server thread errorMigration process 2011/03/14 141934 The job failed Migration hangs if the source server is shut downReiserFS volumes are blocked for Linux migration Ntfs resize error message appearsMigration fails during the disk cloning phase SAN-connected destination server displays a blue screen Error occurs during data copy of Linux migrationHP Smart Array B320i controller name is not displayed Destination server boots with an invalid IP addressPostmigration Linux migration to servers with iSCSI storage fails to bootHidusb.sys Hidkbd.sys Mouhid.sys Suggested action Drives do not appear on the migrated operating system Guest OS ID guest name is not valid Server is unresponsive during PSP installation Multiboot kernel must be loaded before modules Suggested action Subscription service How to contact HPSupport and other resources Information to collect before contacting HPRelated information HP authorized resellersDocuments WebsitesRelated documentation Typographic conventionsTIP Documentation feedback Applying old server migration standalone licenses Basic hardware design of a three-node duster Premigration consideration steps for clustersPost migration considerations and steps Performing the migrationPost migration considerations and steps Page Glossary Index Page SPP Postmigration tasks Yellow bang ! appears on NIC adapter