HP Virtual Connect Enterprise Manager Software manual

Page 59

Cause

There could be bad blocks on the source or destination disk.

Suggested action

Insight Control does not support migrations of disks with bad blocks. If the bad block is on the destination disk, change the destination disk.

SAN-connected destination server displays blue screen

Suggested action

To migrate Windows Server 2003 to a SAN-connected destination server, install the following on the source server:

Service Pack 1

Service Pack 2

Updated Storport storage driver (see http://support.microsoft.com/kb/932755)

Out of memory error occurs on the application station during migration

The Insight Control application station requires a minimum of 1024 MB of free memory for Insight Control migrations.

Suggested action

If an Out of memory error occurs on the application station during migration, you must free memory or add memory to the application station and then restart the migration.

Destination server boots with an invalid IP address

After a P2P migration, the destination server may boot with an invalid IP address (for example, 169.x.x.x), instead of using the IP address that was configured through the migration wizard.

Cause

This issue occurs if the destination IP address configuration fails or Dynamic Host Configuration Protocol (DHCP) is not enabled in the network. Whenever a NIC is added to the server, then by default the NIC is assigned an IP address using the DHCP configuration. If there is no DHCP server configured on the network, then the server will boot with an invalid IP address.

Suggested action

After the P2P migration is complete, manually configure the IP address on the destination server. Refer to the specific operating system documentation help files for specific instructions on performing this task.

Windows server migration Source Agent or PINT remote deployment fails with Agent is already deployed or not required error

When you remotely deploy the Windows server migration Source Agent or PINT from the Insight Control server migration application station or from Systems Insight Manager, the server migration Source Agent deployment fails with the error Agent is already deployed or not required. In addition, no logs are generated for the agent deployment under the <server migration installation folder>\log\AgentLogs\hp\log\source IP\ folder.

Migration process 59

Image 59
Contents HP Insight Control Server Migration 7.0 User Guide Legal Notices Contents Post-migration tasks IV Troubleshooting and supportMigrating the servers ISO Contents Contents Glossary Index Support and other resourcesApplying old server migration standalone licenses 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 application station system requirements Preparing hardware for migrationVerifying hardware and operating system support 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 PacksDisabling antivirus software 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 server identification fails Destination preparationIncorrect LUN size detected in of the migration wizard Suggested action CD ISO Auto booting destination physical server fails Manually migrate these disks after a successful migration Migration process Drivers cannot be installed or injected onto boot diskLarge volumes fail with server thread error Java.lang.OutOfMemoryError Java heap space Migration hangs if source server is shut down Ntfs resize error messageReiserFS volumes are blocked for Linux migration 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 Information to collect before contacting HP How to contact HPSupport and other resources Related information HP authorized resellersDocumentation feedback 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