HP Virtual Connect Enterprise Manager Software manual Preparing software for migration

Page 19

5 Preparing software for migration

Verifying licenses for software to be migrated

Before performing 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 operating systems license agreements might require you to purchase a new license for the destination server.

IMPORTANT: Servers with Windows Original Equipment Manufacturer (OEM) licenses are not supported for migration. For licensing questions, contact HP support. See “Support and other resources” (page 66).

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 performing the migration, you need to manually disable, reconfigure, or uninstall other firewall products. If you reconfigure a firewall product, you will be required to uninstall 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 performing a migration, then 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 integrated Lights Out (iLO) for auto destination 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

Verifying licenses for software to be migrated

19

Image 19
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 Related products Installing and configuring server migration softwareServer migration introduction OverviewProduct Description Overview of migrating a server Migration checklistServer migration concepts Server migration componentsMigration screen HP Insight Control server migration software tabsServer 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 Disabling firewalls Preparing software for migrationVerifying licenses for software to be migrated Migration SecurityDisabling antivirus software Installing ProLiant Support PacksGenerating static or dynamic certificates 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 Uninstalling guest toolsChoosing server migration Agents Deploying server migration AgentsNavigate to server migration Source Agent Server migration agent install dialog 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 migrationPreparing for a Linux server migration SAN migrations in Windows Starting the migration wizard Launching server migrations using the Deploy menuVerify Source Physical server Quick Launch Launching server migrations using Quick LaunchAvailable operations X2V post-migration tasks Windows Installing ProLiant Support Packs after migrationPost-migration tasks X2P post-migration tasks WindowsX2P post-migration tasks Linux Edit the boot.ini file to activate a graphical boot processValidating Linux migrations X2V post-migration tasks LinuxViewing migration logs Validating the migrationPost-migration tasks Part IV Troubleshooting and support Server migration wizard hangs TroubleshootingUser interface Source preparationMigration Agent deployment fails Source server identification failsSuggestion action Linux Source Agent window does not appear on Rhel 64-bitIncorrect 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 SAN-connected destination server displays blue screen Destination server boots with an invalid IP addressPerform one of the following Post-migrationHidusb.sys Hidkbd.sys Mouhid.sys Suggested action Drives do not appear on the migrated operating system Server is unresponsive during PSP installation Destination virtual machine fail to boot after X2V migrationReboot 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 Related documentation Typographic conventionsTIP Applying old server migration standalone licenses Basic hardware design of a three-node duster Pre-migration consideration steps for clustersPost migration considerations and steps Performing the migrationPost migration considerations and steps Glossary Index Index SIM Websites