HP PART NUMBER: 461487-401A manual Migrating the servers

Page 35

8 Migrating the servers

Prerequisites

CAUTION: If the Insight Control application station shuts down or fails during any migration, the migration fails. The application station must be available during the complete migration cycle for a successful migration.

Minimum source server prerequisites for all migrations

The prerequisites are the same for all migration types: P2P, P2V, V2P, or V2V. The subsequent sections describe only the prerequisites specifically different for that particular type of migration.

Before you start any migration, verify that these minimum prerequisites are completed on the source server:

A valid network connection exists between the source server and destination server.

The source server contains an active boot partition to be migrated.

Any pending reboots and software installations on the source server are finished.

Any antivirus software autoscans on the source server are temporarily disabled. Re-enable the antivirus software after the migration.

The disks are not corrupted. To verify, run CHKDSK (Windows) or File System Consistency Check (Linux).

All hard drives on the source (physical) server are correctly initialized (disk signature written).

All partitions on the source server have a valid file system and are in a healthy state.

All applications and background services on the source server are disabled.

After the migrated server has synchronized with the new hardware and is assigned a unique network identity, appropriate applications can be manually re-enabled and configured for the new environment.

Insight Control server migration is not installed and the ports, 51126 and 51125, are not used by any other service/application.

Uploading drivers

Use the Upload Drivers tab to upload binary files for the following:

iSCSI Initiator

For Windows migrations, the Microsoft iSCSI Initiator software is required for proper connection between the CMS and destination for mounting/injecting drivers.

PSP (Windows only)

You can upload one or more PSPs when you select additional migration options from the server migration wizard. When a PSP is selected during migration, it is copied to the destination server and executed on first boot after migration.

For more information on loading PSP executables, see the server migration online help.

SPP (Windows only)

You can upload one or more SPPs when you select additional migration options from the server migration wizard. When a SPP is selected during migration, it will be automatically applied to the destination server.

For more information on loading SPP ISO images, see the server migration online help.

Prerequisites 35

Image 35
Contents HP Insight Control Server Migration 7.2 User Guide Legal Notices Contents Postmigration tasks IV Troubleshooting and supportMigrating the servers Contents CD ISO Contents Support and other resources Glossary Index Part I Overview and concepts Related products Installing and configuring server migration softwareServer migration introduction OverviewRight configuration Overview of migrating a server Migration checklistServer migration concepts Server migration componentsMigration screen HP Insight Control server migration software tabsHP Insight Control server migration software tabs Part II Premigration tasks Verifying system requirements for the application station 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 PacksInstalling Service Pack for ProLiant Disabling antivirus softwarePreparing software for migration 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 Removing guest toolsChoosing server migration Agents Deploying server migration AgentsNavigate to server migration Source Agent Server migration agent install screen 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 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 X2P postmigration tasks Windows Installing ProLiant Support Packs after migrationInstalling Service Pack for ProLiant after migration Postmigration tasksX2V postmigration tasks Windows Edit the boot.ini file to activate a graphical boot processX2V postmigration tasks Linux X2P postmigration tasks LinuxValidating Windows migrations Viewing migration logsValidating the migration Validating Linux migrationsPart IV Troubleshooting and support Server migration wizard hangs TroubleshootingUser interface 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 server identification fails Unable to boot Windows due to unsigned or corrupt driversDestination preparation Migration might appear If expected volumes do not appear, try one of the following Automatic booting of the destination physical server fails Suggested action Migration process Drivers cannot be installed or injected onto a boot diskLarge volumes fail with a server thread error 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 Information to collect before contacting HP How to contact HPSubscription service Support and other resourcesWebsites HP authorized resellersRelated information DocumentsRelated 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