The choice of migration technologies should consider minimizing the workload required by business teams to modify application configurations, as well as reducing the complexity of business cutovers. Different business types (e.g., virtual machines, SQL databases, Oracle RAC) should adopt different migration methods.

Below are the applicable scenarios for each migration method. Please select the most appropriate one based on your specific situation.

	VMware integrate migrate(aHM)		SCMT				ISO	Cross Cluster	OVA/OVF/VMA Import
Method	Cold Migration	Live Migration	Agentbase	Agentless	Hot Standby	Backup	Cold Migration	Cross Cluster	OVA/OVF/VMA Import
License	yes		yes				no	no	no
Speed	Unlimited, subject to storage and network limitations		100MB/s (Gigabit network) 500MB/s(10 Gigabit netwrok)	35MB/s	300MB/s	300MB/s	50MB/s	HCI version 670 and below: 50MB/s HCI version 680: No limit	/
Business Downtime	all the process	During aHM Migration, in the state of live migration, the final phase of the migration involves shutting down the source virtual machine on VMware to complete the entire migration process.The interruption time is the duration between the completion of the shutdown and the time the virtual machine is powered on within the HCl cluster.	5-10mins	5-10mins	60s	30min	all the process	NO	all the process
Agent Install	no		yes	no	yes	yes	no	no	no
breakpoint resume	no	no	15 mins	15 mins	15 mins	15 mins	10 mins	no	/
source VM Mem Requirement	no	no	mem more than 2G	mem more than 2G	mem more than 2G	mem more than 2G	mem more than 4G	no	no
Limt	1.Cluster-based services are not supported (e.g., RAC, SQL Always on,AD cluster). 2.Migration is not supported for RDS databases, container platforms (Docker, Kubernetes), and big data platforms. 3.do not support independ disk 4.do not support RDM disk 5.do not support passthrough NIC 6.do not support nested virtualization VM 7.do not support migration physical server to HCI		1.Cluster-based services are not supported (e.g., RAC, SQL Always on,AD cluster). 3.do not support container platforms (Docker, Kubernetes), and big data platforms. 4.Migration is not supported for RDS databases 5.do not support nested virtualization VM 6. do not support migration physical server to HCI	1.Cluster-based services are not supported (e.g., RAC, SQL Always on,AD cluster). 2.do not support container platforms (Docker, Kubernetes), and big data platforms. 3.do not support independ disk 4.do not support RDM disk 5.Migration is not supported for RDS databases 6.do not support passthrough NIC 7.Does not support nested virtualization VM or physical server to HCI	1.Cluster-based services are not supported (e.g., RAC, SQL Always on,AD cluster). 2.Migration is not supported for container platforms (Docker, Kubernetes), and big data platforms. 3.SCMT requires 1.5 to 2 times the amount of data to be migrated as free storage space. 4.Migration is not supported for RDS databases 5.Does not support nested virtualization VM or physical server to HCI	1.Cluster-based services are not supported (e.g., RAC, SQL Always on,AD cluster). 2.Migration is not supported for container platforms (Docker, Kubernetes), and big data platforms. 3.SCMT requires 1.5 to 2 times the amount of data to be migrated as free storage space. 4.Migration is not supported for RDS databases 5.Does not support nested virtualization VM or physical server to HCI	1.Cluster-based services are not supported (e.g., RAC, SQL Always on,AD cluster). 2.Migration is not supported for RDS databases, container platforms (Docker, Kubernetes), and big data platforms. 3.do not support independ disk 4.do not support RDM disk 5.do not support passthrough NIC 6.Does not support nested virtualization VM or physical server to HCI	Cross Cluster Support Version	The OS needs to be one that HCI can support. Does not support nested virtualization VM or physical server to HCI
support OS	Support OS		Support kernel				Support OS	Support OS	Support OS
Applicable scenarios	1.Sangfor paltform has already managed the VMware cluster.		1.Point-to-point: Suitable for most business migrations. 2.Hot standby: Suitable for core businesses with high continuity requirements. 3.Backup: Suitable for large data volumes with limited bandwidth.				1.A business system that can tolerate prolonged downtime and data loss. 2.SCMT migration service has not been purchased.	Applicable for migration between different versions of HCI.	Applicable for scenarios where the source can export OVA, OVF, or VMA files.

The speeds are all when the network status is good and storage speed is not considered.

Cautions

• If a VMware VM is configured with an SR-IOV passthrough network card, the VM’s network card type on VMware must be changed to another type before migration.

• If the VMware VM uses RDM disks, management-based migration is not supported.

• If VMware VM uses independent disks, management-based migration is not supported.

• If the VMware VM has performed snapshot rollbacks (e.g., restoring the VM from a snapshot), it cannot be migrated via the VMware CBT snapshot interface.

• If the VM mounts external storage LUNs:

Bare LUN is not formatted with VMFS, RDM assigned to the VM (i.e., RDM disk).

Bare LUN is not formatted with VMFS, accessed by the VM via iSCSI.

These configurations cannot be migrated via VMware management-based migration.

It is recommended to use SCMT agent-based migration or perform a conversion before using aHM migration. The conversion can do like following:

RDM disk: Shut down the virtual machine, clone it, and change the virtual disk to non-independent (dependent) mode.

Independent Disk: Shut down the virtual machine and change the virtual disk to dependent mode

The virtual machine is configured with an SR-IOV passthrough network card: Change the virtual machine’s passthrough network card to a virtual network card.

{{ $t('index.defaultHeader.logo') }}

Sangfor Cloud Platform (SCP)

Choose the right migration method