{{ $t('productDocDetail.guideClickSwitch') }}
{{ $t('productDocDetail.know') }}
{{ $t('productDocDetail.dontRemind') }}
6.11.3
{{sendMatomoQuery("Sangfor Cloud Platform (SCP)","ISO")}}

ISO

{{ $t('productDocDetail.updateTime') }}: 2025-12-17

ISO migration, also known as image migration, works as follows: Burn the ISO file of the current HCI version to a USB drive, then insert the USB drive into the server to be migrated and set the server to boot from the USB drive. Alternatively, if migrated from a VM platform, upload the ISO file to the virtualization platform, shut down the target VM, and reconfigure it to boot from the ISO file. Once booted, the ISO system will share all disks on the server to be migrated. After that, the hyper-converged platform directly converts all data on these disks into virtual qcow2-format disk files compatible with the hyper-converged platform. Finally, a new virtual machine is created using these qcow2 disk files.

A black and white logo

AI-generated content may be incorrect.

1.To perform managed migration, authorization of aHM must be activated.

2.HCI can access to Ports 443 and 902 of VMware.

3.The source virtual machine for migration must have at least 4GB of memory

4.Cluster-based services are not supported (e.g., RAC, SQL Always on).

5.ISO shutdown migration supports resumable transfer within one minute of interruption. If the migration interruption exceeds one minute, it will result in migration failure, and the migration will need to be restarted.

6.Migration is not supported for RDS databases, container platforms (Docker, Kubernetes), and big data platforms.