HP Virtual Connect Enterprise Manager Software manual Preparing hardware for migration

Page 16

3 Preparing hardware for migration

Verifying hardware and operating system support

Before starting an X2P (P2P or V2P) migration, verify the following:

The source server operating system is supported on the destination server. To verify OS support on ProLiant destination servers, see the following website:

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

For the supported hardware and software configurations of server migration, see HP Insight Management Support Matrix available at:

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

Remove unsupported storage and NIC controllers from the destination server before performing a migration. Unsupported storage and NIC controllers can be added back on the destination server, with proper manual configuration, after performing a migration.

Verifying application station system requirements

The application station has the following prerequisites:

A supported Windows operating system running on physical hardware or as a Windows guest on a supported hypervisor. For a list of supported operating systems, and CMS hardware and software requirements and caveats see the HP Insight Management Support Matrix at the following website:

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

Microsoft iSCSI Initiator, which you can download and install from http://www.microsoft.com if not already available with the operating system on your application station.

Insight Control server migration installed on an NTFS partition

Availability of ports 51124 and 51125 (or ports specified during Insight Control installation for agent communications and iLO booting)

Availability of port 51127

User account credentials with administrative rights

Free disk space of at least 300 MB per iLO Boot, while booting a destination server for P2P and V2P

The initial installation of Insight Control server migration can take 1GB of storage space, and each automatically booted destination server will need at least 300MB of storage space on the application station for non-Gen8 servers.

16 Preparing hardware for migration

Image 16
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 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 Verifying hardware and operating system support Preparing hardware for migrationVerifying application station system requirements Planning the migration Resizing Linux file systems Preparing software for migration Verifying licenses for software to be migratedMigration Security Disabling firewallsDisabling antivirus software Installing ProLiant Support PacksGenerating 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 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