HP PART NUMBER: 461487-401A manual Manually creating and booting a virtual destination server

Page 32

Booting a physical destination server automatically by using the migration wizard

1.Identify the source server and select volumes to migrate in steps 1 and 2 in the server migration wizard.

2.In step 3 of the P2P or V2P migration wizard, select Auto Boot - Let server migration boot the destination server.

3.Enter the iLO IP address and iLO credentials.

4.Enter the static IP address, subnet mask, and default gateway (Optional). If the network has a gateway, enter it here to ensure connectivity. Optionally, you can also select the Duplex Settings.

5.Click Next.

6.To view the boot progress, click Launch iLO, and then log on to the iLO remote console.

iLO boot prerequisites

You must meet the following requirements to use the feature of booting from iLO:

The iLO user credentials provided must have Virtual Power and Reset and Virtual Media access applied.

The browser must be configured to support HTTP 1.1. To add this support:

1.On your web browser, open Internet Options, and then click the Advanced tab.

2.As appropriate, select Use HTTP 1.1 and Use HTTP 1.1 through proxy connections.

An iLO Advanced license must be applied to the destination server iLO.

At least 300 MB of free space must exist on the application station for each iLO boot. This free space should exist on the partition on which Insight Control server migration is installed. This space is recovered after the migration is complete or the boot job times out.

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

If the migration is not started within 2 hours of the server being powered up through iLO, the server migration will time out and power down the destination server.

Manually creating and booting a virtual destination server

Prerequisites for manually creating and booting a destination virtual machine

This section lists the prerequisites for manually creating a virtual machine for different migrations.

To manually create and boot a destination virtual machine, you must create the virtual machine with the prerequisites specified, and then attach the Insight Control server migration Virtual Machine Boot CD ISO to the virtual machine.

The following sections list the special steps required to prepare virtual machines for booting to the Insight Control server migration Virtual Machine Boot CD ISO.

Prerequisites for booting a virtual machine in Microsoft Hyper-V

Make sure that the following parameters are met:

The virtual machine does not have more than three disks attached.

The virtual machine has at least 1024 MB of memory.

The network adapter is a legacy network adapter.

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

The virtual disks that you created are attached to an IDE controller.

32 Preparing the destination server and deploying the destination agent

Image 32
Contents HP Insight Control Server Migration 7.2 User Guide Legal Notices Contents Postmigration tasks IV Troubleshooting and supportMigrating the servers Contents CD ISO Contents Support and other resources Glossary Index Part I Overview and concepts Installing and configuring server migration software Server migration introductionOverview Related productsRight configuration Migration checklist Server migration conceptsServer migration components Overview of migrating a serverHP Insight Control server migration software tabs Migration screenHP Insight Control server migration software tabs Part II Premigration tasks Verifying system requirements for the application station Preparing hardware for migrationVerifying hardware and operating system support Planning the migration Resizing Linux file systems Preparing software for migration Verifying licenses for software to be migratedMigration security Disabling firewallsInstalling ProLiant Support Packs Installing Service Pack for ProLiantDisabling antivirus software Generating static or dynamic certificatesPreparing software for migration Part III Migration Preparing the source server and deploying the Source Agent Verifying Windows source server requirementsVerifying Linux source server requirements Preparing a Microsoft Hyper-V source serverRemoving guest tools Choosing server migration AgentsDeploying 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 Prerequisites Linux destination size requirementPhysical destination servers Virtual machine hostsBooting the destination server Manually creating and booting a virtual destination server ILO boot prerequisitesPrerequisites for VMware ESX migration Page Migrating the servers Minimum source server prerequisites for all migrationsPreparing for a Windows server migration If you use a firewall, see Disabling firewallsPreparing for a Linux server migration Source virtual machine prerequisitesSource physical server prerequisites SAN migrations in Windows Launching server migration by using the Deploy menu Starting the migration wizardLaunching server migration by using Quick Launch Identify the source serverQuick Launch Starting the migration wizard Installing ProLiant Support Packs after migration Installing Service Pack for ProLiant after migrationPostmigration tasks X2P postmigration tasks WindowsEdit the boot.ini file to activate a graphical boot process X2V postmigration tasks WindowsX2P postmigration tasks Linux X2V postmigration tasks LinuxViewing migration logs Validating the migrationValidating Linux migrations Validating Windows migrationsPart IV Troubleshooting and support Server migration wizard hangs TroubleshootingUser interface HP SIM Source preparation Source server identification failsMigration Agent deployment fails Linux Source Agent window does not appear on Rhel 64-bitIncorrect LUN size is detected in of the migration wizard Perform any one of the following on the source serverDestination server identification fails Unable to boot Windows due to unsigned or corrupt driversDestination preparation Migration might appear If expected volumes do not appear, try one of the following Automatic booting of the destination physical server fails Suggested action Migration process Drivers cannot be installed or injected onto a boot diskLarge volumes fail with a server thread error Migration hangs if the source server is shut down 2011/03/14 141934 The job failedNtfs resize error message appears ReiserFS volumes are blocked for Linux migrationMigration fails during the disk cloning phase Error occurs during data copy of Linux migration SAN-connected destination server displays a blue screenDestination server boots with an invalid IP address HP Smart Array B320i controller name is not displayedLinux migration to servers with iSCSI storage fails to boot PostmigrationHidusb.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 How to contact HP Subscription serviceSupport and other resources Information to collect before contacting HPHP authorized resellers Related informationDocuments WebsitesTypographic conventions Related documentationTIP Documentation feedback Applying old server migration standalone licenses Premigration consideration steps for clusters Basic hardware design of a three-node dusterPerforming the migration Post migration considerations and stepsPost migration considerations and steps Page Glossary Index Page SPP Postmigration tasks Yellow bang ! appears on NIC adapter