HP PART NUMBER: 461487-401A manual Preparing for a Linux server migration

Page 37

Comply with all minimum prerequisites as listed in “Minimum source server prerequisites for all migrations” (page 35).

During migration, the migration Agent initiates an operating system reboot on the source server. Verify that the operating system is on the first boot order. If not, manually change the boot order:

For Windows Server 2003, edit the [system drive]\boot.ini file or use the bootcfg.exe tool.

For Windows Server 2008 or later, use the bcdedit.exe tool.

Source virtual machine prerequisites

If you are migrating from a source virtual machine, verify that it complies with all minimum prerequisites as listed in “Minimum source server prerequisites for all migrations” (page 35).

Destination physical server prerequisites

If you are migrating to a destination physical server, verify that the following prerequisites are completed:

Configure the primary storage controller with drives attached.

Connect and configure the NIC cards.

Manually boot the destination server with the Insight Control server migration ProLiant Boot CD ISO and make sure that it is running the migration Agent.

Select the Auto Boot option in step 3 of the migration wizard to automatically boot the desalination server with Insight Control server migration ProLiant Boot CD ISO.

NOTE: For Gen8 servers, Manual Boot option is not supported.

Destination virtual machine host or virtual machine prerequisites

If you are migrating to a destination virtual machine, verify that the following prerequisites are completed:

Select one of the following:

Let Insight Control server migration create the virtual machine automatically, which will automatically create and boot the destination virtual machine by using the server migration Virtual Machine Boot CD ISO.

Create the virtual machine manually, and then boot the virtual machine manually by using the server migration Virtual Machine Boot CD ISO.

Verify that the destination virtual machine host has sufficient system resources, including processor, memory, and disk space to host the migrated virtual machine guest.

Temporarily disable any antivirus software auto-scans on the destination virtual machine host to prevent interrupting the migration process. Re-enable the antivirus software after the migration.

Preparing for a Linux server migration

The following sections list prerequisites for a Linux server migration.

If a firewall is running on the source server and Source Agent deployment is required, see “Disabling firewalls” (page 20).

Make sure that the SSH port is open when a firewall is in use, or the server migration Source Agent might not be deployed successfully.

Prerequisites 37

Image 37
Contents HP Insight Control Server Migration 7.2 User Guide Legal Notices Contents Migrating the servers IV Troubleshooting and supportPostmigration 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 Verifying hardware and operating system support Preparing hardware for migrationVerifying 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 User interface TroubleshootingServer 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 wizardDestination preparation Unable to boot Windows due to unsigned or corrupt driversDestination 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 Large volumes fail with a server thread error Drivers cannot be installed or injected onto a boot diskMigration 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