HP Virtual Connect Enterprise Manager Software manual Planning the migration

Page 17

4 Planning the migration

Planning a migration strategy

One challenge when 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 running 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 essential when planning a migration strategy.

Be sure to include adequate time for copying data, as 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 two to three minutes to migrate. Using two 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 execute on the server are not available during migration. After the migration is complete, the source server is restored to its pre-migration state.

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

Considerations for multi-boot systems

While 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, which 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 1023 GB 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 may 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 with too many clusters, resulting in large volume cluster bitmaps that cannot be resized. In some cases, the volume might be recognized as

Planning a migration strategy 17

Image 17
Contents HP Insight Control Server Migration 7.0 User Guide Legal Notices Contents Post-migration tasks IV Troubleshooting and supportMigrating the servers ISO Contents Contents Glossary Index Support and other resourcesApplying old server migration standalone licenses Part I Overview and concepts Server migration introduction Installing and configuring server migration softwareOverview Related productsProduct Description Server migration concepts Migration checklistServer migration components Overview of migrating a serverMigration screen HP Insight Control server migration software tabsServer migration concepts Part II Pre-migration tasks Verifying application station system requirements Preparing hardware for migrationVerifying hardware and operating system support Planning the migration Resizing Linux file systems Verifying licenses for software to be migrated Preparing software for migrationMigration Security Disabling firewallsGenerating static or dynamic certificates Installing ProLiant Support PacksDisabling antivirus software Part III Migration Verifying Windows source server requirements Preparing the source server and deploying the Source AgentVerifying Linux source server requirements Preparing a Microsoft Hyper-V source serverChoosing server migration Agents Uninstalling guest toolsDeploying 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 Linux destination size requirement PrerequisitesPhysical destination servers Virtual machine hostsBooting the destination server ILO boot prerequisites Manually creating and booting a virtual destination serverPrerequisites for VMware ESX migration Page Minimum source server prerequisites for all migrations Migrating the serversIf you use a firewall, see Disabling firewalls Preparing for a Windows server migrationPreparing for a Linux server migration SAN migrations in Windows Starting the migration wizard Launching server migrations using the Deploy menuVerify Source Physical server Quick Launch Launching server migrations using Quick LaunchAvailable operations Post-migration tasks Installing ProLiant Support Packs after migrationX2P post-migration tasks Windows X2V post-migration tasks WindowsX2P post-migration tasks Linux Edit the boot.ini file to activate a graphical boot processViewing migration logs X2V post-migration tasks LinuxValidating the migration Validating Linux migrationsPost-migration tasks Part IV Troubleshooting and support User interface TroubleshootingSource preparation Server migration wizard hangsMigration Agent deployment fails Source server identification failsSuggestion action Linux Source Agent window does not appear on Rhel 64-bitDestination server identification fails Destination preparationIncorrect LUN size detected in of the migration wizard Suggested action CD ISO Auto booting destination physical server fails Manually migrate these disks after a successful migration Migration process Drivers cannot be installed or injected onto boot diskLarge volumes fail with server thread error Java.lang.OutOfMemoryError Java heap space Migration hangs if source server is shut down Ntfs resize error messageReiserFS volumes are blocked for Linux migration Migration fails during the disk cloning phase Error during data copy of Linux migration SAN-connected destination server displays blue screen Destination server boots with an invalid IP addressPerform one of the following Post-migrationHidusb.sys Hidkbd.sys Mouhid.sys Suggested action Drives do not appear on the migrated operating system Server is unresponsive during PSP installation Destination virtual machine fail to boot after X2V migrationReboot the server and then reinstall PSP manually Information to collect before contacting HP How to contact HPSupport and other resources Related information HP authorized resellersDocumentation feedback Related documentation Typographic conventionsTIP Applying old server migration standalone licenses Basic hardware design of a three-node duster Pre-migration consideration steps for clustersPost migration considerations and steps Performing the migrationPost migration considerations and steps Glossary Index Index SIM Websites