HP PART NUMBER: 461487-401A manual Postmigration

Page 65

Suggested action

No action required.

Unable to install Service Pack for ProLiant (SPP) on Windows 2008 SP2 operating system after successful migration

After successful server migration of Windows 2008 SP2 operating system, SPP fails to install as part of postmigration task.

Suggested action

After the migration is complete, connect SPP ISO to the destination server and manually install SPP.

Linux migration to servers with iSCSI storage fails to boot

When you perform a X2P migration of Linux OS on any server with iSCSI storage as destination, the kernel panic message appears.

Suggested action:

The iscsi-initiator-utilsand dracut-networkRPM packages are missing on the source and must be installed on the source before migration.

Postmigration

Migration does not start after confirmation. The event log continuously displays

Operation Migration waiting for connection to source

When the migration starts, the source server reboots and runs the migration agent in exclusive mode during migration.

Rebooting the source machine might take a few minutes. If this process takes a long time, verify that the source machine is rebooted with the migration agent running in exclusive mode. The source machine might be waiting for user input during the reboot. Another possibility is that the boot order is incorrect.

If the migration agent is deployed on an operating system that is not first in the boot order, the migration agent might fail to boot to the Insight Control mode.

Suggested action

Change the boot order by editing boot.ini, and verify that the operating system on which Insight Control is deployed is first in the boot order.

Destination server mouse and keyboard do not work after a Windows migration

The mouse and keyboard might not be operational immediately on a destination server after a migration.

Suggested action

To detect and activate the mouse and keyboard, reboot the destination server so that PnP correctly detects and activates the mouse and keyboard.

If the mouse and keyboard still do not work, ensure that DevCon is installed and ready on the Upload Drivers tab and then re-run the migration. Select Use DevCon in Step 6 of the P2P or V2P migration wizard.

Postmigration 65

Image 65
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