HP Virtual Connect Enterprise Manager Software manual Uninstalling guest tools, Deploying Agents

Page 23

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

•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 may 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.

•To perform SAN Linux migration, destination server specific Fiber Channel HBA firmware files must be 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 using a QLogic HBA, you need to 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.

Uninstalling guest tools

Before starting a migration, you must uninstall 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 starting 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 file1

virtual machine destination

Insight Control server migration Virtual Machine Boot CD

 

ISO file

1

 

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 be running 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 deploying the migration Agent. Failure to do so can result in improper IP address assignment and can disrupt the migration.

Uninstalling guest tools

23

Page 22 Page 24
Image 23
Page 22 Page 24
Contents HP Insight Control Server Migration 7.0 User Guide Legal Notices Contents Post-migration tasks IV Troubleshooting and supportMigrating the servers ISO Contents Contents Glossary Index Support and other resourcesApplying old server migration standalone licenses Part I Overview and concepts Related products Installing and configuring server migration softwareServer migration introduction OverviewProduct Description Overview of migrating a server Migration checklistServer migration concepts Server migration componentsMigration screen HP Insight Control server migration software tabsServer migration concepts Part II Pre-migration tasks Verifying application station system requirements Preparing hardware for migrationVerifying hardware and operating system support Planning the migration Resizing Linux file systems Disabling firewalls Preparing software for migrationVerifying licenses for software to be migrated Migration Security Generating static or dynamic certificates Installing ProLiant Support Packs Disabling antivirus software Part III Migration Preparing a Microsoft Hyper-V source server Preparing the source server and deploying the Source AgentVerifying Windows source server requirements Verifying Linux source server requirementsDeploying Agents Uninstalling guest toolsChoosing server migration Agents Deploying server migration AgentsNavigate to server migration Source Agent Server migration agent install dialog Navigate to server migration Source Agent Linux Source Agent screen Virtual machine hosts PrerequisitesLinux destination size requirement Physical destination serversBooting 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 migrationPreparing for a Linux server migration SAN migrations in Windows Starting the migration wizard Launching server migrations using the Deploy menuVerify Source Physical server Quick Launch Launching server migrations using Quick LaunchAvailable operations X2V post-migration tasks Windows Installing ProLiant Support Packs after migrationPost-migration tasks X2P post-migration tasks WindowsX2P post-migration tasks Linux Edit the boot.ini file to activate a graphical boot processValidating Linux migrations X2V post-migration tasks LinuxViewing migration logs Validating the migrationPost-migration tasks Part IV Troubleshooting and support Server migration wizard hangs TroubleshootingUser interface Source preparationMigration Agent deployment fails Source server identification failsSuggestion action Linux Source Agent window does not appear on Rhel 64-bitDestination server identification fails Destination preparationIncorrect LUN size detected in of the migration wizard Suggested action CD ISO Auto booting destination physical server fails Manually migrate these disks after a successful migration Migration process Drivers cannot be installed or injected onto boot diskLarge volumes fail with server thread error Java.lang.OutOfMemoryError Java heap space Migration hangs if source server is shut down Ntfs resize error messageReiserFS volumes are blocked for Linux migration Migration fails during the disk cloning phase Error during data copy of Linux migration SAN-connected destination server displays blue screen Destination server boots with an invalid IP addressPerform one of the following Post-migrationHidusb.sys Hidkbd.sys Mouhid.sys Suggested action Drives do not appear on the migrated operating system Server is unresponsive during PSP installation Destination virtual machine fail to boot after X2V migrationReboot the server and then reinstall PSP manually Information to collect before contacting HP How to contact HPSupport and other resources Related information HP authorized resellersDocumentation feedback Related documentation Typographic conventionsTIP Applying old server migration standalone licenses Basic hardware design of a three-node duster Pre-migration consideration steps for clustersPost migration considerations and steps Performing the migrationPost migration considerations and steps Glossary Index Index SIM Websites
Top Page Image Contents