TDSQL-C for MySQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Suggestions on Usage Specifications
- Kernel Features
- Kernel Version Release Notes
- Optimized Kernel Version
- Functionality Features
- Performance Features
- Security Features
- Stability Feature
- Analysis Engine Features
- Purchase Guide
- Value-Added Services Billing Overview
- Database Audit
- Audit Rule Template
- Serverless Service
- Serverless Introduction
- Serverless Resource Pack
- Configuration Change
- Operation Guide
- Database Connection
- Configuring Network Address
- Instance Management
- Configuration Adjustment
- Instance Mode Management
- Cluster Management
- Scaling Instance
- Database Proxy
- Database Proxy Kernel Features
- Managing Database Proxy
- Automatic Read/Write Separation
- Connection Pool Feature
- Other Features
- Account Management
- Console Account
- Database Account
- Configuring Custom Password Strength
- Database Management
- Database Management Tool
- Columnar Storage Index (CSI)
- Utilization of Columnar Storage Indexes
- Read-Only Analysis Engine
- Feature Limits and Compatibility
- Description of Functions and Operators
- Read-Only Analysis Engine Management
- Data Loading
- Executing Queries
- Exclusive Features
- Performance Optimization
- Performance White Paper
- Parameter Configuration
- Multi-AZ Deployment
- Backup and Restoration
- Performing Backup
- Managing Backup
- Rollback
- Restoring Data from Logical Backups
- Restoring Data Through the Console
- Restoring Data from Snapshot Backup
- Data Migration
- Parallel Query
- Setting Parallel Query
- Database Security and Encryption
- Access and Authorization
- Security Group Management
- TencentDB Security Group Management
- Monitoring and Alarms
- Monitoring
- Alarms
- Monitoring Metric Alarm
- Practical Tutorial
- Data Rollback
- Database/Table-Level Rollback
- Rolling back Entire Cluster
- White Paper
- Security White Paper
- Performance White Paper
- Troubleshooting
- Connection Issues
- API Documentation
- Making API Requests
- Instance APIs
- Account APIs
- Audit APIs
- Database Proxy APIs
- Backup and Restoration APIs
- Parameter Management APIs
- Performance Analysis APIs
- Serverless APIs
- ResourcePackage APIs
- Other APIs
- FAQs
- Service Agreement
- TDSQL-C Policy
- General References
DocumentationTDSQL-C for MySQLOperation GuideBackup and RestorationPerforming BackupCross-Region Backup
Cross-Region Backup
Last updated: 2024-11-15 14:24:11
Cloud Native Database TencentDB for CynosDB provides a cross-region backup function, enabling users to store backup files in a different region for storage to enhance regulatory compliance and disaster recovery ability and improve data reliability. Currently, TencentDB for CynosDB cluster supports cross-region backup settings for automatic logical backup, binlog backup, and manual logical backup (for the entire cluster).
This article presents the function of cross-region backup.
Background
Data is an important part of enterprise operations. Although the information technology brings convenience, it also reveals that electronic data and stored information are very vulnerable to damage or loss. Any incident, such as natural disaster, system failure, maloperation, or virus, can cause interruption of business operations or even disastrous losses. Therefore, ensuring the security and integrity of core data is a top priority of every enterprise. The cross-region backup feature of Cloud Native Database TencentDB for CynosDB can be used to store backup files in another region so as to minimize data corruptions caused by natural disasters or system failures. This feature ensures the high availability, security, and recoverability of data and implement various features, such as remote backup and restoration, remote disaster recovery, long-term data archive, and regulatory compliance.
Cross-Region Backup Limitations
Currently, only high IO edition clusters support cross-region backup capabilities in automatic logical backup, binlog backup, and manual logical backup (for the entire cluster).
Notes on Cross-Region Backup
Cross-region backup can restore data to the region where the cluster or the backup is.
Cross-region backup doesn't affect the local default backup, and both coexist after cross-region backup is enabled.
Cross-region backup will be triggered after the local default automatic backup is complete, that is, the default automatic backup is dumped to the storage device for cross-region backup.
Billing Description
Cross-region backup is currently in the public testing phase, and is presently available for use without charge.
The Difference between Cross-region Logical Backup and Local Automatic Backup
Comparison Item | Cross-Region Logical Backup | Local Automatic Backup |
Is it enabled by default | It is disabled by default and requires manual enabling. | Enabled by default |
Backup storage region | Backup is stored in the specified remote region (up to three regions) | Backup is stored in the region where the cluster is located |
Backup and restoration | Data can be restored to: Original cluster New cluster in the target region | Can be restored to: Original cluster New cluster in the current region |
Supported Regions
The regions supporting cross-region backup span all the regions in TencentDB for CynosDB.
Enabling Cross-Region Backup for Automatic Logical Backup
Note:
After the enabling of cross-region backup of automatic logical backup, it is recommended to synchronously enable the Binlog cross-region backup for the corresponding regions, providing convenience for time point recovery in the corresponding regions.
1. Log in to the TencentDB for CynosDB console.
2. At the top, select a region and operate according to the console view pattern currently in use.
On the left side of the cluster list, click Target Custer to enter the cluster management page.
Find the target cluster in the cluster list on the left and click the cluster ID or Manage in the Operation column to access the cluster management page.
3. On the cluster management page, select Backup Management tab, then click Auto-Backup Settings.
4. Under Logical Backup, click Modify Backup Settings.
Note:
If you have enabled automatic logical backup, but have not activated the cross-region backup feature for automatic logical backup, please click on Modify Backup Settings.
5. In the pop-up dialog box, finish the following configuration, then click OK.
Parameter | Description |
Start time | Set the daily start time of automatic logical backup. Set by default from 02:00 to 06:00. |
Auto-Backup Cycle | Daily is set by default. Note: The current version only supports an automatic backup cycle being daily. Due to logical backup speed limitations, the backup cycle for some larger data volume clusters is expected to extend to more than a day (if the logical backup for that day is not completed, the next automatic logical backup will not occur until the day after this logical backup is completed). |
Cross-Region Backup | Select to enable cross-region backup. |
Backup Region | Choose the regions for backup storage, supporting up to three different regions. |
Automatic Backup Retention | Backups can be retained from 7 to 1830 days. |
Enabling Cross-Region Backup of binlog Backup
1. Log in to the TencentDB for CynosDB console.
2. At the top, select the region and operate according to the console view pattern currently in use.
On the left side of the cluster list, click on the desired cluster to enter the cluster management page.
Find the target cluster in the cluster list on the left and click Cluster ID or Manage in Operation column to access the cluster management page.
3. On the cluster management page, select the Backup Management tab and click Log Backup Settings.
4. In the pop-up dialog box, complete the following configuration and click OK.
Parameter | Description |
Binlog Settings | Enabled by default. |
Binlog Backup Retention | Binlog backup retention period lasts 7 to 1,830 days, which must not be less than the data backup retention period of 7 days. |
Cross-Region Backup | Select if the cross-region backup should be enabled. If it is activated, binlog backups can be stored in other regions. If it is not activated, binlog backups will be kept in the region where the cluster is currently located by default. |
Backup Region | When enabling cross-region backup, you can select the region where the backup is stored, supporting up to three different regions. |
Enabling Manual Logical Cross-Region Backup
1. Log in to the TencentDB for CynosDB console.
2. At the top, select the region and operate according to the console view pattern currently in use.
On the left side of the cluster list, click the desired cluster to enter the cluster management page.
Find the target cluster in the cluster list on the left and click Cluster ID or Manage in Operation column to access the Cluster Management page.
3. On the cluster management page, click Backup Management and then click Manual Backup.
4. In the pop-up dialog box, complete the following configuration, then click OK to create a backup task.
Parameter | Description |
Backup Type | Choose logical backup. Note: We recommend you perform a manual logical backup task during off-peak hours, as it will lock the database and affect database use. |
Object | In manual backup, the capacity for cross-region backup is currently only supported for selecting the entire cluster for cross-region backup. |
Alias | When a manual backup is created, the settings of the remark name for the backup file is supported. Only digits, English upper case and lower case letters, Chinese as well as special characters -_./()[]()+=:;@ are supported and the length cannot exceed 60. |
Cross-Region Backup | Choose to enable cross-region backup. After that, you can save manual logical backups to other regions. |
Backup Region | Choose the region where the manual logical backup is stored; Up to three different regions can be selected. |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No