HP PART NUMBER: 461487-401A manual Incorrect LUN size is detected in of the migration wizard

Page 53

Suggested action

The server migration Source Agent uses a 32–bit Java Runtime Environment. In 64–bit RHEL, the Linux source migration agent window does not appear, although the agent is running. To enable the display of the agent, you must install the X.Org X11 libXtst runtime library, libXtst-1.0.99.2-3.el6.i686.rpm.

Remote deployment of Linux Source Agent using nonroot credentials fails

Remote deployment of Linux Source Agent using nonroot credentials fails with the following error:

Failed to deploy server migration Source Agent. Error while installing the server migration Source Agent on the given Server : exec tar -zxf hpsmpagent.tar.gz -C /tmp on the remote host failed. The ports 51124, 51125 and 51126 required by the agent might be in use. : exec tar -zxf hpsmpagent.tar.gz -C /tmp on the remote host failed. The ports 51124, 51125 and 51126 required by the agent might be in use.

Suggested action

Deploy the Linux Source Agent by using root privileges.

Manual installation of Linux Source Agent using sudo user privileges fails

Manual installation of Linux Source Agent using sudo user privileges fails.

Suggested action

Launch the server migration Linux Source Agent by using proper root user privileges.

Incorrect LUN size is detected in step 2 of the migration wizard

If the size of the source LUN detected during step 2 of the migration wizard is incorrect, you might be attempting to initialize the LUN by using GPTs.

Cause

LUNs initialized with GPTs are not supported, even if they contain partitions with filesystems that server migration supports. Those partitions appear as RAW partitions in the migration wizard, and data might be incomplete after the migration.

Suggested action

Deselect LUNs initialized with GPTs in step 2 of the migration wizard, and manually copy data on GPT disks after the migration.

Migrating a source server fails with the Microsoft Hyper-V role enabled

If you are trying to migrate a source server with the Microsoft Hyper-V role enabled, you must make sure that certain preconditions are met.

Suggested action

Perform any one of the following on the source server:

•Turn off the hypervisor by using the following command: bcdedit /set hypervisorlaunchtype off

After the migration, you can re-enable the hypervisor by using the following command: bcdedit /set hypervisorlaunchtype auto

•Remove the Microsoft Hyper-V role from the source server.

Source preparation 53

Page 52 Page 54
Image 53
Page 52 Page 54
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 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 system requirements for the application station Preparing hardware for migrationVerifying hardware and operating system support 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 Server migration wizard hangs TroubleshootingUser interface 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 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 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