HP Virtual Connect Enterprise Manager Software manual

Page 63

Drives do not appear on the migrated operating system

After a successful migration, some migrated volumes do not appear in Windows Explorer.

Suggested action

Depending on the operating system, perform the following task to assign a driver letter to the volume so it is visible in Windows Explorer:

1.For Windows Server 2003 systems—Select Control Panel→Administrative Tools→Computer Management→Disk Management, and then verify that the disk manager has initialized all disks.

2.Assign the driver letter in the migrated virtual machine guest using the appropriate disk administrator or manager.

Mouse and keyboard do not work after migrating a Microsoft Hyper-V virtual machine to a ProLiant server

Suggested action

If the mouse and keyboard do not work after migrating a Microsoft Hyper-V virtual machine to a ProLiant server, reboot the destination server.

If rebooting does not solve the issue, try the following:

Uninstall Microsoft Hyper-V Integration Tools on the source virtual machine before performing a migration.

Rerun the migration, but select Automatic PSP installation in the migration wizard so that the PSP is installed automatically on the destination server after a migration.

Rerun the migration, but select Use DevCon in the migration wizard so that DevCon is installed automatically on the ProLiant server at the end of the migration.

Static IP address cannot be assigned on the destination server after migration

Assigning a static IP address on the destination server might result in an error similar to the following:

The IP address xxx.xxx.xxx.xxx you have entered for this network adapter is already assigned to another adapter.

This scenario can occur if the IP address is assigned to a network adapter on the source server.

Suggested action

For more information, see the following website:

http://support.microsoft.com/kb/269155/en-us

Virtual machine hosts Integrated Components do not install on the destination virtual machine following migration

Suggested action

To resolve this issue:

1.Power down the destination virtual machine.

2.Add a CD-ROM drive to the virtual machine.

3.Power up the virtual machine, and then restart the installation of the Integrated Components.

Exclamation point (!) appears on the NIC adapter in Device Manager on the migrated virtual machine

After performing a migration, the NIC Adapter might not appear on the destination virtual machine. This might happen during V2V migrations between VMware Server and VMware ESX servers. This

Post-migration 63

Image 63
Contents HP Insight Control Server Migration 7.0 User Guide Legal Notices Contents IV Troubleshooting and support Migrating the serversPost-migration tasks ISO Contents Contents Support and other resources Applying old server migration standalone licensesGlossary 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 Preparing hardware for migration Verifying hardware and operating system supportVerifying application station system requirements Planning the migration Resizing Linux file systems Disabling firewalls Preparing software for migrationVerifying licenses for software to be migrated Migration SecurityInstalling ProLiant Support Packs Disabling antivirus softwareGenerating 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 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 preparation Incorrect LUN size detected in of the migration wizardDestination server identification fails Suggested action CD ISO Auto booting destination physical server fails Manually migrate these disks after a successful migration Drivers cannot be installed or injected onto boot disk Large volumes fail with server thread errorMigration process Java.lang.OutOfMemoryError Java heap space Ntfs resize error message ReiserFS volumes are blocked for Linux migrationMigration 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 How to contact HP Support and other resourcesInformation to collect before contacting HP HP authorized resellers Documentation feedbackRelated 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