The disaster recovery plan feature was launched on August 15, 2019.
Prerequisites
You have completed relevant configurations for a Global Traffic Manager (GTM) instance, such as the instance creation, access policy configuration, address pool creation, health check, global settings, and CNAME access.
Features
Read features of disaster recovery plans based on the following figure.
1 . Create Disaster Recovery Plan
A disaster recovery plan helps you test the disaster recovery capabilities, and switch traffic when failures occur.
2 . Disaster Recovery Plan Name
You can enter an easy-to-identify name for the created disaster recovery plan, such as "fault drill test".
3 . Disaster Recovery Plan Description
You can enter remarks based on the created disaster recovery plan for easy memorization. For example, enter "switch from China Mobile to China Unicom".
4 . Fault Address Pools
To use a disaster recovery plan, you must configure a fault address pool. Then the system assumes that the configured address pools have failed and performs a failover based on the configured access policy.
5 . Run
After you create a disaster recovery plan, you must return to the Disaster Recovery Plan page and click Run in the Actions column. After you run the disaster recovery plan, all the addresses in the disaster recovery address pool are set to the Always Offline mode. The address pool becomes unavailable, and automatic failover is performed based on the configured access policy.
Note: Always Offline is an address working mode. For more information about how an address works, see Address pool configurations.
6 . Roll Back
After a disaster recovery drill or traffic switchover is completed, you can use the rollback feature to restore the original access policy. After you roll back the disaster recovery plan, the system sets all the addresses in the disaster recovery address pool to the Smart Return mode and restores the access policy.
Note: Smart Return is an address working mode. For more information about how an address works, see Address pool configurations.
7 . Preview
You can preview the access policy that will be executed for the disaster recovery plan.
Note: If the message "No access policies in this instance need to be switched" appears in the Preview Disaster Recovery Plan dialog box, you must click the instance on the Global Traffic Manager page, and check the access policy configuration on the Access Policy tab. For example, check whether Alternative Address Pool is set and whether Address Pool Switching Policy is set to Manual Switching.
8 . Edit
You can edit a created disaster recovery plan. You can only edit the disaster recovery plans that have not been run or have been rolled back. You can modify Disaster Recovery Plan Name, Disaster Recovery Plan description, and Fault Address Pools.
9 . Delete
You can delete a created disaster recovery plan.
Note: If you delete a disaster recovery plan that has been run, the access policy remains the executed policy, and the original access policy will not be restored.
Procedure
1 . Log on to the Alibaba Cloud DNS console.
2 . In the left-side navigation pane, click Global Traffic Manager. On the Global Traffic Manager page, click Disaster Recovery Plan.
3 . On the Disaster Recovery Plan page, click Create Disaster Recovery Plan.
4 . Enter an easy-to-identify name for the disaster recovery plan, set Fault Address Pools, and then click Complete.
5 . Return to the Disaster Recovery Plan page and click Run next to the disaster recovery plan.
6 . Return to the Global Traffic Manager page and click the instance. On the page that appears, click the Access Policy tab and view the execution result of the disaster recovery plan. The address pool has been switched to the alternative one, as shown in the following figure.
7 . Return to the Disaster Recovery Plan page and click Roll Back to restore the access policy.
8 . Return to the Global Traffic Manager page and click the instance. On the page that appears, click the Access Policy tab and view the rollback result of the disaster recovery plan. The address pool has been switched to the default one, as shown in the following figure.
