HP Virtual Connect Enterprise Manager Software manual Verifying Windows source server requirements

Page 22

6 Preparing the source server and deploying the Source Agent

Verifying Windows source server requirements

The physical or virtual Windows source server requires the following:

•User account credentials with administrative rights

•A supported Windows operating system. For a list of operating systems, see the HP Insight Management Support Matrix available at: http://www.hp.com/go/insightmanagement/ docs.

•Available disk space of at least 180 MB

•The availability of ports 51125 and 51126

•Screen resolution of at least 800 x 600

•All detachable media removed

•If the source server is an application station, disable the HP Insight Control server migration Application Service and HP Insight Control server migration Web Service.

Preparing a Microsoft Hyper-V source server

If you are planning to migrate a source server with the Microsoft Hyper-V role enabled, perform one of the following on the source server:

•Turn off the hypervisor using bcdedit /set hypervisorlaunchtype off at a command line.

After the migration, you can re-enable the hypervisor at a command line by using bcdedit /set hypervisorlaunchtype auto.

•Remove the Microsoft Hyper-V role from the source server by using the server configuration tools.

Verifying Linux source server requirements

The physical Linux source server requires the following:

•User account credentials with administrative rights

•SELinux must be running in passive mode

•A supported Linux operating system. For a list of operating systems, see the HP Insight Management Support Matrix at:

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

•Available disk space of at least 10 MB on /boot and 150 MB under the directory where the Linux server migration Source Agent has to be installed.

NOTE: When Linux Source Agent is launched remotely from the CMS, the default location on the source server for agent installation is /root.

•The availability of ports 51125 and 51126

•Verify that you have removed all unused boot entries from /boot/grub/menu.lst and the corresponding initrd from the /boot.

•Disable any scripts that might clean up the migration agent files on reboot or shutdown. For instance, if the agent has been deployed manually to /root, ensure that there are no scripts which will cleanup /root on reboot/shutdown.

22 Preparing the source server and deploying the Source Agent

Image 22

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 Overview Installing and configuring server migration softwareServer migration introduction Related productsProduct Description Server migration components Migration checklistServer migration concepts 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 Migration Security Preparing software for migrationVerifying licenses for software to be migrated Disabling firewallsDisabling antivirus software Installing ProLiant Support PacksGenerating static or dynamic certificates 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 Uninstalling guest toolsChoosing 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 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 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 X2P post-migration tasks Windows Installing ProLiant Support Packs after migrationPost-migration tasks X2V post-migration tasks WindowsEdit the boot.ini file to activate a graphical boot process X2P post-migration tasks LinuxValidating the migration X2V post-migration tasks LinuxViewing migration logs Validating Linux migrationsPost-migration tasks Part IV Troubleshooting and support Source preparation TroubleshootingUser interface 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