Procedure

Use async replication in the Cloud Backup console to protect ECS workloads. This topic covers the end-to-end procedure: plan resources, create a site pair, configure mappings, create a protection group, add instances, start replication, and perform a failover.

Implement disaster recovery protection for critical applications in the Cloud Backup console by completing the following steps:

1. Plan resources.

   Determine the compute, network, and storage resources for the disaster recovery site: the number of servers, storage capacity, and VPCs.

2. Create a disaster recovery site pair.

   Create VPCs and vSwitches for the disaster recovery site and set CIDR blocks. For testing, use the default configurations or the same VPC and vSwitch CIDR blocks as the production site. For actual disaster recovery, configure CIDR blocks as required.

3. Configure network and security settings.

   Create zone mapping, vSwitch mapping, and security group mapping between the production site and the disaster recovery site.

4. Create a protection group.

5. Add protected instances.

   Add the ECS instances to be protected to the protection group.

6. Start replication.

   Start disaster recovery protection to replicate data from the production site to the disaster recovery site. When the protection group reaches Incremental Replication status or has a recovery point, replication is active and the protection group is ready for a fault drill or failover.

   Note

   Perform a fault drill when the protection group is in Incremental Replication status or has a recovery point. See Fault drill.

7. Perform a failover.

   • Switch after data synchronization

     Cloud Backup stops protected instances, completes a final data synchronization, then initiates the failover. The disaster recovery site is fully consistent with the production site at the moment of switch. Use this option for planned fault drills and scheduled business migrations.

   • Switch now

     Cloud Backup attempts to stop protected instances and initiates the failover immediately, without waiting for a final sync. Some data within the RPO may be lost. Use this option when the production site cannot be restored quickly and you must switch to the disaster recovery site immediately.