HP Virtual Connect Enterprise Manager Software manual X2V post-migration tasks Linux

Page 43

4.If the source and destination servers must be on the network at the same time:

a.Change the host name of either server or consider reconfiguring the applications.

b.If the IP addresses are static, reassign them.

5.If the license is not a volume license, then reactivate it.

6.The mouse and keyboard might not be immediately active after the migration. Wait until all required drivers are automatically installed by the guest operating system.

X2V post-migration tasks (Linux)

After you complete an X2V migration, perform the following steps on the destination server:

1.If you manually booted the virtual machine using the Insight Control server migration Virtual Machine Boot CD ISO, you must disconnect the Insight Control server migration Virtual Machine Boot CD ISO and then manually reboot or shut down the virtual machine.

2.Perform a network configuration for the migrated virtual machine guest. To do so, access the destination virtual machine host remote console to configure the network connections for the migrated virtual machine guest.

3.(Optional) Add a CD-ROM component to the destination virtual machine. The CD-ROM might be required to install additional Integrated Components.

After the virtual machine reboots, you must perform the following steps on the destination virtual machine guest for hypervisors.

1.Modify the system host name.

2.Install the proper Guest tools.

3.If necessary, verify the network connections.

4.The mouse and keyboard might not be immediately active on the migrated virtual machine guest. Wait until all required drivers are automatically installed by the guest operating system, and reboot the migrated virtual machine guest when prompted.

Viewing migration logs

From the View Status/Logs tab, you can:

View currently running migrations

View a log of the migration results

Create support logs

For more information, click the help icon on the server migration View Status/Logs page.

NOTE: When a job is complete, its link no longer appears in the View Status/Logs page, but the job-specific log files are still available in the HP Insight Control server migration installation path\logs directory.

Validating the migration

Validating Linux migrations

To verify that the Linux migration was successful, you can do the following:

1.Compare the md5 checksum of the files on the migrated file-system with the checksum on the source. The md5 checksum should match for all files except for the initrd and log files.

2.Ensure that the operating system on the destination server boots normally without critical errors.

Validating Windows migrations

To verify that the Windows migrations was successful, you can do the following:

1.Ensure that the operating system on the destination server boots normally without critical errors.

X2V post-migration tasks (Linux) 43

Image 43
Contents HP Insight Control Server Migration 7.0 User Guide Legal Notices Contents Migrating the servers IV Troubleshooting and supportPost-migration tasks ISO Contents Contents Applying old server migration standalone licenses Support and other resourcesGlossary Index 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 hardware and operating system support Preparing hardware for migrationVerifying application station system requirements Planning the migration Resizing Linux file systems Disabling firewalls Preparing software for migrationVerifying licenses for software to be migrated Migration SecurityDisabling antivirus software Installing ProLiant Support PacksGenerating static or dynamic certificates 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 Launch Available 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-bitIncorrect LUN size detected in of the migration wizard Destination preparationDestination server identification fails Suggested action CD ISO Auto booting destination physical server fails Manually migrate these disks after a successful migration Large volumes fail with server thread error Drivers cannot be installed or injected onto boot diskMigration process Java.lang.OutOfMemoryError Java heap space ReiserFS volumes are blocked for Linux migration Ntfs resize error messageMigration hangs if source server is shut down 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 Support and other resources How to contact HPInformation to collect before contacting HP Documentation feedback HP authorized resellersRelated information 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