HP Virtual Connect Enterprise Manager Software manual Server migration introduction, Overview

Page 10

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 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).

See the HP Insight Management Installation and Configuration Guide for installation and upgrade instructions and supported upgrade paths.

See the HP Insight Management Getting Started Guide for a description of all software that is delivered on the Insight Management distribution media.

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 6.0 or above, you can perform unlimited migrations to the Insight Control licensed server.

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

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

Related products

Table 1: “Related products” (page 10) lists HP products that are available for extending deployment or customizing the migrated server.

Table 1 Related products

Product

Description

PINT and PISA

Used to solve networking issues (specifically, NIC

 

configuration issues) when 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

10 Server migration introduction

Image 10
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 Overview Installing and configuring server migration softwareServer migration introduction Related productsProduct Description Server migration components Migration checklistServer migration concepts Overview of migrating a serverHP Insight Control server migration software tabs Migration screenServer 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 Migration Security Preparing software for migrationVerifying licenses for software to be migrated Disabling firewallsDisabling antivirus software Installing ProLiant Support PacksGenerating static or dynamic certificates Part III Migration Verifying Linux source server requirements Preparing the source server and deploying the Source AgentVerifying Windows source server requirements Preparing a Microsoft Hyper-V source serverDeploying server migration Agents Uninstalling guest toolsChoosing 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 Physical destination servers PrerequisitesLinux destination size requirement 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 X2P post-migration tasks Windows Installing ProLiant Support Packs after migrationPost-migration tasks X2V post-migration tasks WindowsEdit the boot.ini file to activate a graphical boot process X2P post-migration tasks LinuxValidating the migration X2V post-migration tasks LinuxViewing migration logs Validating Linux migrationsPost-migration tasks Part IV Troubleshooting and support Source preparation TroubleshootingUser interface Server migration wizard hangsSource server identification fails Migration Agent deployment failsLinux Source Agent window does not appear on Rhel 64-bit Suggestion actionIncorrect 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 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 Support and other resources How to contact HPInformation to collect before contacting HP Documentation feedback HP authorized resellersRelated 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