HP Virtual Connect Enterprise Manager Software manual Preparing for a Windows server migration

Page 34

website.) Do not extract the binary that you download from the Microsoft website before uploading it here.

Preparing for a Windows server migration

The following sections list prerequisites for a Windows server migration.

If you use a firewall, see “Disabling firewalls” (page 19) .

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

Windows source server prerequisites

For Windows migrations, verify that the following source server prerequisites are complete:

If Windows Server 2003 is installed, then verify that the disks are initialized as MBR disks. Insight Control server migration does not support GPT-based disks.

During migration, the migration agent initiates an operating system reboot on the source physical server. Verify that the operating system is on the first boot order. Insight Control server migration supports migration of source servers that have operating systems installed on the primary drive (Hard Disk 0) and the primary drive loaded first in the boot order.

Record the drive letter or mount point to disk-partition mapping for dynamic disk partitions before performing the migration. Any simple (non-extended) dynamic disk partitions are converted to basic disk partitions. The mapped drive letters might have to be manually reassigned after migration.

Before migrating a source server with BitLocker Drive Encryption enabled and drives encrypted using BitLocker, decrypt the drives on the source server and disable BitLocker.

When a migration is started from a Windows Server 2003 application station to a Windows Server 2008 source server, migrations will be blocked in step 1 of the migration wizard. If the Source Agent was launched from the Windows 2003 application station, the Source Agent will be locked to that specific application station and must be stopped. In order to stop the agent on the Windows 2008 source server, manually run stopHPSMPAgent.cmd tool on the source desktop. The application station must be running Windows Server 2008 (x64) or later to run Windows Server 2008 server migrations.

Source physical server prerequisites

If migrating from a physical source server, verify that the following prerequisites are complete:

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

During migration, the migration Agent initiates an operating system reboot on the source server. Verify that the operating system is on the first boot order. If not, then manually change the boot order:

For Windows Server 2003, edit the [system drive]\boot.ini file or use thebootcfg.exe tool.

For Windows Server 2008 or later, use the bcdedit.exe tool.

Source virtual machine prerequisites

If migrating from a source virtual machine, verify that it complies with all minimum prerequisites as listed in “Minimum source server prerequisites for all migrations” (page 33).

Destination physical server prerequisites

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

34 Migrating the servers

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