Re-creating a DR Task After the Primary Instance Is Faulty

Scenarios

A DR relationship has been established with instance A as the primary instance and instance B as the DR instance. If primary instance A is faulty, you need to manually promote instance B to primary.

After instance A is recovered, re-establish a DR relationship between instance B and instance A and promote instance A to primary again.

Procedure

1. If the primary instance A is faulty, log in to the console, select the region where the DR instance B is deployed, promote instance B to primary by referring to Promoting the DR Instance to Primary, and enable Re-establish DR Relationship.
   

   In this case, instance B takes over the role of instance A to provide services.

2. Log in to the console, select the region where instance B is located, and re-establish a DR relationship by referring to Re-establishing a DR Relationship.
3. After the fault of instance A is rectified, switch roles of instance A and instance B by referring to Switching Roles of Primary and DR Instances.

   In this case, the services are taken over by instance A and the DR relationship is restored to the status before the fault occurs.

   

   Instance A provides services. You need to switch services to instance A.