HP PART NUMBER: 461487-401A manual Source physical server prerequisites

Page 38

Verify compliance with all minimum prerequisites. For more information, see “Minimum source server prerequisites for all migrations” (page 35).

Make sure that the 32–bit version of glibc is installed. The 32–bit version of glibc is required to run the Linux server migration Source Agent. The library is present by default on 32–bit Linux installations, but you might need to install it manually on 64–bit Linux systems. The 32–bit version of glibc is available on your Linux OS installation CD/DVD.

If X–Windows is configured on the source server, make sure that the 32–bit version of the libXtst runtime library is installed.

Source physical server prerequisites

If you are migrating from a source physical server, verify that the following prerequisites are completed:

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

Make sure that PermitRootLogin and PasswordAuthentication are set to Yes in the

/etc/ssh/sshd_config file and that the sshd service is running.

Make sure that GRUB Boot Loader is the primary boot loader on the source server.

Source virtual machine prerequisites

If you are migrating from a source virtual machine, verify that the following prerequisites are completed:

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

Make sure that PermitRootLogin and PasswordAuthentication are set to Yes in the

/etc/ssh/sshd_config file and that the sshd service is running.

Make sure that GRUB Boot Loader is the primary boot loader on the source server.

Remove guest tools.

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.

38 Migrating the servers

Image 38
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 Overview Installing and configuring server migration softwareServer migration introduction Related productsRight configuration Server migration components Migration checklistServer migration concepts 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 Migration security Preparing software for migrationVerifying licenses for software to be migrated Disabling firewallsDisabling antivirus software Installing ProLiant Support PacksInstalling Service Pack for ProLiant Generating static or dynamic certificatesPreparing software for migration Part III Migration Verifying Linux source server requirements Preparing the source server and deploying the Source AgentVerifying Windows source server requirements Preparing a Microsoft Hyper-V source serverDeploying server migration Agents Removing guest toolsChoosing 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 Physical destination servers PrerequisitesLinux destination size requirement 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 Postmigration tasks Installing ProLiant Support Packs after migrationInstalling Service Pack for ProLiant after migration X2P postmigration tasks WindowsEdit the boot.ini file to activate a graphical boot process X2V postmigration tasks WindowsX2P postmigration tasks Linux X2V postmigration tasks LinuxValidating Linux migrations Viewing migration logsValidating the migration 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 Support and other resources How to contact HPSubscription service Information to collect before contacting HPDocuments HP authorized resellersRelated information 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