Cross-region backup automatically copies your ApsaraDB for MongoDB backups to a different region. If a regional outage makes your source region unavailable, you can restore data from the destination region without depending on the source. Use this feature to meet data compliance requirements or to implement cross-region disaster recovery.
Cross-region backup vs. standard backup
| Item | Cross-region backup | Standard backup |
|---|---|---|
| Default status | Disabled. Must be enabled manually. | Enabled by default. |
| Backup storage | Stored in a different region. | Stored in the same region as the instance. |
| Restore while instance is active | Restore to a new instance in the destination region. | Restore to a new instance in the current region. |
| Restore after instance is released | Not applicable. | Use a valid backup set from the recycle bin to create a new instance in the current region. |
| Retention after instance is released | Retained for the specified period, even after the instance is released. If you do not want to retain these backups after releasing the instance, change the retention period before you release the instance. | Retained based on the policy in effect at the time of release. |
Prerequisites
Before you begin, make sure that:
The instance is a replica set or sharded cluster instance.
The instance uses Enterprise SSD (ESSD) storage.
Billing
Cross-region backup incurs two types of fees: storage fees and network traffic fees.
| Billable item | Destination region | Unit price (USD/GB/day) |
|---|---|---|
| Cross-region 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 | |
| SAU (Riyadh - Partner Region) | 0.00135 | |
| Network traffic fee | Varies by region | See Network feesNetwork fees |
Disabling cross-region backup stops new backups and eliminates network traffic fees, but existing backup files are not deleted immediately and continue to incur storage fees. To avoid ongoing storage charges, set Cross-region Backup Retention Period (Days) to 3 before disabling the feature. Existing backup files are automatically deleted after 3 days, after which no further storage fees apply.
Usage notes
Cross-region backup data can only be restored to the destination region where the backup sets are stored.
Cross-region backups and standard backups are independent. Both can coexist without affecting each other.
Cross-region backup copies all manual backups, the first standard backup of the day, and the first high-frequency backup of the day.
Downloading data backup sets or log backup sets from a cross-region backup is not supported.
Cross-region backup is only supported between specific source and destination region pairs. See the supported regions below.
Supported regions
| Area | Supported regions |
|---|---|
| China | China (Beijing), China (Hohhot), China (Ulanqab), China (Hangzhou), China (Shanghai), China (Shenzhen), China (Heyuan), China (Chengdu), China (Qingdao), China (Guangzhou), China (Zhangjiakou), and China (Hong Kong) |
| Other countries and regions | US (Silicon Valley), US (Virginia), Singapore, Japan (Tokyo), Germany (Frankfurt), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila), UK (London), South Korea (Seoul), Thailand (Bangkok), and SAU (Riyadh - Partner Region) |
The region list above is for reference only. For actual supported regions, check the console.
Enable cross-region backup
Go to the ApsaraDB for MongoDB Replica Set Instances page or the ApsaraDB for MongoDB Sharded Cluster Instances page. Select a resource group and a region, then click the ID of the target instance.
In the left navigation pane, click Backup and Restoration.
Click Backup Settings.
Click Edit. In the Backup Settings panel, under Advanced Features, select Cross-region Backup and configure the following parameters. Example configuration The following example shows a typical cross-region backup setup for a sharded cluster instance that needs daily backups replicated to a secondary region for disaster recovery.
For standard backup parameters such as backup window and frequency, see Automatically back up ApsaraDB for MongoDB data.
Parameter Description Source Region The region where the instance resides. Read-only. Backup Region The region to copy backups to. Must differ from the source region. Retention Type Retain for a specified period or Permanent. Cross-region Backup Retention Period (Days) The number of days to retain cross-region backups. Valid values: 3 to 1825. Required only when Retention Type is set to Retain for a specified period. Day of Week The days on which backups are copied to the destination region. For example, selecting Monday and Wednesday copies all manual backups, the first standard backup, and the first high-frequency backup from those days. Cross-region Log Backup Status Whether to enable log backup for cross-region backup. Log backup is not supported for replica set instances. For sharded cluster instances, log backup is required for cross-region restore and cannot be disabled. Compliance Statement Read and select I have read and agreed to the compliance statement. Parameter Example value Source Region China (Hangzhou) Backup Region China (Beijing) Retention Type Retain for a specified period Cross-region Backup Retention Period (Days) 30 Day of Week Monday, Wednesday, Friday Cross-region Log Backup Status Enabled Click OK.
Modify cross-region backup settings
Go to the ApsaraDB for MongoDB Replica Set Instances page or the ApsaraDB for MongoDB Sharded Cluster Instances page. Select a resource group and a region, then click the ID of the target instance.
In the left navigation pane, click Backup and Restoration.
Click Backup Settings.
Click Edit. In the Backup Settings panel, under Advanced Features, modify the parameters under Cross-region Backup. The configurable parameters are the same as those described in Enable cross-region backup.
Click OK.
View cross-region backup files
Go to the ApsaraDB for MongoDB Replica Set Instances page or the ApsaraDB for MongoDB Sharded Cluster Instances page. Select a resource group and a region, then click the ID of the target instance.
In the left navigation pane, click Backup and Restoration.
Click the Cross-region Backup tab to view backup files for the current instance.
Disable cross-region backup
Disabling cross-region backup stops new backups and eliminates network traffic fees, but existing backup files are not deleted immediately and continue to incur storage fees. To stop storage charges, set Cross-region Backup Retention Period (Days) to 3 before disabling. Backup files are automatically deleted after 3 days.
Go to the ApsaraDB for MongoDB Replica Set Instances page or the ApsaraDB for MongoDB Sharded Cluster Instances page. Select a resource group and a region, then click the ID of the target instance.
In the left navigation pane, click Backup and Restoration.
Click Backup Settings.
Clear the Cross-region Backup checkbox.
Click OK.
Restore from a cross-region backup
To restore data to a new or existing instance in the destination region, see Restore data across regions.
API reference
| API | Description |
|---|---|
| DescribeBackups | Queries the backup list of a replica set instance. |
| DescribeClusterBackups | Queries the backup list of a sharded cluster instance. |
| ModifyBackupPolicy | Modifies the backup policy of an instance. |
| DescribeBackupPolicy | Queries the backup policy of an instance. |
| CheckRecoveryCondition | Checks whether a cloud disk instance meets data restoration conditions. |