HP PART NUMBER: 461487-401A manual Removing guest tools, Choosing server migration Agents

Page 25

•To enable the display of the Linux source server agent in 64–bit RHEL, installation of the X.Org X11 libXtst runtime library libXtst-1.0.99.2-3.el6.i686.rpm.

•The 32-bit version of glibc 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.

•For SAN Linux migration, destination server–specific Fibre Channel HBA firmware files installed on the source server. These firmware files are available on the installation media of the Linux OS. For example, if you plan to migrate to a destination server with SAN storage by using a QLogic HBA, you must install qlogic-firmware-<version>.noarch.rpmon SLES OS or ql2xxx-firmware-<version>.noarch.rpmon RHEL OS. For information on the firmware files required and the installation instructions, see the respective HBA documentation.

•If an IPv6 DHCP server running on the network and if the source is a SLES OS running DHCP client for IPv6, then the source may not boot in the safe migration mode. To resolve this issue, you must disable IPv6 DHCP on all the NIC interfaces in the source server prior to migration and restart the server manually after the migration.

Removing guest tools

Before you start a migration, you must remove guest tools if you are migrating a source virtual machine. Guest tools are not applicable on the destination server and might cause issues with the normal functioning of the network adapters, keyboard, and mouse. After the migration is completed, you can reinstall the guest tools on the source virtual machine.

Choosing server migration Agents

Deploy and run migration Agents on the source server and the destination server before you start a server migration.

Table 2 Server and migration Agent types

Server

Migration Agent

Physical Windows source server or source virtual machine

Windows server migration Source Agent

Physical Linux source server or source virtual machine

Linux server migration Source Agent

Physical destination server

Insight Control server migration ProLiant Boot CD ISO file

 

1

Virtual machine destination

Insight Control server migration Virtual Machine Boot CD

 

ISO file

1HP ProLiant Gen8 servers must be booted automatically from the server migration wizard. When HP ProLiant Gen8 servers are used as destination servers, the manual boot option of the Insight Control server migration ProLiant Boot CD is not supported.

The Source Agent does not run as a service on the source server, and you must apply the agent for each migration. The agent will no longer run on the source after migration.

Deploying server migration Agents

Deploying Agents

If you have administrative rights to connect to the source server, you can deploy a migration Agent.

NOTE: Shut down any running hypervisor or virtual machines on the source server before you deploy the migration Agent. Failure to do so can result in improper IP address assignment and can disrupt the migration.

Removing guest tools 25

Page 24 Page 26
Image 25
Page 24 Page 26
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
Top Page Image Contents