HP PART NUMBER: 461487-401A manual Server migration concepts, Server migration components

Page 13

2 Server migration concepts

Server migration components

The Insight Control server migration environment consists of the following required components:

•Application station—The computer from which the migration is set up and performed. This can be either a physical machine or a Windows guest on a supported hypervisor.

In earlier versions of HP Insight Management, the standalone installation of Insight Control server migration software was enabled. The server on which the server migration software was installed was then designated the application station. The installation of standalone server migration software is no longer supported, and so the same server that hosts the installation of Insight Management software and HP Systems Insight Manager now must host the Insight Control server migration software. The terms “application station” and "CMS" now both refer to the same server, which hosts both Insight Management and the server migration software.

•Source server—The physical source server or the virtual machine to be migrated.

•Destination server—The ProLiant server or the virtual machine to which the source server is migrated.

Overview of migrating a server

Use the checklist in this section as a general guide to the tasks performed during a server migration. For an explanation of the tabs in the server migration wizard, see “HP Insight Control server migration software tabs” (page 14).

Migration checklist

The specific tasks required to complete a migration are listed in the server migration online help. However, every migration can be condensed into the following general migration tasks:

1.Plan the migration.

2.Prepare the hardware and software for migration.

3.Prepare the source server or virtual machine for migration by installing the server migration Source Agent on the source server or virtual machine:

a.Deploy the server migration Source Agent to the source server.

b.Select the source disks to migrate.

4.Prepare the destination server or virtual machine for migration:

a.Boot the destination server by using the Boot CD. For HP ProLiant Gen8 servers, only the autoboot option is supported.

b.Create the destination disks.

5.Migrate the servers:

a.Test the network connectivity between the source and destination servers.

b.Map the source disks to the destination disks.

c.Choose destination server reboot, driver package, and network options.

d.Review choices and execute the migration.

6.Monitor the migration progress and view the logs when the migration is complete.

7.Log on to the new server and configure the drivers, communication settings, and boot options.

Server migration components

13

Page 12 Page 14
Image 13
Page 12 Page 14
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 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 hardware and operating system support Preparing hardware for migrationVerifying system requirements for the application station 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 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 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
Top Page Image Contents