HP PART NUMBER: 461487-401A manual Contents

Page 7

Suggested action	61
Filesystem on source disk \\.\PhysicalDrive0, Partition 0 could not be resized during the
migration	61
Cause	61
Suggested action	62
Migration fails during the disk cloning phase	62
Cause	62
Suggested action	62
Failed: Drivers could Not Be Injected Into Boot Disk in the logs	62
Suggested action	62
Starting a new migration after a current migration is stopped	62
Suggested action	62
Unrecoverable sector-read errors on the source server hard drive are not supported and fail
a Windows P2P or P2V migration	62
Cause	63
Suggested action	63
Source Agent fails to launch when source server reboots in migration agent mode	63
Suggested action	63
Error occurs during data copy of Linux migration	63
Cause	63
Suggested action	63
SAN-connected destination server displays a blue screen	63
Suggested action	63
Out of memory error occurs on the application station during migration	64
Suggested action	64
Destination server boots with an invalid IP address	64
Cause	64
Suggested action	64
Windows server migration Source Agent or PINT remote deployment is intermittent and
deployment fails with a General failure occurred error	64
Suggested action	64
Unable to detect HP FlexFabric 10Gb 2-port554FLR-SFP+ Adapter configured as iSCSI disk
in step 5 of migration wizard	64
Suggested action	64
HP Smart Array B320i controller name is not displayed	64
Suggested action	65
Unable to install Service Pack for ProLiant (SPP) on Windows 2008 SP2 operating system after
successful migration	65
Suggested action	65
Linux migration to servers with iSCSI storage fails to boot	65
Suggested action:	65
Postmigration	65
Migration does not start after confirmation. The event log continuously displays Operation
Migration waiting for connection to source	65
Suggested action	65
Destination server mouse and keyboard do not work after a Windows migration	65
Suggested action	65
USB mouse or keyboard drivers are not loaded after an X2P Windows migration	66
Cause	66
Suggested action	66
Mouse does not work on the iLO of the destination server after a Linux X2P migration	67
Suggested action	67
Mouse does not work on the destination ESX virtual machine after a V2V migration	67
Suggested action	67
Drive letters are not the same in the migrated virtual machine guest after migration	67

Contents 7

Image 7

Contents HP Insight Control Server Migration 7.2 User Guide Legal Notices Contents Migrating the servers IV Troubleshooting and supportPostmigration tasks Contents CD ISO Contents Support and other resources Glossary Index Part I Overview and concepts Related products Installing and configuring server migration softwareServer migration introduction OverviewRight configuration Overview of migrating a server Migration checklistServer migration concepts Server migration componentsMigration screen HP Insight Control server migration software tabsHP Insight Control server migration software tabs Part II Premigration tasks Verifying hardware and operating system support Preparing hardware for migrationVerifying system requirements for the application station 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 PacksInstalling Service Pack for ProLiant Disabling antivirus softwarePreparing software for migration 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 Removing guest toolsChoosing server migration Agents Deploying server migration AgentsNavigate to server migration Source Agent Server migration agent install screen 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 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 X2P postmigration tasks Windows Installing ProLiant Support Packs after migrationInstalling Service Pack for ProLiant after migration Postmigration tasksX2V postmigration tasks Windows Edit the boot.ini file to activate a graphical boot processX2V postmigration tasks Linux X2P postmigration tasks LinuxValidating Windows migrations Viewing migration logsValidating the migration Validating Linux migrationsPart IV Troubleshooting and support User interface TroubleshootingServer migration wizard hangs 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 preparation Unable to boot Windows due to unsigned or corrupt driversDestination server identification fails Migration might appear If expected volumes do not appear, try one of the following Automatic booting of the destination physical server fails Suggested action Large volumes fail with a server thread error Drivers cannot be installed or injected onto a boot diskMigration process 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 Information to collect before contacting HP How to contact HPSubscription service Support and other resourcesWebsites HP authorized resellersRelated information DocumentsRelated 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