HP Virtual Connect Enterprise Manager Software manual Post-migration tasks

Page 44

2.Compare the source and the destination server to ensure that the partitions selected on the source server are present on the destination server.

3.Compare random samples of files and directories between the source and the destination servers to ensure that the data has been migrated successfully.

44 Post-migration tasks

Image 44

Contents HP Insight Control Server Migration 7.0 User Guide Legal Notices Contents Post-migration tasks IV Troubleshooting and supportMigrating the servers ISO Contents Contents Glossary Index Support and other resourcesApplying old server migration standalone licenses 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 application station system requirements 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 firewallsGenerating static or dynamic certificates Installing ProLiant Support PacksDisabling antivirus software 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 actionDestination server identification fails Destination preparationIncorrect LUN size detected in of the migration wizard Suggested action CD ISO Auto booting destination physical server fails Manually migrate these disks after a successful migration Migration process Drivers cannot be installed or injected onto boot diskLarge volumes fail with server thread error Java.lang.OutOfMemoryError Java heap space Migration hangs if source server is shut down Ntfs resize error messageReiserFS volumes are blocked for Linux migration 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 Information to collect before contacting HP How to contact HPSupport and other resources Related information HP authorized resellersDocumentation feedback 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