Cross-zone disaster recovery protects your AnalyticDB for PostgreSQL instance against zone-level failures by deploying primary and secondary nodes across two zones in the same region. If the primary zone becomes unavailable due to a natural disaster or instance failure, the secondary zone nodes automatically take over as the primary nodes to ensure business continuity. Primary and secondary nodes share the same storage capacity.
How it works
The instance exposes a single endpoint that connects to the primary zone nodes only. Secondary zone nodes serve as standby replicas and do not accept external connections.
Supported versions
Cross-zone disaster recovery requires a High-availability Edition instance running one of the following versions:
V6.6.2.10 or later
V7.1.1.0 or later
To check your instance's minor version, see View the minor version of an instance. If your instance does not meet the version requirements, update the minor version before proceeding.
Supported primary zones
Cross-zone disaster recovery is available only for instances in the following zones. The zone you select when creating an instance becomes the primary zone. When enabling the feature, you select only the secondary zone.
| Region | Zone | Supported |
|---|---|---|
| China (Hangzhou) | Zone H | Yes |
| China (Hangzhou) | Zone I | Yes |
| China (Hangzhou) | Zone J | Yes |
| China (Shanghai) | Zone F | Yes |
| China (Shanghai) | Zone G | Yes |
| China (Shanghai) | Zone L | No |
| China (Shanghai) | Zone M | Yes |
| China (Shanghai) | Zone N | Yes |
| China (Beijing) | Zone G | Yes |
| China (Beijing) | Zone H | Yes |
| China (Beijing) | Zone I | Yes |
| China (Zhangjiakou) | Zone B | Yes |
| China (Zhangjiakou) | Zone C | Yes |
| China (Hohhot) | Zone A | Yes |
| China (Hohhot) | Zone B | Yes |
| China (Ulanqab) | Zone B | Yes |
| China (Ulanqab) | Zone C | Yes |
| China (Shenzhen) | Zone A | Yes |
| China (Shenzhen) | Zone E | Yes |
| China (Shenzhen) | Zone F | Yes |
| China (Chengdu) | Zone A | No |
| China (Hong Kong) | Zone C | No |
| Japan (Tokyo) | Zone B | No |
| Singapore | Zone A | Yes |
| Singapore | Zone B | Yes |
| Singapore | Zone C | No |
| Malaysia (Kuala Lumpur) | Zone A | Yes |
| Malaysia (Kuala Lumpur) | Zone B | Yes |
| Indonesia (Jakarta) | Zone A | No |
| Germany (Frankfurt) | Zone A | No |
| UK (London) | Zone A | No |
| US (Virginia) | Zone A | Yes |
| US (Virginia) | Zone B | Yes |
| US (Silicon Valley) | Zone A | Yes |
| US (Silicon Valley) | Zone B | Yes |
| South Korea (Seoul) | Zone A | No |
| Thailand (Bangkok) | Zone A | No |
| SAU (Riyadh - Partner Region) | Zone A | Yes |
| SAU (Riyadh - Partner Region) | Zone B | Yes |
Billing
After you enable cross-zone disaster recovery, computing resource fees are charged at twice the original rate. Storage resource fees remain unchanged. For the exact cost impact, see the configuration change page of your instance.
Enable cross-zone disaster recovery
During the enabling process, your instance may be temporarily unavailable for approximately 20 minutes. Enable it during off-peak hours.
Log on to the AnalyticDB for PostgreSQL console. In the upper-left corner, select a region. Find the target instance and click its ID.
In the upper-right corner of the Basic Information page, choose Manage Instance > Enable Multi-zone Deployment.
In the Enable Multi-zone Deployment message, click OK.
On the Upgrade/Downgrade page, click Enable next to Multi-zone Deployment. Select the secondary zone and secondary zone vSwitch.
Read and select the Terms of Service, then click Buy Now.
View the primary and secondary zones
Log on to the AnalyticDB for PostgreSQL console. In the upper-left corner, select a region. Find the target instance and click its ID.
On the Basic Information page, check the Instance Region and Zone parameter.
FAQ
What does the Current primaryZoneId and standbyZoneId do not support multi az, please reselect error mean?
Your instance's primary zone does not support cross-zone disaster recovery with the secondary zone you selected. Select a different secondary zone and try again. For the list of supported zones, see Supported primary zones.