HP PART NUMBER: 461487-401A manual Preparing software for migration, Migration security

Page 20

5 Preparing software for migration

Verifying licenses for software to be migrated

Before you perform a migration, review all hardware, operating system, and application licenses on the source server and acquire all valid licenses necessary for the destination server. Some hardware, software, and OS license agreements might require you to purchase a new license for the destination server.

IMPORTANT: Servers that have Windows OEM licenses are not supported for migration. For licensing questions, contact HP support. For information about HP support, see “Support and other resources” (page 73).

Migration security

Disabling firewalls

The source server Microsoft Windows firewall or Linux firewall and SELinux are disabled automatically by server migration when a migration begins. The firewall and SELinux (if applicable) are re-enabled after the migration is completed.

Before you perform the migration, you must manually disable, reconfigure, or remove other firewall products. If you reconfigure a firewall product, you will be required to remove the product before migration and reinstall it after migration.

If the firewall is not disabled or configured properly on the source server, application station, and virtual machine hosts before a migration, the source server, application station, and virtual machine hosts might not be able to communicate. Symptoms of this issue can include the following:

The application station cannot detect the source server migration Agent for migrations.

The source server hangs after booting into exclusive mode during migrations.

The following TCP ports are used for Insight Control server migration:

Port 51124—For communication between the Insight Control server migration Web Service and the Insight Control application service using Secure Sockets Layer (SSL)

Port 51125—For communication between the Insight Control server migration Web Service and iLO for autodestination boot

Ports 51125 and 51126—For communication between the Insight Control server migration Application Service and the migration agent on the source server

Ports 51125 and 51126—For communication between the Insight Control server migration Application Service and the migration agent on the destination server

Port 51126—For communication between the migration agents on the source server and destination server

Port 51127—For use on the application station for Insight Control server migration Web Service

SSH port 22—For Linux migrations

20 Preparing software for migration

Image 20
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 Installing and configuring server migration software Server migration introductionOverview Related productsRight configuration Migration checklist Server migration conceptsServer migration components Overview of migrating a serverHP Insight Control server migration software tabs Migration screenHP 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 Preparing software for migration Verifying licenses for software to be migratedMigration security Disabling firewallsInstalling ProLiant Support Packs Installing Service Pack for ProLiantDisabling antivirus software Generating static or dynamic certificatesPreparing software for migration 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 serverRemoving guest tools Choosing server migration AgentsDeploying server migration Agents Deploying AgentsNavigate to server migration Source Agent Server migration agent install screen 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 Source virtual machine prerequisitesSource physical server prerequisites SAN migrations in Windows Launching server migration by using the Deploy menu Starting the migration wizardLaunching server migration by using Quick Launch Identify the source serverQuick Launch Starting the migration wizard Installing ProLiant Support Packs after migration Installing Service Pack for ProLiant after migrationPostmigration tasks X2P postmigration tasks WindowsEdit the boot.ini file to activate a graphical boot process X2V postmigration tasks WindowsX2P postmigration tasks Linux X2V postmigration tasks LinuxViewing migration logs Validating the migrationValidating Linux migrations Validating Windows migrationsPart IV Troubleshooting and support Server migration wizard hangs TroubleshootingUser interface HP SIM Source preparation Source server identification failsMigration Agent deployment fails Linux Source Agent window does not appear on Rhel 64-bitIncorrect LUN size is detected in of the migration wizard Perform any one of the following on the source serverDestination 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 Migration hangs if the source server is shut down 2011/03/14 141934 The job failedNtfs resize error message appears ReiserFS volumes are blocked for Linux migrationMigration fails during the disk cloning phase Error occurs during data copy of Linux migration SAN-connected destination server displays a blue screenDestination server boots with an invalid IP address HP Smart Array B320i controller name is not displayedLinux migration to servers with iSCSI storage fails to boot PostmigrationHidusb.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 How to contact HP Subscription serviceSupport and other resources Information to collect before contacting HPHP authorized resellers Related informationDocuments WebsitesTypographic conventions Related documentationTIP Documentation feedback Applying old server migration standalone licenses Premigration consideration steps for clusters Basic hardware design of a three-node dusterPerforming the migration Post migration considerations and stepsPost migration considerations and steps Page Glossary Index Page SPP Postmigration tasks Yellow bang ! appears on NIC adapter