This topic describes how to back up an ApsaraDB RDS for MySQL instance by using the cross-region backup feature. This feature allows ApsaraDB RDS to replicate the backup files of your RDS instance from the source region to a specified destination region. The destination region is different from the source region where the original RDS instance resides. You can use the backup files in the destination region to manage and restore your RDS instance. In this case, your RDS instance is known as the original RDS instance.
Prerequisites
- MySQL 8.0 on RDS High-availability Edition (with local SSDs)
- MySQL 5.7 on RDS High-availability Edition (with local SSDs)
- MySQL 5.6
Background information
You can use a cross-region backup file of the original RDS instance to restore data to an existing or new RDS instance that resides in the destination region. For more information, see Restore the data of an ApsaraDB RDS for MySQL instance across regions.
Differences between the cross-region backup feature and the default backup feature
- By default, the cross-region backup feature is disabled, and the default backup feature is enabled. If you require the cross-region backup feature, you must manually enable this feature.
- Cross-region backup files are stored in the destination region. Default backup files are stored in the source region.
- Cross-region backup files can be restored to a new or existing RDS instance in the source or destination region. Default backup files can be restored to the original RDS instance or a new RDS instance in the source region.
- Cross-region backup files are independent of the original RDS instance. If you release the original RDS instance, cross-region backup files are still retained based on the specified retention period. However, default backup files are retained only for seven days.
Billing
- Remote storage: USD 0.0002/GB/hour.
- Traffic consumption: For more information, see Billing methods and billing items.
Precautions
- You can restore data from cross-region backup files to the source or destination region. However, if transparent data encryption (TDE) is enabled, you can restore data from these files only to the source region. For more information, see Configure TDE for an ApsaraDB RDS for SQL Server instance.
- Cross-region backups do not interrupt default backups. These two types of backups can be used at the same time.
- After a default backup is complete, the original RDS instance triggers a cross-region backup. This allows the original RDS instance to dump the generated default backup files to the destination region.
- After you enable the cross-region backup feature, the original RDS instance checks whether a valid data backup file is generated over the last 24 hours. If no valid data backup files are generated over the last 24 hours, the original RDS instance triggers a backup on its secondary RDS instance.
- After you enable the cross-region log backup feature, the original RDS instance checks
whether a valid data backup file is generated over the last 24 hours.
- If continuous binary log files are generated following the valid data backup file, the original RDS instance dumps the binary log files to the destination region.
- If no continuous binary log files are generated following the valid data backup file, the original RDS instance triggers a backup on its secondary RDS instance.
- The cross-region backup feature is not supported in some regions due to network issues.
The following table lists the regions in which the cross-region backup feature is
supported.
Source region Destination region China (Hangzhou) China (Shanghai), China (Qingdao), China (Shenzhen), China (Zhangjiakou), and China (Hohhot) China (Shanghai) China (Hangzhou), China (Qingdao), China (Shenzhen), China (Zhangjiakou), and China (Hohhot) China (Qingdao) China (Hangzhou), China (Shanghai), China (Shenzhen), China (Zhangjiakou), and China (Hohhot) China (Beijing) China (Hangzhou), China (Shanghai), China (Qingdao), China (Shenzhen), China (Zhangjiakou), and China (Hohhot) China (Zhangjiakou) China (Hangzhou), China (Shanghai), China (Qingdao), China (Shenzhen), and China (Hohhot) China (Hohhot) China (Hangzhou), China (Shanghai), China (Qingdao), China (Shenzhen), and China (Zhangjiakou) China (Shenzhen) China (Hangzhou), China (Shanghai), China (Qingdao), China (Zhangjiakou), and China (Hohhot) China (Hong Kong) China (Hangzhou), China (Shanghai), China (Qingdao), China (Shenzhen), China (Zhangjiakou), and China (Hohhot) US (Silicon Valley) US (Virginia) US (Virginia) US (Silicon Valley) China East 1 Finance China East 2 Finance and China South 1 Finance China East 2 Finance China East 1 Finance and China South 1 Finance China South 1 Finance China East 1 Finance and China East 2 Finance
Enable the cross-region backup feature for an RDS instance
Enable the cross-region backup feature for multiple RDS instances at a time
Modify the cross-region backup settings of an RDS instance
A menu item named Cross-region Backup is added to the homepage of the ApsaraDB RDS console. You can modify the cross-region backup settings of an RDS instance even after the instance is released.
Disable the cross-region backup feature for an RDS instance
If you do not require the cross-region backup feature, you can perform the following steps to disable this feature:
FAQ
After I disable the cross-region backup feature for my RDS instance, why am I still charged for cross-region backup files?
After you disable the cross-region backup feature for your RDS instance, no new cross-region backup files are generated. In addition, you are no longer charged for the traffic that is consumed for these cross-region backup files. However, you must still pay for the storage of the existing cross-region backup files within the specified retention period. The existing cross-region backup files are retained for at least seven days. You can set the retention period to seven days. For more information, see the "Modify the cross-region backup settings of an RDS instance" section of this topic. After the specified retention period elapses, all of the existing cross-region backup files are deleted and you are no longer charged for the storage of these cross-region backup files.
Related operations
Operation | Description |
---|---|
Check whether an ApsaraDB for RDS instance can be restored across regions | Checks whether an ApsaraDB RDS instance has a cross-region backup set that can be used to restore data. |
Restore data to a new instance across regions | Restores the data of an ApsaraDB RDS instance to a new RDS instance that resides in a different region than the original RDS instance. |
Modify cross-region backup settings | Modifies the cross-region backup settings of an ApsaraDB RDS instance. |
Query cross-region backup settings | Queries the cross-region backup settings of an ApsaraDB RDS instance. |
Query cross-region data backup files | Queries the cross-region data backup files of an ApsaraDB RDS instance. |
Query cross-region log backup files | Queries the cross-region log backup files of an ApsaraDB RDS instance. |
Query regions that support cross-region backup | Queries the regions to which the cross-region backup files from the current region can be restored. |
Query the time range to which you can restore data by using a cross-region backup set | Queries the restorable time range that is supported by a cross-region backup file. |
Query ApsaraDB for RDS instances on which cross-region backup is enabled | Queries the ApsaraDB RDS instances for which the cross-region backup feature is enabled in a region and the cross-region backup settings of these instances. |