Operational flow

Operational flow

You can protect key applications in the Hybrid Disaster Recovery console. The main steps are as follows:

• Step 1: Resource planning.

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

• Step 2: Create a disaster recovery site pair.

  Prepare a VPC and a vSwitch for the disaster recovery site and configure their CIDR blocks. For testing, you can use the default configurations to create the VPC and vSwitch. You can also set the CIDR blocks of the disaster recovery site to match those of the production site. For production environments, configure the CIDR blocks as required.

• Step 3: Configure network and security settings.

  Map resources, such as network zones, vSwitches, and security groups.

• Step 4: Create a protection group.

• Step 5: Add protected instances.

  Add the instances that you want to protect.

• Step 6: Start replication.

  Start replication to begin disaster recovery protection. This process copies data from the production site to the disaster recovery site.

  Note

  You can perform a failover drill when the protection group is in the Replicating Incrementally state or after a recovery point is created. For more information, see Failover Drill.

• Step 7: Failover

  • Failover after data synchronization

    This failover pattern first stops the protected instances in the protection group. It waits for all instances to stop before performing a final round of data synchronization. The failover starts after the synchronization is complete. This process ensures that data on the disaster recovery site is identical to the production site, resulting in zero data loss. This pattern is suitable for scenarios such as planned disaster recovery drills and service migration.

  • Switch Now

    This failover pattern attempts to stop the protected instances in the protection group. It does not wait for all instances to stop and does not perform a final data synchronization. This results in some data loss within the Recovery Point Objective (RPO) range. This pattern is suitable for scenarios that require an immediate failover to the disaster recovery site, such as when the production site fails and cannot be recovered quickly.