Release Notes
Product Announcements
Cross-Region Backup
This document describes the cross-region backup feature of TencentDB for MySQL. This feature allows you to store backup files in another region, which enhances the regulatory compliance and disaster recovery capabilities and improves the data reliability.
Background
Data is an important part of enterprise operations. Although the information technology brings convenience, 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 business interruptions 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 TencentDB for MySQL 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.
Notes on Cross-Region Backup
Cross-region backup feature is not supported currently for single-node cloud disk edition instances.
A cross-region backup can be restored to the instance regions or backup region.
Once enabled, cross-region backup doesn't affect the local default backup, and both coexist.
Cross-region backup will be triggered after the local automatic backup is completed, that is, the automatic backup will be dumped to the storage device for cross-region backup.
The retention period of cross-region backup only affects the backup cycle of the cross-region storage.
Backups and binlogs stored in a remote region cannot use the free storage space, and cross-region backups will use the space in the backup region of the source instance.
Enabling/disabling cross-region backup or changing the region won't affect existing backups.
After cross-region backup is enabled, the last valid backup and the binlogs generated from the last valid backup time to the current time will be synced to the target region.
If you enable cross-region backup again, remote backups generated before the enablement cannot be used to restore data to the specified time point.
Billing
Differences Between Cross-Region Backup and Local Default Backup
Comparison Item | Cross-Region Backup | Local Default Backup |
Enabled by default | No. It needs to be enabled manually. | Yes. |
Backup storage region | Up to two specified remote regions. | Instance region. |
Backup restoration | The data can be restored to: Original instance New instance in the target region | The data can be restored to: Original instance New instance in the current region |
Uses the free storage space | No. | Yes. |
Supported Regions
The regions currently supporting this feature are listed in the following table. This feature will be successively supported in other cities in the future.
Source region | Regions for cross-region backup |
Beijing, Shanghai, Guangzhou, Chengdu, Nanjing, Chongqing, Hong Kong (China), Singapore | Beijing, Shanghai, Guangzhou, Chengdu, Nanjing, Chongqing, Hong Kong (China), Singapore Note： Supports backup to regions other than the source region itself. The details are subject to the regions actually supported by the console. |
Jakarta, Bangkok, Seoul, Tokyo, Silicon Valley, Virginia, Frankfurt, Sao Paulo | Singapore |
Enabling Cross-Region Backup
1. Log in to the TencentDB for MySQL console. In the instance list, click an instance ID or Manage in the Operation column to enter the instance management page.
2. On the instance management page, select Backup and Restoration > Cross-Region Backup.
3. In the Cross-Region Backup window, complete the configuration and click OK to enable cross-region backup.
Cross-Region Backup: It is disabled by default.
Back up Binlog: When cross-region backup is enabled, it will be enabled automatically and can be disabled separately.
Backup Region: Select one or two regions other than the source instance region.
Backup Retention Period: 7 days by default. Value range: 3–1830 days. Backup sets will be deleted automatically upon expiration.
4. After cross-region backup is completed, the backup will be synced to the target region and can be queried in the backup list of the source instance.
For cross-region backup files, all selected backup regions are displayed in the Backup Region column.
The backup list has the following fields:
Field | Description |
File Name | You can set a filename when creating a backup, which cannot be modified after the backup is created. |
Backup Time | The backup start time. |
Task Start TimeTask End Time | The time points when the backup task starts and ends respectively. |
Backup Size | The size of the current backup file. |
Type | The backup file type. The cross-region backup type for two-node and three-node instances is physical cold backup, while the cross-region backup type for Cluster Edition instances is snapshot backup. |
Backup Mode | Automatic backup |
Backup Method | Full backup |
Backup Region | It displays all regions where the backup file is stored. |
Status | It displays the backup task status. |
Operation |
Disabling Cross-Region Backup
You can disable the cross-region backup feature in the console. After it is disabled, cross-region backup files won't be deleted immediately; instead, they will be deleted automatically upon expiration.
1. Log in to the TencentDB for MySQL console. In the instance list, click an instance ID or Manage in the Operation column to enter the instance management page.
2. On the instance management page, select Backup and Restoration > Cross-Region Backup.
3. In the Cross-Region Backup window, disable the feature and click OK.
FAQs
Why are fees still incurred after I disable cross-region backup?
If your data volume exceeds the free storage space, the excessive data will be billed. After cross-region backup is disabled, no more new backups will be generated, but existing backups won't be deleted immediately. They will be retained within the retention period and use the storage space before expiration, so they will still incur fees before expiration. You can set the backup retention period to automatically clear all expired backup files, and then no more cross-region backup fees will be incurred.
Help and Support
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback