tencent cloud

TDSQL-C for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
Beginner's Guide
Product Introduction
Overview
Strengths
Use Cases
Architecture
Product Specifications
Instance Types
Product Feature List
Database Versions
Regions and AZs
Common Concepts
Use Limits
Suggestions on Usage Specifications
Kernel Features
Kernel Overview
Kernel Version Release Notes
Optimized Kernel Version
Functionality Features
Performance Features
Security Features
Stability Feature
Analysis Engine Features
Inspection and Repair of Kernel Issues
Purchase Guide
Billing Overview
Product Pricing
Creating Cluster
Specification Adjustment Description
Renewal
Payment Overdue
Refund
Change from Pay-as-You-Go to Yearly/Monthly Subscription
Change from Pay-as-You-Go to Serverless Billing
Value-Added Services Billing Overview
Viewing Billing Statements
Getting Started
Database Audit
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Logs
Log Shipping
Post-Event Alarm Configuration
Modifying Audit Rule
Modifying Audit Service
Disabling Audit Service
Audit Rule Template
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
Serverless Service
Serverless Introduction
Creating and Managing a Serverless Cluster
Elastic Scaling Management Tool
Serverless Resource Pack
Multi-AZ Deployment
Configuration Change
FAQs
Serverless Cost Estimator
Operation Guide
Operation Overview
Switching Cluster Page View in Console
Database Connection
Instance Management
Configuration Adjustment
Instance Mode Management
Cluster Management
Scaling Instance
Database Proxy
Account Management
Database Management
Database Management Tool
Parameter Configuration
Multi-AZ Deployment
GD
Backup and Restoration
Operation Log
Data Migration
Parallel Query
Columnar Storage Index (CSI)
Analysis Engine
Database Security and Encryption
Monitoring and Alarms
Basic SQL Operations
Connecting to TDSQL-C for MySQL Through SCF
Tag
Practical Tutorial
Classified Protection Practice for Database Audit of TDSQL-C for MySQL
Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS
Usage Instructions for TDSQL-C MySQL
New Version of Console
Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses
Strengths of Database Proxy
Selecting Billing Mode for Storage Space
Creating Remote Disaster Recovery by DTS
Creating VPC for Cluster
Data Rollback
Solution to High CPU Utilization
How to Authorize Sub-Users to View Monitoring Data
White Paper
Security White Paper
Performance White Paper
Troubleshooting
Connection Issues
Performance Issues
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Multi-Availability Zone APIs
Other APIs
Audit APIs
Database Proxy APIs
Backup and Recovery APIs
Parameter Management APIs
Billing APIs
serverless APIs
Resource Package APIs
Account APIs
Performance Analysis APIs
Data Types
Error Codes
FAQs
Basic Concepts
Purchase and Billing
Compatibility and Format
Connection and Network
Features
Console Operations
Database and Table
Performance and Log
Database Audit
Between TDSQL-C for MySQL and TencentDB for MySQL
Service Agreement
Service Level Agreement
Terms of Service
TDSQL-C Policy
Privacy Policy
Data Privacy and Security Agreement
General References
Standards and Certifications
Glossary
Contact Us
DocumentationTDSQL-C for MySQLServerless ServiceMulti-AZ DeploymentOverview of Multi-AZ Deployment

Overview of Multi-AZ Deployment

PDF
Focus Mode
Font Size
Last updated: 2025-12-25 17:11:53
TDSQL-C for MySQL offers both preset resources and Serverless cluster types, all supporting multi-availability zone deployment. Compared to single availability zone deployment, multi-availability zone deployment offers higher disaster recovery capabilities, ensuring database protection against instance failures or availability zone interrupts, and providing resilience against data center level failures. Multi-availability zone deployment enhances database instances with high availability and failover support. A multi-availability zone configuration involves combining multiple single availability zones within the same region into a physical zone. This article introduces multi-availability zone deployment for Serverless clusters. For information on multi-availability zone deployment with preset resources, please see Overview of Multi-availability zone Deployment.

Prerequisites

The cluster region has at least two AZs.
The target AZ has sufficient computing resources.
Database version requirements:
Database version 5.7 with kernel minor version 2.0.15 or later.
Database version 8.0 with kernel minor version 3.0.1 or later.

Supported Regions and AZs

Currently, this feature is in beta test and only supports the following regions and AZs.
This feature will gradually support more regions and AZs.
If your business requires it, you can Submit a Ticket to request deployment in other Regions and AZs.
Supported Region
Supported Primary AZ
Supported Secondary AZ
Beijing
Beijing Zone 3
Beijing Zone 5
Beijing Zone 5
Beijing Zone 7
Beijing Zone 6
Beijing Zone 7
Beijing Zone 8
Beijing Zone 7
Beijing Zone 5
Shanghai
Shanghai Zone 2
Shanghai Zone 4
Shanghai Zone 4
Shanghai Zone 2
Shanghai Zone 5
Shanghai Zone 4
Guangzhou
Guangzhou Zone 4
Guangzhou Zone 6
Guangzhou Zone 6
Guangzhou Zone 4
Guangzhou Zone 7
Guangzhou Zone 7
Guangzhou Zone 4
Hong Kong (China)
Hong Kong (China) Zone 2
Hong Kong (China) Zone 3
Nanjing
Nanjing Zone 1
Multi-AZ deployment is currently unavailable
Singapore
Singapore Zone 3
Singapore Zone 4
Singapore Zone 4
Singapore Zone 3
Silicon Valley
Silicon Valley Zone 2
Silicon Valley Zone 1
Virginia
Virginia Zone 1
Virginia Zone 2
Virginia Zone 2
Virginia Zone 1
Tokyo
Tokyo Zone 1
Tokyo Zone 2
Tokyo Zone 2
Tokyo Zone 1
Jakarta
Jakarta Zone 2
Jakarta Zone 1
Chengdu
Chengdu Zone 1
Multi-AZ deployment is not supported
Seoul
Seoul Zone 2
Multi-AZ deployment is not supported
Frankfurt
Frankfurt Zone 2
Frankfurt Zone 1
São Paulo
São Paulo Zone 1
Multi-AZ deployment is not supported
Bangkok
Bangkok Zone 2
Multi-AZ deployment is not supported

Multi-AZ Deployment Fee Description

There are no additional fees for the Multi-AZ Deployment feature for the time being.
Previous Topic: Requesting Refund for Resource PackNext Topic: Operations Related to Multi-AZ Deployment

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback