Cloud Backup:Procedure

Procedure

To implement disaster recovery protection for critical applications in the Cloud Backup console, perform the following steps:

• Step 1: Plan resources.

  Before you perform disaster recovery, you must plan the required compute, network, and storage resources. You must determine the number of servers, storage capacity, and virtual private clouds (VPCs).

• Step 2: Create a disaster recovery site pair.

  Create VPCs and vSwitches for the disaster recovery site, and configure CIDR blocks. During the test, you can use the default configurations to create VPCs and vSwitches. You can also configure the same VPC CIDR block and vSwitch CIDR block for the production site and the disaster recovery site. During actual disaster recovery, you can configure CIDR blocks as required.

• Step 3: Configure network and security settings.

  Create resource mappings, including the zone mapping, vSwitch mapping, and security group mapping.

• Step 4: Create a protection group.

• Step 5: Add protected instances.

  Add instances to be protected.

• Step 6: Start replication.

  Start disaster recovery protection, a process of replicating data from the production site to the disaster recovery site.

  Note

  You can perform a fault drill if the protection group is in Incremental Replication status or has a recovery point. For more information, see Fault drill.

• Step 7: Perform a failover.

  • Switch After Data Synchronization

    During the failover, Cloud Backup stops the protected instances in the protection group, and performs the final data synchronization after all the protected instances are stopped. The failover starts after the data is synchronized. This ensures that the data at the disaster recovery site is the same as that at the production site. This type of failover applies to scenarios such as planned fault drills and business migration.

  • Switch Now

    During the failover, Cloud Backup attempts to stop the protected instances in the protection group. Cloud Backup does not wait until all the protected instances are stopped or perform the final data synchronization. Some data may be lost within the recovery point objective (RPO) range. This type of failover applies to scenarios where a fault cannot be rectified within a short period of time at the production site and business must be immediately switched to the disaster recovery site.