HP Virtual Connect Enterprise Manager Software manual Starting the migration wizard

Page 37

4.Follow the relevant migration steps in “Preparing for a Windows server migration” (page 34).

5.In step 5 (Specify destination disks) of the migration wizard, verify that you have selected the boot LUN that you configured in the HBA BIOS of the destination server when you migrate the boot partition on the source server.

NOTE: To migrate Windows 2003 to a SAN-connected destination server, you must first install Service Pack 2, and the updated Storport storage driver (see http://support.microsoft.com/kb/ 932755) on the source server.

You can perform a migration to a destination server with some source disks migrated to local disks on the destination and some source disks migrated to SAN disks presented to the destination.

A local disk cannot be migrated to a SAN disk on the same server. That is, a DAS-to-SAN migration cannot be run on the same server. For example, you cannot migrate a SAS disk on a server to a SAN disk on the same server. The migration must be a Server A to Server B migration, where A and B are distinct servers.

Before running an X2P migration to a SAN LUN, HP recommends that you disable any ports that are not used for migrating to the destination HBA before initiating the migration. Otherwise, if the operating system is migrated to a SAN LUN connected to a fibre channel HBA in the destination server, the server migration may not migrate to the primary LUN. Failing to disable unused ports may produce the error message Error loading operating system when the destination server is booted.

Starting the migration wizard

After source and destination server agents are launched, you can start the migration from Systems Insight Manager in two ways:

Through the Deploy menu

Using the Quick Launch feature

Launching server migrations using the Deploy menu

To launch Insight Control server migration from the Deploy menu, perform the following tasks:

1.In Systems Insight Manager, select the source server or source virtual machine. Ensure the source server is discovered properly and that the OS type and IP address are correctly identified.

2.From the main wizard, select Deploy→server migration Tools, and then select the appropriate migration option.

Starting the migration wizard

37

Image 37
Contents HP Insight Control Server Migration 7.0 User Guide Legal Notices Contents Migrating the servers IV Troubleshooting and supportPost-migration tasks ISO Contents Contents Applying old server migration standalone licenses Support and other resourcesGlossary Index Part I Overview and concepts Server migration introduction Installing and configuring server migration softwareOverview Related productsProduct Description Server migration concepts Migration checklistServer migration components Overview of migrating a serverMigration screen HP Insight Control server migration software tabsServer migration concepts Part II Pre-migration tasks Verifying hardware and operating system support Preparing hardware for migrationVerifying application station system requirements Planning the migration Resizing Linux file systems Verifying licenses for software to be migrated Preparing software for migrationMigration Security Disabling firewallsDisabling antivirus software Installing ProLiant Support PacksGenerating static or dynamic certificates 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 Uninstalling guest toolsDeploying server migration Agents Deploying AgentsNavigate to server migration Source Agent Server migration agent install dialog 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 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 Post-migration tasks Installing ProLiant Support Packs after migrationX2P post-migration tasks Windows X2V post-migration tasks WindowsX2P post-migration tasks Linux Edit the boot.ini file to activate a graphical boot processViewing migration logs X2V post-migration tasks LinuxValidating the migration Validating Linux migrationsPost-migration tasks Part IV Troubleshooting and support User interface TroubleshootingSource preparation Server migration wizard hangsMigration Agent deployment fails Source server identification failsSuggestion action Linux Source Agent window does not appear on Rhel 64-bitIncorrect LUN size detected in of the migration wizard Destination preparationDestination server identification fails Suggested action CD ISO Auto booting destination physical server fails Manually migrate these disks after a successful migration Large volumes fail with server thread error Drivers cannot be installed or injected onto boot diskMigration process Java.lang.OutOfMemoryError Java heap space ReiserFS volumes are blocked for Linux migration Ntfs resize error messageMigration 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 Support and other resources How to contact HPInformation to collect before contacting HP Documentation feedback HP authorized resellersRelated 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