All Products
Search
Document Center

ApsaraDB RDS:Overview of data restoration methods for ApsaraDB RDS for MySQL

Last Updated:May 20, 2025

This topic describes the methods that you can use to restore data of an ApsaraDB RDS for MySQL instance. You can select a method based on the scenarios in which you accidentally release an ApsaraDB RDS for MySQL instance, delete or modify the data of an RDS instance, or want to restore data of an RDS instance to an on-premises database or the cloud from backup files.

Scenario 1: Restore data of an RDS instance that is released

Select a restoration method based on when the instance was released (deleted):

  • Restore through the recycle bin:

    • For instances that are manually released (deleted), you can rebuild and restore them through the recycle bin within 9 days after they are released.

    • For subscription instances that have expired or pay-as-you-go instances with overdue payments, you can unlock or rebuild and restore them through the recycle bin within 16 days.

  • Restore through deleted instance backups:

    If you have configured a backup retention policy after instance release, you can download backups for restoration from the Deleted Instance Backups page.

    Note
    • Disk instances: For RDS MySQL disk instances purchased on or after February 1, 2024, the default backup retention policy after instance release is Retain The Last One.

    • High-performance local disks: For newly purchased RDS MySQL instances with high-performance local disks, the default backup retention policy after instance release is Do Not Retain. You need to manually configure a backup retention policy after instance release.

Scenario 2: Restore data that is deleted or modified on an RDS instance

Method

Supported instances

Restoration point in time

Restoration scope

Restoration destination

Restoration speed

High-performance local disk

Disk

Any point in time

Point in time of backup set

All databases and tables

Partial databases and tables

Restore to a new RDS instance

Restore to the original RDS instance

Restore to another existing RDS instance

Instance restoration

✔️

✔️

✔️

✔️

✔️

✔️

Slow

RDS MySQL emergency recovery

✔️

✔️

✔️

✔️

Fast

Database and table restoration

Standard

✔️

✔️

✔️

✔️

✔️

✔️

✔️

✔️

Slow

Ultra-fast

✔️

✔️

✔️

✔️

✔️

✔️

Fast

Note
  • Restore data to a new RDS instance: If you want to temporarily use the new RDS instance, you can create a pay-as-you-go RDS instance. Restore data to the pay-as-you-go RDS instance, migrate the data to the original RDS instance, and then release the pay-as-you-go RDS instance to reduce costs.

  • Restore data to the original RDS instance: Data restoration does not overwrite the data of the original RDS instance.

  • You can also use the data tracking feature of DMS to roll back data by executing rollback SQL statements.

Scenario 3: Query data at a specific point in time

Scenario 4: Restore from backup files to the cloud or on-premises

Migrate/restore to the cloud

Migrate/restore to on-premises

Migrate between RDS instances

Other scenarios

  • If you need to back up data to another region, or restore data across regions to a new instance or an existing instance in the destination region, see Cross-region backup and Cross-region data restoration.

  • You can also use the mysqldump command to export data from a specified database as an SQL file for backup, and use the mysql command to import data from the SQL file to the destination database for restoration. For more information, see Back up and restore a database by using mysqldump.