Primary/secondary failovers can be performed in the following scenarios: DR test, scheduled recovery, and DR.

DR test: Commonly used in DR drilling scenarios to verify the availability of services. After you select DR Test, the system generates connectionless VMs for drilling based on the latest backup data on the secondary site. This operation has no impact on the VMs running on the primary site or placeholder VMs.

Scheduled recovery: When you want to maintain the primary site that has VMs running on it, you can select Scheduled recovery to shut down the VMs on the primary site. Then, the VMs are recovered on the secondary site within the estimated time. Differentiated data is synced from the primary site to the secondary site during this process to avoid data loss. However, your services will experience a temporary disruption.

DR: When the primary site encounters a disaster, you can select Disaster recovery to start up placeholder VMs on the secondary site. Data that is not synced to the secondary site will be lost. In a Layer 2 VM network, if the VMs on the primary site are still active, the placeholder VMs running on the secondary site may encounter IP conflicts. Make sure that the network configuration of the primary and secondary sites will not cause IP conflicts before you start.