HP Virtual Connect Enterprise Manager Software Server migration concepts, Migration checklist

Page 12

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 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 the 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 found 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 13)

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 with the Boot CD. For Gen8 servers, auto-boot option is only 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 in to the new server and configure the drivers, communication settings, and boot options.

12 Server migration concepts

Image 12
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 Installing and configuring server migration software Server migration introductionOverview Related productsProduct Description Migration checklist Server migration conceptsServer migration components Overview of migrating a serverHP Insight Control server migration software tabs Migration screenServer 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 Preparing software for migration Verifying licenses for software to be migratedMigration Security Disabling firewallsInstalling ProLiant Support Packs Disabling antivirus softwareGenerating static or dynamic certificates Part III Migration Preparing the source server and deploying the Source Agent Verifying Windows source server requirementsVerifying Linux source server requirements Preparing a Microsoft Hyper-V source serverUninstalling guest tools Choosing server migration AgentsDeploying 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 Prerequisites Linux destination size requirementPhysical destination servers Virtual machine hostsBooting the destination server Manually creating and booting a virtual destination server ILO boot prerequisitesPrerequisites for VMware ESX migration Page Migrating the servers Minimum source server prerequisites for all migrationsPreparing for a Windows server migration If you use a firewall, see Disabling firewallsPreparing for a Linux server migration SAN migrations in Windows Launching server migrations using the Deploy menu Starting the migration wizardVerify Source Physical server Launching server migrations using Quick Launch Quick LaunchAvailable operations Installing ProLiant Support Packs after migration Post-migration tasksX2P post-migration tasks Windows X2V post-migration tasks WindowsEdit the boot.ini file to activate a graphical boot process X2P post-migration tasks LinuxX2V post-migration tasks Linux Viewing migration logsValidating the migration Validating Linux migrationsPost-migration tasks Part IV Troubleshooting and support Troubleshooting User interfaceSource preparation Server migration wizard hangsSource server identification fails Migration Agent deployment failsLinux Source Agent window does not appear on Rhel 64-bit Suggestion actionDestination 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 Destination server boots with an invalid IP address SAN-connected destination server displays blue screenPost-migration Perform one of the followingHidusb.sys Hidkbd.sys Mouhid.sys Suggested action Drives do not appear on the migrated operating system Destination virtual machine fail to boot after X2V migration Server is unresponsive during PSP installationReboot 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 Typographic conventions Related documentationTIP Applying old server migration standalone licenses Pre-migration consideration steps for clusters Basic hardware design of a three-node dusterPerforming the migration Post migration considerations and stepsPost migration considerations and steps Glossary Index Index SIM Websites