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

Page 22

NOTE: Before installing SPP on the destination server, ensure that the server has a minimum disk space of 1 GB.

•For Linux X2P migrations, you must manually apply the Linux SPP to the destination server after the migration is complete.

22 Preparing software for migration

Image 22

Contents HP Insight Control Server Migration 7.2 User Guide Legal Notices Contents Migrating the servers IV Troubleshooting and supportPostmigration tasks Contents CD ISO Contents Support and other resources Glossary Index Part I Overview and concepts Overview Installing and configuring server migration softwareServer migration introduction Related productsRight configuration Server migration components Migration checklistServer migration concepts Overview of migrating a serverHP Insight Control server migration software tabs Migration screenHP Insight Control server migration software tabs Part II Premigration tasks Verifying hardware and operating system support Preparing hardware for migrationVerifying system requirements for the application station 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 PacksInstalling Service Pack for ProLiant Generating static or dynamic certificatesPreparing software for migration 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 Removing guest toolsChoosing 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 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 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 Postmigration tasks Installing ProLiant Support Packs after migrationInstalling Service Pack for ProLiant after migration X2P postmigration tasks WindowsEdit the boot.ini file to activate a graphical boot process X2V postmigration tasks WindowsX2P postmigration tasks Linux X2V postmigration tasks LinuxValidating Linux migrations Viewing migration logsValidating the migration Validating Windows migrationsPart IV Troubleshooting and support User interface TroubleshootingServer migration wizard hangs 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 preparation Unable to boot Windows due to unsigned or corrupt driversDestination server identification fails Migration might appear If expected volumes do not appear, try one of the following Automatic booting of the destination physical server fails Suggested action Large volumes fail with a server thread error Drivers cannot be installed or injected onto a boot diskMigration process 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 Support and other resources How to contact HPSubscription service Information to collect before contacting HPDocuments HP authorized resellersRelated information 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