Prerequisites, Physical destination servers, Virtual server hosts – HP Insight Control User Manual
Page 37: Linux destination size requirement, Physical destination servers virtual server hosts
7 Preparing the destination server and deploying the
destination agent
Prerequisites
Physical destination servers
A supported ProLiant destination server must be used for P2P or V2P migrations, and the
destination server disks must be configured to support migration of source servers.
For a list of supported ProLiant servers for P2P and V2P, see the list of supported servers in the
HP Insight Software Support Matrix at the following website:
When performing a P2P or V2P migration, prepare your destination server disk sizes and
configuration to accommodate the partitions to be migrated. You can change the logical disk
numbers on the destination server. For example, data on \PhysicalDrive5 on the source
server during a Windows migration might be reordered to \PhysicalDrive2 on the destination
server. During a Linux migration, data on /dev/sda on the source server might be reordered
to /dev/sdc on the destination server.
IMPORTANT:
X2P migrations can be launched only for ProLiant servers that have been properly
discovered in Insight Control. For more about discovery, see the HP Systems Insight Manager User
Guide at the following website:
Virtual server hosts
The destination virtual server hosts require the following:
•
User account credentials with administrative rights
•
Available memory of at least 600 MB
•
Available disk space of at least 750 MB
•
The latest operating system updates installed
When performing a P2V or V2V migration, be sure your destination virtual server host has
adequate memory, processor resources, and disk space to migrate the source server partitions.
For example, if disk 1 on your source server has 10 GB of data to migrate, verify that the disk
you migrate to on the destination server has at least 10 GB of available disk space.
Linux destination size requirement
For migrating the /boot partition during Linux Migration, Insight Control server migration needs
extra space for creating a new file for each of the valid initrd entries in
/boot/grub/menu.lst.
For each of the valid initrd entries in /boot/grub/menu.lst, a valid entry is created with
corresponding file name followed by -smpue.
Linux server migration can fail with the following error if Destination Size, chosen when
specifying destination disks in the migration wizard, does not have enough space to create the
files:
Server migration could not modify initrd on the destination server.
This could happen when there is not enough free space available on boot
partition. Increase free space on boot partition by deleting unused
Prerequisites
37