HP Insight Control - Manual (Page 108)

If you establish the source-to-destination or application-station-to-destination connection and the network
test reports a transfer speed of at least 250 kb/s, the Next button is enabled.
CAUTION: If the application-station-to-destination latency is less than 125 milliseconds, continue with
the migration. Latency greater than 125 milliseconds might cause driver injection issues.
9. Click Next.
10. Use the following steps to assign source disks to destination disks:
1. Map source disks to destination disks.
2. Ensure that migrated disks fit on their mapped destination disks.
For migrating the boot partition, HP Insight Control server migration needs extra space for creating
/-smpue for each of the valide initrd entries in partition>/grub/menu.lst. Each valid entry has a corresponding file name uncer the
boot partition. Choose a “Destination Size” that is large enough to create the /naem>-smpue files on the corresponding disk partition on the destination server. The Source Server
requirement earlier in the document already state that 10 MB free spec must be available on /boot
partition on the source. The recommended minimum value for the “Destination Size” for /boot is
hence equal to the used space in /boot plus 10 MB.
3. You must migrate the boot partition to the default boot disk of the boot controller. If one active
volume is migrated and you can identify the boot controller on the destination server, the boot
partition is migrated to the default boot disk of the boot controller.
4. Volumes stored on a common source disk are also stored on a common destination disk. You can
migrate a source disk with one or more source volume groups (VGs) to the same or a different
destination disk if there is enough space on the destination disk. However, you must select the
Logical Volume Managers (LVMs) to be migrated under the logical volume table in step 2 of the
migration wizard.
108 Using Insight Control server migration to migrate servers