ApsaraDB RDS for MySQL provides the cross-region backup (geo-redundancy) feature, which automatically replicates backups to a different region. You can use this feature to meet compliance requirements or for disaster recovery.
Cross-region backup vs. default backup
Item | Cross-region backup | Default backup |
Enabled by default | No. You must enable it manually. | Yes. |
Backup storage | Stored in a different region. | Stored in the same region as the instance. |
Data restoration | You can restore data to:
Note For MySQL instances that use cloud disks, you can restore data only to a new instance in the destination region. | You can restore data to: |
Backup retention period | Instances with Premium Local SSDs: After an instance is released, its cross-region backup data is retained based on the configured retention policy. Storage fees are incurred for the retained backup sets, but no network traffic fees are generated. In this case, you can perform the following operations: Cloud disk instances: After the instance is released, existing cross-region backup data is not retained and no charges apply.
| By default, backups are retained for 7 days after the instance is released. |
Note Cross-region backup and restoration data is transferred over a virtual private cloud (VPC) for non-cross-border scenarios and over the public internet for cross-border scenarios.
Procedure
Select the tab that corresponds to your instance's storage type for specific features and instructions.
Cloud disk instances
Prerequisites
The ApsaraDB RDS for MySQL instance must meet the following requirements:
Major engine version: 8.0 or 5.7
Edition: Basic, High-availability, or Cluster
Storage type: cloud disk (Serverless instances are not supported)
Note You can view this information on the Basic Information page of the instance.
If this is your first time using the RDS backup service, you must authorize the service-linked role for Data Disaster Recovery.
Billing
For a cloud disk instance, cross-region backups created in the ApsaraDB RDS console incur the following fees:
Billable item | Destination region | Unit price(USD/GB/day) |
Geo-redundant storage fee | China (Beijing), China (Hohhot), China (Ulanqab), China (Hangzhou), China (Shanghai), China (Shenzhen), China (Heyuan), China (Chengdu), China (Qingdao), China (Guangzhou), and China (Zhangjiakou) | 0.0009375 |
China (Hong Kong), US (Silicon Valley), US (Virginia), Singapore, Japan (Tokyo), Germany (Frankfurt), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila), UK (London), South Korea (Seoul), and Thailand (Bangkok) | 0.001125 |
Network traffic fee | For region-specific pricing details, see Network fees. |
Note For large amounts of data, we recommend using a DBS network plan to offset network fees.
Considerations
When using the cross-region backup feature in the ApsaraDB RDS console, note the following:
You can back up data only to a region other than the source region. You cannot restore data to the source region.
Cross-region backup does not affect the default backup feature. Both can be active simultaneously, as cross-region backup works by copying local backups to another region.
After a default backup completes, the system copies it to the destination region for cross-region backup.
Enabling cross-region backup does not create a new backup schedule; it only copies backups created by your existing default backup policy.
After you enable cross-region log backup, the system copies only log files generated after the feature is enabled.
You cannot download cross-region data backup sets or log backup sets of cloud disk instances.
Supported backup routes and regions
Due to network limitations, the cross-region backup feature is available only in specific regions.
Supported backup routes | Data backup is supported between regions in the Chinese mainland, China (Hong Kong), and other regions. The destination region must be different from the source region. |
Supported regions | Chinese mainland: China (Beijing), China (Shanghai), China (Hangzhou), China (Shenzhen), China (Qingdao), China (Guangzhou), China (Ulanqab), China (Heyuan), China (Chengdu), China (Hohhot), and China (Zhangjiakou) China (Hong Kong) Other regions: US (Silicon Valley), US (Virginia), Singapore, Japan (Tokyo), Germany (Frankfurt), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila), UK (London), South Korea (Seoul), and Thailand (Bangkok)
|
Procedure
Enable cross-region backup
Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region in which your RDS instance resides.
Go to the target instance. On the Backup and Restoration page, go to the Backup Strategy tab. Find the Cross-region Backup Settings option and click Edit.
Note If the Cross-region Backup Settings option is not displayed, verify that the instance meets the prerequisites.
Configure the following parameters.
Parameter | Description |
Cross-region Backup | The primary switch for cross-region backup. Select Enable. |
Backup Region | The region where backups are stored. Local backup files are automatically replicated to this region. |
Cross-Region Backup Retention | The retention period of cross-region backup files. Valid values: 7 to 1825 days. The maximum retention period is five years.
Note For a cloud disk instance, after the instance is released, existing cross-region backup data is not retained and no charges apply. |
Cross-region Log Backup | The switch for cross-region log backup. When enabled, local log backup files are automatically replicated to an OSS bucket in the destination region. |
Read and select the billing description and the data cross-border compliance commitment, and click OK.
Modify cross-region backup settings
Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region in which your RDS instance resides.
Go to the target instance, and on the Backup and Restoration page > Backup Strategy tab, find the Cross-region Backup Settings section, and click Edit to modify the cross-region backup settings.
Click OK.
Disable cross-region backup
You can disable cross-region backup if you no longer need it.
Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region in which your RDS instance resides.
Go to the target instance. On the Backup and Restoration page, on the Backup Strategy tab, find the Cross-region Backup Settings section, and then click Edit.
Change the cross-region backup status to Close, and set the Cross-region Retention Period period to 7 days.
Note However, existing backups are not immediately deleted. They are retained according to the previously configured retention period and are deleted only when they expire.
Click OK.
Query cross-region backup sets
Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region in which your RDS instance resides.
Navigate to the target instance. On the Cross-region Backups tab of the Backup and Restoration page, select the Backup Set Region to view all cross-region backup information.
Premium local SSD instances
Prerequisites
The ApsaraDB RDS instance must meet the following requirements:
Major engine version: 8.0, 5.7, or 5.6
Edition: High-availability Edition, or Enterprise Edition with three nodes (MySQL 5.7)
Storage type: Premium Local SSDs
Note You can view this information on the Basic Information page of the instance.
If this is your first time using the RDS backup service, you must authorize the service-linked role for Data Disaster Recovery.
Billing
For an instance with Premium Local SSDs, cross-region backups created in the ApsaraDB RDS console incur the following fees:
Billable item | Unit price(USD/GB/hour) |
Geo-redundant storage fee | 0.0002 |
Network traffic fee | For region-specific pricing details, see Network fees. |
Note For large amounts of data, we recommend using a DBS network plan to offset network fees.
Considerations
When using the cross-region backup feature in the ApsaraDB RDS console, note the following:
You can restore data from a cross-region backup to the source region or the destination region. However, if the instance has transparent data encryption (TDE) enabled, you can restore the data only to the source region.
Cross-region backup does not affect the default backup feature. Both can be active simultaneously, as cross-region backup works by copying local backups to another region.
After a default backup completes, the system copies it to the destination region for cross-region backup.
When you enable cross-region backup, the system triggers a backup of the secondary instance if no valid backup set has been created in the last 24 hours.
When you enable cross-region log backup, the system checks for a valid backup set that was generated in the last 24 hours:
If consecutive logs exist after the valid backup set, these logs are copied.
If no consecutive logs exist after the valid backup set, a backup of the secondary instance is triggered.
Supported backup routes and regions
Due to network limitations, the cross-region backup feature is available only in specific regions.
Supported backup routes | Data backup is supported between regions in the Chinese mainland, China (Hong Kong), and other regions. The destination region must be different from the source region. |
Supported regions | Chinese mainland: China (Beijing), China (Shanghai), China (Hangzhou), China (Shenzhen), China (Qingdao), China (Guangzhou), China (Ulanqab), China (Heyuan), China (Chengdu), China (Hohhot), and China (Zhangjiakou) China (Hong Kong) Other regions: US (Silicon Valley), US (Virginia), Singapore, Japan (Tokyo), Germany (Frankfurt), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila), UK (London), South Korea (Seoul), and Thailand (Bangkok)
|
Procedure
Enable cross-region backup for a single instance
Log on to the RDS console, click Instances in the left navigation bar, and then select a region at the top of the page.
Find the target instance, and on the right, select .
Note You can also find the Cross-region Backup Settings option on the Backup Strategy tab of the instance's Backup and Restoration page, and then click Edit.
If you do not see the Cross-region Backup option, verify that the instance meets the prerequisites.
Configure the following parameters.
Parameter | Description |
Cross-region Backup | The primary switch for cross-region backup. Select Enable. |
Backup Region | The region where backups are stored. Local backup files are automatically replicated to this region. |
Cross-region Backup Retention Period | The retention period of cross-region backup files. Valid values: 7 to 1825 days. The maximum retention period is five years.
Note The retention period of cross-region backups is unaffected even if the ApsaraDB RDS instance expires or is released. You can view unexpired backups on the Cross-region Backup page. |
Cross-region Log Backup | The switch for cross-region log backup. When enabled, local log backup files are automatically replicated to an OSS bucket in the destination region. |
Cross-border compliance agreement | Read and select the related agreement. |
Click OK.
Enable cross-region backup for multiple instances (batch)
Log on to the ApsaraDB RDS console. In the navigation pane on the left, click Backups. In the top navigation bar, select a region.
Click the tab.
Select the instances for which you want to enable cross-region backup, and click Backup Settings.
Note You can also click Settings in the Actions column to enable cross-region backup for a single instance.
Configure the following parameters.
Parameter | Description |
Cross-region Backup Status | The primary switch for cross-region backup. Select Enable. |
Backup Region | The region where backups are stored. Local backup files are automatically replicated to this region. |
Cross-region Retention Period | The retention period of cross-region backup files. Valid values: 7 to 1825 days. The maximum retention period is five years.
Note Even if the ApsaraDB RDS instance expires or is released, the retention period of the cross-region backup files is not affected. You can view unexpired backup files on the Cross-region Backup page of the console. |
Cross-region Log Backup Status | The switch for cross-region log backup. When enabled, local log backup files are automatically replicated to an OSS bucket in the destination region. |
Cross-border compliance agreement | Read and select the related agreement. |
Click OK.
Modify cross-region backup settings
Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region in which your RDS instance resides.
Go to the target instance, and on the Backup and Restoration page > Backup Strategy tab, find the Cross-region Backup Settings section, and click Edit to modify the cross-region backup settings.
Click OK.
Disable cross-region backup
You can disable cross-region backup if you no longer need it.
Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region in which your RDS instance resides.
Go to the target instance. On the Backup and Restoration page, on the Backup Strategy tab, find the Cross-region Backup Settings section, and then click Edit.
Change the cross-region backup status to Close, and set the Cross-region Retention Period period to 7 days.
Note However, existing backups are not immediately deleted. They are retained according to the previously configured retention period and are deleted only when they expire.
Click OK.
Download cross-region backup sets (data and log backups)
After a cross-region backup is created in the ApsaraDB RDS console, you can download the backup data that is stored in the destination region.
Log on to the RDS console, click Backups in the left-side navigation pane, and then select a region at the top of the page.
On the tab, find the target instance and click the instance ID.
On the Data Backup or Log backup tab, click Download in the row of the target backup set to download a full or an incremental backup set.
Click Download.
Important When you download backup files, intranet traffic is free of charge and internet traffic is charged. For more information, see Network Fees.
Query cross-region backup sets
Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region in which your RDS instance resides.
Navigate to the target instance. On the Backup and Restoration page, click the Cross-region Backups tab to view all cross-region backups.
This tab contains the Data Backup and Log Backup subtabs. The backup list displays information such as the start and end time, backup policy, backup size, point in time for restoration, backup method, backup type, backup region, and ID of the instance to which the backup belongs. In the Actions column, you can Download or Restore a backup.
Related operations
After a cross-region backup is created, you can restore data across regions to a new or existing instance in the destination region.
To modify a cross-region backup policy, such as the destination region or the retention period, or to disable the feature, see the Procedure section of this topic.
You can also call the following API operations to manage cross-region backups:
FAQ
How do I configure a separate backup frequency for cross-region backup?
You cannot configure a separate backup frequency for cross-region backup. This feature copies backup files generated in the source region, so the replication frequency depends on the backup policy of the source instance. The following rules apply:
If the source instance is configured for automatic daily backups, the system automatically copies each successful backup to the destination region.
After you enable cross-region backup, any manual backups you create are also automatically copied to the destination region upon successful creation.
Multiple backups generated on the same day, including automatic and manual backups, are individually copied to the destination region and retained in the cross-region backup list.
Are historical backups that were created before I enabled cross-region backup automatically synchronized to the destination region?
No. The cross-region backup feature replicates only backups created after you enable it. It does not copy backups that existed before enablement.
Why am I still being charged after I disable cross-region backup? How do I stop the billing?
After you disable cross-region backup, what happens to existing backups varies by instance type:
Cloud disk instances
If the instance is not released, the backup data that is replicated to the destination region is retained based on the original retention policy. Cross-region storage fees continue to be generated until the backups expire and are automatically cleared.
To delete existing cross-region backups and stop billing, change the retention period to its minimum value (for example, 7 days). The system will automatically delete the backups after this period, and you will no longer be charged for storage.
After the instance is released, the cross-region backups are not retained, and billing stops immediately.
Instances with Premium Local SSDs
Regardless of whether the instance is released, the backup data that has been replicated to the destination region is retained based on the original retention policy. Cross-region storage fees continue to be generated until the backups expire and are automatically cleared.
To delete existing cross-region backups and stop billing, change the retention period to its minimum value (for example, 7 days). The system will automatically delete the backups after this period, and you will no longer be charged for storage.
Can I manually delete previous cross-region backup files after I disable cross-region backup?
No. You cannot delete existing cross-region backups directly. To have them deleted, you must set a shorter retention period.
Does enabling cross-region backup affect instance performance?
Enabling cross-region backup has no impact on the performance of the source instance.
After I disable level-2 backup, how do existing backup sets expire?
Cross-region level-2 backup
Backup sets are retained based on the current cross-region backup retention period until all backup sets expire.
Same-region level-2 backup
Backup sets are not purged, but they are not visible and do not incur fees. You can view them again after you re-enable level-2 backup.
Can I use a resource plan to offset the geo-redundant storage fees from cross-region backups?
No resource plans are available to offset geo-redundant storage fees.
Does cross-region backup cause unstable connections?