Multi-zone clusters provide higher disaster recovery capabilities than single-zone clusters, and can withstand data center-level failures. By switching to multi-zone deployment, AnalyticDB for MySQL replicates your data across two zones and automatically fails over to the secondary zone if the primary zone becomes unavailable—keeping your cluster running without manual intervention.
Prerequisites
Before you begin, make sure that:
The cluster's product series is Enterprise Edition or Data Lakehouse Edition
The cluster's disk performance level is PL0 or PL1
What happens during the change
The configuration change happens in two phases:
Phase 1 — Node rebuild: The system remounts a regional Enterprise SSD (ESSD) and rebuilds nodes. How long it takes depends on your data volume. During this phase, query and write operations may experience slight jitter.
Phase 2 — Switchover: After the rebuild completes, the system switches traffic from old nodes to new ones. This switchover takes approximately 5 to 10 minutes. During this window, read and write operations are unavailable.
To minimize disruption, run the change during off-peak hours. Alternatively, set a specific time window for the switchover using the following SQL statement (in this example, the window is 23:00 to 23:30):
SET adb_config REPLICATION_SWITCH_TIME_RANGE=`23:00, 23:30`;After the switchover completes, the cluster operates in multi-zone mode. If the primary zone fails, the cluster workloads are automatically switched to the secondary zone. During the switchover, the cluster may be unavailable for read and write operations.
Billing impact
After the change, hot data storage is billed at the regional ESSD rate, which is 1.5 times the price of PL1 disks. If you also modify the reserved resource node specifications or node count on the Change Configuration page, those costs change as well.
For pricing details, see Enterprise Edition and Basic Edition pricing and Data Lakehouse Edition pricing.
Change the deployment mode
Log on to the AnalyticDB for MySQL console. In the upper-left corner, select the region where your cluster is located. In the left-side navigation pane, click Clusters.
On the Clusters page, find the target cluster and click Scale Down in the Actions column.
On the Change Configuration page, set the following parameters:
Parameter Description Change type Fixed as Same Version Change. Version The product series of your cluster: Enterprise Edition or Data Lakehouse Edition. Deployment mode Select Multi-zone Deployment. Primary Zone Select the zone where your cluster currently runs. Primary Zone vSwitch Select a virtual private cloud (VPC) and vSwitch for the primary zone. If you already have a VPC that meets your requirements, select it. To use the default network, see Default VPCs and default vSwitches. To create a custom VPC, see Create and manage a VPC. Secondary Zone Select the zone for automatic failover. If the primary zone fails, the cluster switches workloads to this zone. Secondary Zone vSwitch Select a VPC and vSwitch for the secondary zone, using the same criteria as the primary zone. Reserved resource node specifications Defaults to the cluster's current node specifications. Change this only if the current specifications no longer meet your requirements. Number of reserved resource nodes Defaults to the cluster's current node count. Adjustments are made in increments of 3. Disk performance level Fixed as Zone-redundant ESSD. Complete the purchase:
Subscription clusters: Accept the Service Agreement, click Buy Now, confirm the order and payment method, then click Buy Now again.
Pay-as-you-go clusters: Accept the Service Agreement, then click Buy Now.
After you submit the change, monitor progress on the Cluster List page or the Task Hub page in the console.
What's next
For details on how automatic failover works after multi-zone deployment is enabled, see Cross-zone disaster recovery.