| Version compatibility requirements for clusters and virtual machines |
The VMware vSphere version of the source cluster, the firmware type and operating system version of the virtual machines to be migrated, and the ACOS version of the target cluster must be supported in Arcfra Migration Tool compatibility requirements.
|
| License requirements for the source cluster |
The ESXi hosts in the source cluster use a non-free license.
|
| Requirements for virtual machines to be migrated |
- The virtual machine is either in the
Running or Shutdown state.
- The virtual machine has an operating system installed.
- The number of snapshots for a single virtual machine is less than 32.
- The virtual machine cannot have PCI passthrough or PCIe passthrough configured.
- The number of virtual disks on a single virtual machine is not 0.
- The virtual disk file is in
.vmdk format.
- If the virtual machine is managed by backup software that depends on virtual machine snapshots, stop the corresponding backup task before starting migration.
- If the virtual machine has an RDM disk mounted, remove the disk first, or shut down the virtual machine before migration.
- If the virtual machine has a disk whose sharing attribute is
Multi-Writer, change the sharing attribute to No Sharing before migration.
- If the virtual machine has a disk whose disk mode is
Independent - Persistent or Independent - Non-Persistent, change the disk mode to Dependent, or shut down the virtual machine before migration.
- If the virtual machine runs Linux, contains both SCSI and IDE disks, and these disks are written as drive letters in the device column of the
/etc/fstab file in the guest operating system, change the drive letters to disk UUIDs before migration.
- The
/root partition of the virtual machine is larger than 200 MB for initramfs backup.
|
| Requirements for target hardware resources |
- The available CPU resources in the cluster are sufficient to support normal operation of the migrated virtual machines.
- The cluster memory resources are greater than the total memory resources of all virtual machines to be migrated.
The available data space in the cluster is greater than the estimated required data space.
The data space for different storage policies should be calculated as follows:
- If the redundancy policy is replication:
- For thin provisioning: Estimated Required Data Space = (Sum of Virtual Disk Sizes of All Virtual Machines to Be Migrated + 5 GiB) x Number of Replicas
- For thick provisioning: Estimated Required Data Space = (Sum of Virtual Disk Sizes of All Virtual Machines to Be Migrated + Sum of System Disk Sizes of All Virtual Machines to Be Migrated) x Number of Replicas
- If the redundancy policy is erasure coding (k + m):
- For thin provisioning: Estimated Required Data Space = (Sum of Virtual Disk Sizes of All Virtual Machines to Be Migrated + 5 GiB) x (k+m)/k
- For thick provisioning: Estimated Required Data Space = (Sum of Virtual Disk Sizes of All Virtual Machines to Be Migrated + Sum of System Disk Sizes of All Virtual Machines to Be Migrated) x (k+m)/k
Note that the virtual disks mentioned above include data disks and system disks. At this stage, since it is unknown which disk is the system disk, it is recommended to take the average size of all virtual disks in a virtual machine as the system disk size.
|
