Use async replication in the Cloud Backup console to protect ECS workloads. This topic lists 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:
Plan resources.
Plan the required compute, network, and storage resources: number of servers, storage capacity, and VPCs.
Create a disaster recovery site pair.
Create VPCs and vSwitches for the disaster recovery site and configure CIDR blocks. For testing, use default configurations or the same VPC and vSwitch CIDR blocks as the production site. For actual disaster recovery, configure CIDR blocks as required.
Configure network and security settings.
Create resource mappings: zone mapping, vSwitch mapping, and security group mapping.
Create a protection group.
Add protected instances.
Add the instances to be protected.
Start replication.
Start disaster recovery protection to replicate data from the production site to the disaster recovery site.
NotePerform a fault drill when the protection group is in Incremental Replication status or has a recovery point. See Fault drill.
Perform a failover.
Switch after data synchronization
Cloud Backup stops protected instances, performs final data synchronization, then starts the failover. Data at the disaster recovery site matches the production site. Use for planned fault drills and business migration.
Switch now
Cloud Backup attempts to stop protected instances and does not wait for full synchronization. Some data within the RPO may be lost. Use when the production site cannot be restored quickly and you must switch to the disaster recovery site immediately.