HP Virtual Connect Enterprise Manager Software manual Preparing for a Linux server migration

Page 35

The primary storage controller is configured with drives attached.

The destination server is booted to the Insight Control server migration ProLiant Boot CD ISO and is running the migration agent.

Select Auto Boot option in step 3 of the migration wizard.

Destination virtual machine host or virtual machine prerequisites

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

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 using the server migration Virtual Machine Boot CD ISO.

Create the virtual machine manually, and then boot the virtual machine manually 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 19).

Ensure that the SSH port is open when a firewall is in use or the server migration Source Agent may not be deployed successfully.

Verify compliance with all minimum prerequisites. See “Minimum source server prerequisites for all migrations” (page 33).

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.

If X-Windows is configured on the source server, the 32-bit version of libXtst runtime library must be installed.

Source physical server prerequisites

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

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

PermitRootLogin and PasswordAuthentication are set to Yes in the /etc/ssh/ sshd_config file and the sshd service is running.

The GRUB Boot Loader is required as the primary boot loader on the source server.

Prerequisites 35

Image 35
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 SecurityGenerating static or dynamic certificates Installing ProLiant Support PacksDisabling 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