HP Virtual Connect Enterprise Manager Software manual Available operations

Page 40

Figure 11 Available operations

3.Systems Insight Manager verifies the source physical server or source virtual machine.

If the selected server or virtual machine fails to satisfy the criteria to launch Insight Control server migration, then the Quick Launch list does not display the unsupported migration options.

If the selected server or virtual machine meets the criteria and you choose one of the options displayed, then the Insight Control server migration application opens to the first step of the migration wizard in a new browser with the IP address of the selected source entered for you.

4.Refer to the server migration online help for information about completing the rest of the steps in the server migration wizard.

IMPORTANT: Migrations can be launched only for source servers with supported operating systems and discoverable IP addresses that have been properly discovered in Systems Insight Manager. For more about discovery, see the HP Systems Insight Manager User Guide at the following website:

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

40 Migrating the servers

Image 40
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