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

Disaster Recovery

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

Features:

When tenants use a virtual machine, they can perform aDR by themselves and add virtual machines that need disaster recovery to the disaster recovery policy for disaster recovery.

When the primary site is normal, and the virtual machine fails, the virtual machine can be recovered through local recovery. When the primary site requires planned maintenance or an unforeseen disaster occurs, the disaster recovery data of the secondary site can quickly recover the virtual machine from the secondary site to resume production.

Precautions:

  1. The default RPO for tenants to perform remote disaster recovery is 24 hours. If the tenants need to change the disaster recovery RPO, please contact the administrator. Currently supports RPO: 1 second, 10 seconds, 10 minutes, 30 minutes, 1 hour, 2 hours, 4 hours, 8 hours, 12 hours, and 24 hours.
  2. The physical disks, virtual shared disks, external USB devices, and external optical drives of virtual machines do not support remote disaster recovery.

Prerequisite

  1. SCP platform admin must have configured the linkage for the primary and secondary sites and ensure stable connectivity between the cluster’s management interface.
  2. The tenant has sufficient backup repository quota and quota for disaster recovery virtual machines.

Steps

Navigate to Reliability > Disaster Recovery > DR Policy and click New to create a disaster recovery policy. Fill in the Name of the DR policy and select the Primary Site and Secondary Site. The Recovery Point Retention Method can be selected from recent one week, recent one month, or recent three months.

Configure Recovery Point Retention Method.

Select the virtual machines that need protection and click OK to complete the DR policy creation.

Configure the network for the disaster recovery standby virtual machine, click Configure Network, add the disaster recovery standby machine to the subnet, and configure the network according to actual needs (binding elastic IP or port mapping).

When the primary site is normal, and the virtual machine fails, local recovery can be performed: Go to the Recovery Plan page and click Recovery at Primary Site. It is recommended to select Create new virtual machine, configure the destination location, and click OK.

When the primary site requires planned maintenance or a disaster occurs, the disaster recovery data of the secondary site can quickly recover the virtual machine from the secondary site to provide services: Go to the Recovery Plan page, and click Recovery to Secondary Site, choose the Recovery Method according to the actual recovery scenario, you can check Power on VM upon recovery checkbox, configure the recovery location, and click OK.

After the primary site is recovered, the virtual machine can be migrated from the secondary site back to the primary site: Go to the Recovery Plan page, select the specific Recovery Plan Name and click Migrate to Primary Site, select the datastore for migration, and start migrating the virtual machine to the primary site. During the migration, the status will change to Waiting for Shutdown. At this time, you need to shut down the DR virtual machine manually and execute the migration task.