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
Recycle Bin: Log on to the ApsaraDB RDS console and go to the Recycle Bin page. In the top navigation bar, select the region in which the RDS instance resides. If you can find the RDS instance on the Locked Instances page, you can rebuild the RDS instance.
Backup for Deleted Instances: If you configure the Retain Backup Files after Instance Release parameter for an RDS instance that uses local disks and was created at least seven days ago, you can download the required backup files on the Backup for Deleted Instances tab to restore the data of the RDS instance. For more information about backup settings, see Enable the automatic backup feature.
Scenario 2: Restore data that is deleted or modified on an RDS instance
Solution | Supported instance | Restoration time | Restoration range | Restoration destination | Restore speed |
Local disk | Cloud disk | Any point in time | Point in time when the backup set is generated | All databases and tables | Individual databases and tables | To a new RDS instance | To the original RDS instance | To an existing RDS instance |
Solution | Supported instance | Restoration time | Restoration range | Restoration destination | Restore speed |
Local disk | Cloud disk | Any point in time | Point in time when the backup set is generated | All databases and tables | Individual databases and tables | To a new RDS instance | To the original RDS instance | To an existing RDS instance |
Instance restoration | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ❌ | ✔️ | ❌ | ❌ | Slow |
Emergency recovery | ✔️ | ❌ | ✔️ | ✔️ | ✔️ | ❌ | ❌ | ❌ | ❌ | Fast |
Restoration for individual databases and tables | Regular | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ❌ | Slow |
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 Data Management (DMS) to roll back data by executing SQL statements. For more information, see Use the data tracking feature of DMS to restore the data of an ApsaraDB RDS for MySQL instance.
Scenario 3: View data that exists at a specific point in time in an RDS instance
Scenario 4: Restore data from backup files to an on-premises database or the cloud
Migrate or restore data to the cloud
Migrate or restore data to an on-premises database
Migrate data of an RDS instance to a different RDS instance