HP PART NUMBER: 461487-401A manual Server migration introduction, Overview, Related products

Page 11

1 Server migration introduction

Overview

HP Insight Control server migration provides an automated, accurate, and affordable way to migrate existing servers running Microsoft Windows or Linux and their content to the latest HP ProLiant server technologies or the latest virtualization platforms from VMware and Microsoft.

Insight Control server migration supports the following types of Microsoft Windows and Linux migrations:

•Physical-to-ProLiant (P2P) migration—Migrates a physical machine to a ProLiant server.

•Physical-to-Virtual (P2V) migration—Migrates a physical machine to a virtual machine guest in a virtual machine host.

•Virtual-to-ProLiant (V2P) migration—Migrates a virtual machine guest in a virtual machine host to a ProLiant server.

•Virtual-to-Virtual (V2V) migration—Migrates a virtual machine guest between virtualization layers.

Installing and configuring server migration software

Installing or upgrading server migration software

HP Insight Control server migration software is delivered on the HP Insight Management distribution media and is installed through the Insight Management Integrated Installer. The server on which you install Insight Management is designated to be the Central Management Server (CMS).

For installation and upgrade instructions and supported upgrade paths, see the HP Insight Management Installation and Configuration Guide.

For a description of all software that is delivered on the Insight Management distribution media, see the HP Insight Management Getting Started Guide.

Licensing server migration

The standard procedure for licensing Insight Control server migration is to purchase and apply Insight Control licenses. So if your destination server is licensed by Insight Control version 6.0 or later, you can perform unlimited migrations to the Insight Control licensed server.

For general licensing information, see the HP Insight Management Getting Started Guide, available at the following website:

http://www.hp.com/go/insightmanagement

Related products

Table 1 (page 11) lists HP products that are available for extending deployment or customizing the migrated server.

Table 1 Related products

Product

Description

HP Portable Images Network Tool (PINT) and HP Portable

Used to solve networking issues (specifically, NIC

Images Storage Assistant (PISA)

configuration issues) in moving operating system images

 

between HP BladeSystem c-Class blades using VMware

 

ESX and Microsoft Hyper-V (for PINT only) virtual machines,

 

and HP Virtual Connect on HP BladeSystem c-Class blades.

HP OpenView Change and Configuration Management solutions

Automates the management of software such as operating systems, applications, patches, content, and configuration

Overview 11

Page 10 Page 12
Image 11
Page 10 Page 12
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
Top Page Image Contents