All Products
Search

This Product

    ApsaraDB RDS:Cross-region backup

    Document Center

    ApsaraDB RDS:Cross-region backup

    Last Updated:Mar 28, 2026

    Cross-region backup (geo-redundancy) automatically replicates RDS MySQL backups to a different region to meet regulatory compliance requirements or build cross-region disaster recovery capacity. Each time a local backup completes, the backup file is copied to the destination region immediately. If you also enable cross-region log backup, log files generated after that point are replicated continuously.

    For cross-region backup on other engines, see Cross-region backup for PostgreSQL and SQL Server cross-region backup.

    How cross-region backup works

    Cross-region backup does not run on its own schedule. Each time a local backup completes successfully, the backup file is automatically copied to the destination region. If you enable cross-region log backup, only logs generated after you enable the feature are replicated.

    Cross-region backups and data restoration use a virtual private cloud (VPC) for non-cross-border transfers and the public internet for cross-border transfers.

    Cross-region backup vs. default backup

    ItemCross-region backupDefault backup
    Enabled by defaultNo — must be enabled manuallyYes
    Backup storageDestination region (different from source)Same region as the instance
    Restore target (cloud disk)New instance in the destination region onlySource instance or new instance in the current region
    Restore target (Premium Local SSDs)Source or destination region (TDE restriction applies — see Limitations)Source instance or new instance in the current region
    Retention after release (cloud disk)Not retained; no storage charge7 days
    Retention after release (Premium Local SSDs)Retained per the configured retention policy; storage fees apply7 days
    Download backup setsNot supported for cloud disk instancesSupported

    Storage class comparison

    Behavior differs based on your instance's storage class.

    DimensionCloud diskPremium Local SSDs
    Supported MySQL versions8.0, 5.78.0, 5.7, 5.6
    Supported editionsBasic Edition, High-availability Edition, Cluster EditionHigh-availability Edition, RDS Enterprise Edition (5.7)
    Serverless supportNot supported—
    Geo-redundant storage feeUSD 0.0009375/GB/day (Chinese mainland regions); USD 0.001125/GB/day (other regions)USD 0.0002/GB/hour
    Network traffic feeSee Network feesSee Network fees
    Backup triggered on enableNo — waits for the next scheduled local backupYes — if no valid backup exists in the last 24 hours, a secondary database backup is triggered immediately
    Log backup on enableOnly logs generated after enabling are replicatedSystem checks for a valid backup set in the last 24 hours; if continuous logs follow it, they are replicated; otherwise, a secondary database backup is triggered first
    Download backup setsNot supportedSupported
    Retention after instance releaseNot retained; no chargeRetained per configured retention policy; storage fees continue until backup sets expire
    For large data volumes, use a DBS network plan to offset network traffic fees.

    Limitations

    Review the following constraints before enabling cross-region backup:

    • The destination region must differ from the source region. Restoring to the source region is not supported.

    • Serverless instances do not support cross-region backup.

    • Cloud disk instances do not support downloading cross-region data or log backup sets.

    • For instances with transparent data encryption (TDE) enabled, data can only be restored to the source region, not the destination region.

    • Historical backups created before you enable cross-region backup are not replicated. Only backups created after enabling are copied.

    • Existing backup sets cannot be deleted manually. To stop retaining them, reduce the retention period to 7 days; they are purged automatically after expiration.

    • No resource plans are available to offset geo-redundant storage fees.

    Supported regions

    Cross-region backup is available between the following regions. The destination region must differ from the source region.

    AreaSupported regions
    Chinese mainlandChina (Beijing), China (Shanghai), China (Hangzhou), China (Shenzhen), China (Qingdao), China (Guangzhou), China (Ulanqab), China (Heyuan), China (Chengdu), China (Hohhot), China (Zhangjiakou)
    China (Hong Kong)China (Hong Kong)
    Regions outside ChinaUS (Silicon Valley), US (Virginia), Singapore, Japan (Tokyo), Germany (Frankfurt), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila), UK (London), South Korea (Seoul), Thailand (Bangkok)

    Data backup is supported between the Chinese mainland, China (Hong Kong), and regions outside China.

    Prerequisites

    Before enabling cross-region backup, make sure that:

    Check your instance's version, edition, and storage class on the Basic Information page.

    Enable cross-region backup

    Select the tab that matches your instance's storage class.

    Cloud disk instances

    1. Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where your instance resides.

    2. Find the instance. On the Backup and Restoration page, click the Backup Strategy tab. In the Cross-region Backup Settings section, click Edit.

      If the Cross-region Backup Settings section is not displayed, verify that your instance meets the prerequisites.

    3. Configure the following parameters.

      ParameterDescription
      Cross-region BackupSet to Enable.
      Backup RegionThe destination region where local backups are copied.
      Cross-region Backup Retention Period (Days)Cross-region Backup Retention Period (Days)How long cross-region backup files are retained. Valid values: 7–1825 days (up to 5 years). After an instance is released, existing backups are deleted immediately and are not charged.
      Cross-region Log BackupEnable to replicate local log backup files to an OSS bucket in the destination region. Only logs generated after enabling are replicated.

    4. Read and accept the billing description and data cross-border compliance commitment, then click OK.Cross-border Compliance AgreementCross-border Compliance Agreement

    Instances with Premium Local SSDs

    Enable for a single instance

    1. Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where your instance resides.

    2. Find the instance. In the Actions column, choose More > Cross-region Backup Settings.

      Alternatively, go to the Backup and Restoration page, click the Backup Strategy tab, and in the Cross-region Backup Settings section, click Edit.

    3. Configure the following parameters.

      ParameterDescription
      Cross-region BackupSet to Enable.
      Backup RegionThe destination region where local backups are copied.
      Cross-region Backup Retention Period (Days)How long cross-region backup files are retained. Valid values: 7–1825 days (up to 5 years). Retention is not affected when the instance expires or is released.
      Cross-region Log BackupEnable to replicate local log backup files to an OSS bucket in the destination region.
      Cross-border Compliance AgreementRead and accept the agreement.

    4. Click OK.

    Enable for multiple instances (batch)

    1. Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Backups. In the top navigation bar, select a region.

    2. Click Cross-region Backup > Pending Instances.

    3. Select the instances to configure and click Backup Settings.

      To configure a single instance from this page, click Settings in the Actions column.

      image.png

    4. Configure the following parameters.

      ParameterDescription
      Cross-region Backup StatusSet to Enable.
      Backup RegionThe destination region where local backups are copied.
      Cross-region Retention PeriodHow long cross-region backup files are retained. Valid values: 7–1825 days (up to 5 years). Retention is not affected when the instance expires or is released.
      Cross-region Log Backup StatusEnable to replicate local log backup files to an OSS bucket in the destination region.
      Cross-border Compliance AgreementRead and accept the agreement.

    5. Click OK.

    Modify cross-region backup settings

    1. Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where your instance resides.

    2. Find the instance. On the Backup and Restoration page, click the Backup Strategy tab. In the Cross-region Backup Settings section, click Edit.

    3. Update the settings and click OK.

    Disable cross-region backup

    1. Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where your instance resides.

    2. Find the instance. On the Backup and Restoration page, click the Backup Strategy tab. In the Cross-region Backup Settings section, click Edit.

    3. Set Cross-region Backup to Disabled and set Cross-region Backup Retention Period (Days) to 7 days.

      After you disable cross-region backup, no new network traffic fees or storage fees are incurred. Existing backup sets are not deleted immediately — they are retained until their configured retention period expires, then purged automatically.

    4. Click OK.

    View cross-region backup sets

    Query cross-region backup sets

    1. Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where your instance resides.

    2. Find the instance. On the Backup and Restoration page, click the Cross-region Backups tab. Select a Region of Backup Set to view available backups.

    Query cross-region backup sets

    1. Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where your instance resides.

    2. Find the instance. On the Backup and Restoration page, click the Cross-region Backups tab to view all cross-region backups.

    If the instance has been released, you can still access retained backup sets. In the left-side navigation pane, click Backup Management > Cross-region Backup, and then click the instance ID to view backup data. To change the retention period for retained backups, click Settings on the Backup Management > Cross-region Backup page. You cannot directly delete existing backup sets.

    Download cross-region backup sets

    This operation applies to instances with Premium Local SSDs only. Cloud disk instances do not support downloading cross-region backup sets.

    1. Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Backup Management. In the top navigation bar, select a region.

    2. On the Cross-region Backup > Backup Instances tab, find the instance and click the instance ID.

    3. On the Data Backup or Log Backup tab, find the backup set to download and click Download in the Actions column.

    4. Click Download.

      Important

      Downloading over an internal network incurs no traffic fees. Downloading over the internet incurs internet traffic fees. See Network fees for details.

    FAQ

    Can I set a separate backup frequency for cross-region backups?

    No. Cross-region backup does not have its own schedule — it piggybacks on local backups. Each time a local backup completes successfully, it is automatically copied to the destination region. The replication frequency therefore matches your local backup policy. If multiple backups (both automatic and manual) complete on the same day, each is copied and stored as an independent backup set in the destination region.

    Are backups created before I enabled cross-region backup replicated?

    No. Only backup files created after you enable the feature are copied. Existing backup sets remain in the source region only.

    Why am I still charged after disabling cross-region backup?

    Disabling stops new backups from being copied, but existing backup sets in the destination region are retained until their configured retention period expires. Storage fees continue until the sets are purged.

    • Cloud disk instances: To accelerate purging, reduce the retention period to 7 days. If the instance is released, existing cross-region backups are deleted immediately and storage fees stop.

    • Instances with Premium Local SSDs: To accelerate purging, reduce the retention period to 7 days. Backups are retained regardless of whether the instance is released.

    Can I manually delete cross-region backup sets?

    No. Backup sets cannot be deleted directly. To release storage sooner, reduce the retention period to 7 days — the system purges them automatically after expiration.

    Does enabling cross-region backup affect instance performance?

    No. Cross-region backup has no impact on source instance performance or connection stability.

    What happens to level-2 backups when they are disabled?

    • Cross-region level-2 backup: Existing backup sets are retained until the configured retention period expires.

    • Same-region level-2 backup: Backup sets are not purged, but they are no longer visible and do not incur fees. They reappear when you re-enable level-2 backup.

    Can I use a resource plan to offset geo-redundant storage fees?

    No. No resource plans are available to offset geo-redundant storage fees generated by cross-region backup.

    API reference

    Use the following API operations to manage cross-region backups programmatically.

    OperationDescription
    CheckCreateDdrDBInstancePrecheck whether an instance can be restored across regions
    CreateDdrInstanceRestore data from another region to a new instance
    RestoreDdrTableRestore data to an existing instance across regions
    ModifyInstanceCrossBackupPolicyModify cross-region backup settings
    DescribeInstanceCrossBackupPolicyQuery cross-region backup settings
    DescribeCrossBackupMetaListQuery database and table metadata of cross-region backups
    DescribeCrossRegionBackupsList cross-region data backup files for an instance
    DescribeCrossRegionLogBackupFilesList cross-region log backup files
    DescribeAvailableCrossRegionQuery available destination regions
    DescribeAvailableRecoveryTimeQuery the recoverable time range of a backup
    DescribeCrossRegionBackupDBInstanceList instances with cross-region backup enabled

    What's next

    References