HP PART NUMBER: 461487-401A manual Planning the migration

Page 18

4 Planning the migration

Planning a migration strategy

One challenge in migrating operating systems, applications, and data is modifying the migrated operating system to boot on the destination server and to function properly on the hardware. Insight Control server migration makes the required operating system changes for you.

To best prepare for a migration, consider developing a migration strategy before you run a migration. Migration strategies vary depending on machine hardware, network landscape, and applications. To develop a migration strategy, review the following before beginning your migration.

Preparing a schedule

Schedule preparation is an essential part of planning a migration strategy.

Be sure to include adequate time for copying data, because the source server will be offline until the migration is complete. Large volumes take time to migrate. Under optimal conditions, 1 GB of data requires 2 to 3 minutes to migrate. Using 2 minutes as a best-case scenario, migrating 500 GB of data might take more than 17 hours.

When a migration starts, the source server reboots to a minimal configuration so that no updates occur on the source server during migration. Only those services required for the migration are enabled.

Applications that normally run on the server are not available during migration. After the migration is complete, the source server is restored to its premigration state.

Schedule the migration to occur at a time when the source server can be offline.

Considerations for multiboot systems

Although Insight Control server migration supports migrating multi-boot systems, consider the following:

A supported operating system must be set as the default operating system for the boot disk.

The migration wizard enables the migration of all partitions with supported file systems. Unsupported operating systems on those partitions are also enabled for migration, but Insight Control server migration does not support them.

If unsupported operating systems are migrated, they might be detected, but proper drivers might not be installed. This issue can leave the unsupported operating system on the destination server unable to be booted.

Migrating large NTFS partitions

Insight Control server migration cannot migrate NTFS partitions greater than 2 TB in size.

Resizing file systems for migration

During the migration progress, the partitions being migrated can be resized. There are some file system caveats to be aware of that might affect the migration of your data.

Resizing Windows file systems

Insight Control server migration supports resizing and migration of NTFS volumes. However, some conditions may prevent server migration from resizing NTFS partitions:

Large NTFS partitions or NTFS partitions that have too many clusters, resulting in large volume cluster bitmaps that cannot be resized. In some cases, the volume might be recognized as

18 Planning the migration

Image 18
Contents HP Insight Control Server Migration 7.2 User Guide Legal Notices Contents IV Troubleshooting and support Migrating the serversPostmigration tasks Contents CD ISO Contents Support and other resources Glossary Index Part I Overview and concepts Overview Installing and configuring server migration softwareServer migration introduction Related productsRight configuration Server migration components Migration checklistServer migration concepts Overview of migrating a serverHP Insight Control server migration software tabs Migration screenHP Insight Control server migration software tabs Part II Premigration tasks Preparing hardware for migration Verifying hardware and operating system supportVerifying system requirements for the application station 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 PacksInstalling Service Pack for ProLiant Generating static or dynamic certificatesPreparing software for migration 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 Removing guest toolsChoosing server migration Agents Deploying AgentsNavigate to server migration Source Agent Server migration agent install screen 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 Source virtual machine prerequisitesSource physical server prerequisites SAN migrations in Windows Launching server migration by using the Deploy menu Starting the migration wizardLaunching server migration by using Quick Launch Identify the source serverQuick Launch Starting the migration wizard Postmigration tasks Installing ProLiant Support Packs after migrationInstalling Service Pack for ProLiant after migration X2P postmigration tasks WindowsEdit the boot.ini file to activate a graphical boot process X2V postmigration tasks WindowsX2P postmigration tasks Linux X2V postmigration tasks LinuxValidating Linux migrations Viewing migration logsValidating the migration Validating Windows migrationsPart IV Troubleshooting and support Troubleshooting User interfaceServer migration wizard hangs HP SIM Source preparation Source server identification failsMigration Agent deployment fails Linux Source Agent window does not appear on Rhel 64-bitIncorrect LUN size is detected in of the migration wizard Perform any one of the following on the source serverUnable to boot Windows due to unsigned or corrupt drivers Destination preparationDestination server identification fails Migration might appear If expected volumes do not appear, try one of the following Automatic booting of the destination physical server fails Suggested action Drivers cannot be installed or injected onto a boot disk Large volumes fail with a server thread errorMigration process Migration hangs if the source server is shut down 2011/03/14 141934 The job failedNtfs resize error message appears ReiserFS volumes are blocked for Linux migrationMigration fails during the disk cloning phase Error occurs during data copy of Linux migration SAN-connected destination server displays a blue screenDestination server boots with an invalid IP address HP Smart Array B320i controller name is not displayedLinux migration to servers with iSCSI storage fails to boot PostmigrationHidusb.sys Hidkbd.sys Mouhid.sys Suggested action Drives do not appear on the migrated operating system Guest OS ID guest name is not valid Server is unresponsive during PSP installation Multiboot kernel must be loaded before modules Suggested action Support and other resources How to contact HPSubscription service Information to collect before contacting HPDocuments HP authorized resellersRelated information WebsitesTypographic conventions Related documentationTIP Documentation feedback Applying old server migration standalone licenses Premigration consideration steps for clusters Basic hardware design of a three-node dusterPerforming the migration Post migration considerations and stepsPost migration considerations and steps Page Glossary Index Page SPP Postmigration tasks Yellow bang ! appears on NIC adapter