Scenario
Multi-Availability Zones (Multi-AZ) are physical regions formed by combining multiple single-Availability Zones (single-AZ) within the same geographical area. Compared to single-AZ clusters, Multi-AZ clusters offer higher disaster recovery capabilities to protect against database instance failures or AZ interruptions, mitigating data center-level faults. Upgrading existing single-AZ clusters to Multi-AZ clusters can be automatically accomplished through online data migration, without any impact on your business operations.
Billing description
The multi-AZ feature is currently available free of charge; that is, a single-AZ deployed cluster can be upgraded to a multi-AZ one for free.
Usage Limits
This feature is currently unavailable in Shenzhen Finance, Jakarta, and Mumbai regions and will be available in more regions and AZs in the future.
Instructions for Use
Without the need for the Read Local Nodes Only feature, upgrading to Multi-AZ only involves the migration of management metadata and has no impact on services. In most cases, the upgrade can be completed within 3 minutes.
To support the Read Local Nodes Only feature, you need to upgrade the Proxy version and Redis kernel minor version, which involves data migration and may take several hours. Within the last 3 minutes of the upgrade, there may be one or multiple momentary disconnections. Please ensure your business has an automatic reconnection mechanism in place.
Preparations
The cluster region has at least two AZs.
The database is on v4.0 or later.
The instance is in Running status.
Instructions
1. Log in to the TencentDB for Redis® console.
2. Above the Instance List on the right, select the region.
3. In the instance list, find the target instance.
4. In the row of the target instance, click the Instance ID in blue font to enter the Instance Details page.
5. In the Basic Info section of the Instance Details page, click Upgrade to Support Multi-AZ Deployment after AZ.
6. In the Upgrade to Support Multi-AZ Deployment dialog box, learn about the impact of upgrading the AZ, confirm whether the Proximity Access feature is supported, and click OK.
7. In the Basic Info section, wait for the Instance Status to change to Upgrading to Support Multi-AZ Deployment and then to Running to complete the operation.
Note:
After upgrading to a multi-AZ instance, you need to manually adjust the replica's AZ to deploy the primary and replica nodes in different AZs. For details, see Adding Replicas to Multi-AZ Deployed Instance.
Related APIs
API Name | Description |
Upgrades an instance to support multi-AZ deployment |