HP Virtual Connect Enterprise Manager Software manual SAN migrations in Windows

Page 36

Source virtual machine prerequisites

If migrating from a source virtual machine, verify that the following prerequisites are complete:

Comply with all minimum prerequisites as listed in “Minimum source server prerequisites for all migrations” (page 33).

PermitRootLogin and PasswordAuthentication are set to Yes in the /etc/ssh/ sshd_config file and the sshd service is running.

The GRUB Boot Loader is the primary boot loader on the source server.

Guest tools are uninstalled.

Destination physical server prerequisites

If migrating to a destination physical server, verify that the following prerequisites are complete:

The primary storage controller must be configured with drives attached.

The destination server must be booted to Insight Control server migration ProLiant Boot CD ISO and running migration agent.

Select Auto Boot option in step 3 of the migration wizard.

Destination virtual machine host or virtual machine prerequisites

If migrating to a destination virtual machine, verify that the following prerequisites are complete:

Select one of the following:

Let Insight Control server migration create the virtual machine automatically, and then boot it using the Insight Control server migration Virtual Machine Boot CD ISO for virtual machines.

Create the virtual machine manually, and then boot the virtual machine manually using the Insight Control server migration Virtual Machine Boot CD ISO.

Verify that the destination virtual machine host has sufficient system resources, including processor, memory, and disk space to host the migrated virtual machine guest.

Temporarily disable any antivirus software auto-scans on the destination virtual machine host to prevent interrupting the migration process. Re-enable the antivirus software after the migration.

SAN migrations in Windows

Insight Control server migration supports Windows or Linux migrations to destination physical servers with Fibre Channel SAN connectivity. To verify that your Fibre Channel HBA is supported, see the HP Insight Management Support Matrix at the follow website:

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

The prerequisites for a migration to a server with Fibre Channel SAN connectivity are the same as the prerequisites for migration to a destination physical server, described in “Preparing for a Windows server migration” (page 34), “Preparing for a Linux server migration” (page 35) and, “Destination physical server prerequisites” (page 34) with the following additional preparatory steps:

1.Manually set up the SAN environment by doing the following on the destination server:

Create logical units on the storage

Configure SAN switches

Configure Host Bust Adapter (HBA)

2.After setting up the SAN environment, boot the destination server using the Boot CD ISO.

3.Run the migration wizard.

36 Migrating the servers

Image 36
Contents HP Insight Control Server Migration 7.0 User Guide Legal Notices Contents IV Troubleshooting and support Migrating the serversPost-migration tasks ISO Contents Contents Support and other resources Applying old server migration standalone licensesGlossary 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 Preparing hardware for migration Verifying hardware and operating system supportVerifying application station system requirements Planning the migration Resizing Linux file systems Preparing software for migration Verifying licenses for software to be migratedMigration Security Disabling firewallsInstalling ProLiant Support Packs Disabling antivirus softwareGenerating 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 actionDestination preparation Incorrect LUN size detected in of the migration wizardDestination server identification fails Suggested action CD ISO Auto booting destination physical server fails Manually migrate these disks after a successful migration Drivers cannot be installed or injected onto boot disk Large volumes fail with server thread errorMigration process Java.lang.OutOfMemoryError Java heap space Ntfs resize error message ReiserFS volumes are blocked for Linux migrationMigration 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 How to contact HP Support and other resourcesInformation to collect before contacting HP HP authorized resellers Documentation feedbackRelated 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