ApsaraDB RDS for MySQL allows you to retain instance backups after an instance is released. Before releasing your RDS instance, you can configure the backup retention policy. After release, backup files can be retained for a long period, preventing data loss from unexpected operations. You can download these backup files from the ApsaraDB RDS console or restore them to a new instance.
Scenarios
Data restoration: If you accidentally release an RDS instance, you can use the retained backup files to restore data and prevent data loss.
NoteIf your RDS instance uses cloud disks and was created on or after February 1, 2024, the Backup Retention After Release parameter is automatically set to Latest. If your RDS instance uses local disks, this parameter is automatically set to None. You must manually configure the backup retention policy.
Data security: To enhance data security, configure a backup retention policy before deleting your RDS instance. This allows you to restore data from backup files if the instance is deleted due to attacks or other unknown reasons.
Data migration: When migrating data to another RDS instance but not wanting to immediately delete the original instance, you can retain backup files before deletion. This provides a rollback option if errors occur during migration.
Limits
This feature is not supported for RDS instances that run RDS Enterprise Edition and use local disks.
Usage notes
When you delete or release an RDS instance, the retained backup files are displayed on the Backups > Backup For Deleted Instances page with specific latencies. Typically, after the release task completes in the background, the retained backup files appear within 30 minutes.
Billing rules
If your RDS instance is deleted, the backup files of the RDS instance are retained free of charge within seven days. After the 7-day retention period elapses, you are charged for the storage of the backup files based on the pay-as-you-go billing method. The following tables describe the unit prices. The following tables describe the unit prices.
You cannot purchase storage plans to offset the backup storage fees of deleted RDS instances.
Configure a backup retention policy after instance release
If your RDS instance uses cloud disks and was created on or after February 1, 2024, the Backup Retention After Release parameter is automatically set to Latest.
If the RDS instance is deleted, the backup files are retained free of charge for seven days. After this period, you are charged for storage. To prevent storage costs, you can configure the backup retention policy to None.
When you create an RDS instance that uses local disks, the Backup Retention After Release parameter is automatically set to None.
You can configure a backup retention policy based on the status of an RDS instance.
Method 1: Configure a backup retention policy when you create the RDS instance
You can use this method only when creating a subscription RDS instance that uses local disks. On the ApsaraDB RDS buy page, you can configure the Backup Retention After Release parameter.
Method 2: Configure a backup retention policy on the instance details page before the RDS instance is released
Log on to the ApsaraDB RDS console and go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the instance ID.
In the left-side navigation pane, click Backup and Restoration.
On the Backup and Restoration page, click the Backup Strategy tab. In the Basic Backup section, click Edit.
In the dialog box that appears, configure the Retain Backup Files After Instance Release parameter and click OK.
Latest or All (Recommended): After the RDS instance is released, the backup files are retained based on your settings.
None: After the RDS instance is released, no backup files are retained and the data cannot be restored. Proceed with caution.
ImportantAfter the RDS instance is released, the backup files are retained for a long period of time based on your retention policy settings. You cannot specify the retention period.
The backup files are retained free of charge for seven days. After the seven-day retention period elapses, you are charged for the storage. For more information, see Billing rules.
For more information about how to use the retained backup files after an RDS instance is released, see Use the backup files of an RDS instance after the RDS instance is deleted.
Method 3: Configure a backup retention policy on the Backups page after the RDS instance is released
Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Backups. In the top navigation bar, select the region in which the RDS instance resides.
On the Backup For Deleted Instances tab, find the required RDS instance and click Settings in the Retention Policy column.
In the dialog box that appears, configure the Data Backup Retention Policy parameter and click OK.
Latest or All (Recommended): After the RDS instance is released, the backup files are retained based on your settings.
None: After the RDS instance is released, no backup files are retained and the data cannot be restored. Proceed with caution.
ImportantAfter the RDS instance is released, the backup files are retained for a long period of time based on your retention policy settings. You cannot specify the retention period.
The backup files are retained free of charge for seven days. After the seven-day retention period elapses, you are charged for the storage. For more information, see Billing rules.
For more information about how to use the retained backup files after an RDS instance is released, see Use the backup files of an RDS instance after the RDS instance is deleted.
Use the backup files of an RDS instance after the RDS instance is deleted
After an RDS instance is released, you can visit the Backups > Backup For Deleted Instances page in the ApsaraDB RDS console to view and manage the retained backup files.
Method 1: Restore data from the retained backup files to a new RDS instance
Go to the Backup for Deleted Instances page, find the required RDS instance and click Restore in the Actions column to restore data from backup files to a new RDS instance.
You can go to the Tasks page to view the creation progress of the RDS instance. For more information about how to configure the parameters to create an RDS instance, see Create an ApsaraDB RDS for MySQL instance.
After you create an RDS instance, you can connect to it to view the restored data. For more information, see Connect to an ApsaraDB RDS for MySQL instance.
Method 2: Download and archive the retained backup files
You can download only the physical backup files of RDS instances that use local disks. You cannot download the snapshot backup files of RDS instances that use cloud disks.
If you download backup files over an internal network, no fees are generated. If you download backup files over the Internet, you are charged for the Internet traffic that you use. For more information about the download methods and the fees for the Internet traffic, see Download backup files.
Go to the Backup for Deleted Instances page, find the required RDS instance, click Download in the Actions column, and then copy the internal URL or external URL to download the backup files.
Related operations
View the backup retention policy after instance release
Method 1: View the backup retention policy on the instance details page before the RDS instance is released
You can use this method only before RDS instances are deleted or released. If your RDS instance is deleted or released, you can use Method 2 to view the backup retention policy on the Backups page.
Log on to the ApsaraDB RDS console and go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the instance ID.
In the left-side navigation pane, click Backup and Restoration.
On the Backup and Restoration page, click the Backup Strategy tab. In the Basic Backup section, view the backup retention policy of the RDS instance.
Latest: After the RDS instance is released, the most recent backup file of the RDS instance is retained.
All: After the RDS instance is released, all backup files of the RDS instance are retained.
None: After the RDS instance is released, no backup files are retained and the data cannot be restored. Proceed with caution.
Method 2: View the backup retention policy on the Backups page after the RDS instance is released
Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Backups. In the top navigation bar, select the region in which the RDS instance resides.
On the Backup For Deleted Instances tab, find the required RDS instance and click Settings in the Retention Policy column.
In the dialog box that appears, view the backup retention policy of the RDS instance.
Latest: After the RDS instance is released, the most recent backup file of the RDS instance is retained.
All: After the RDS instance is released, all backup files of the RDS instance are retained.
None: After the RDS instance is released, no backup files are retained and the data cannot be restored. Proceed with caution.
Reduce or delete the backup files of a released RDS instance
If you do not want to retain the backup files of an RDS instance after it is released, you can set the Data Backup Retention Policy parameter to Latest or None to prevent or reduce backup storage costs.
Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Backups. In the top navigation bar, select the region in which the RDS instance resides.
On the Backup For Deleted Instances tab, find the required RDS instance and click Settings in the Retention Policy column.
In the dialog box that appears, set the Data Backup Retention Policy parameter to one of the following values:
Latest: If you change the value from All to Latest, backup storage costs are reduced.
None: If you change the value from All or Latest to None, backup storage fees are no longer generated.
ImportantAfter the configuration is complete, the system automatically deletes the backup files that are stored in the ApsaraDB RDS console based on the retention policy. After the backup files are deleted, data can no longer be restored. Proceed with caution.
Click OK.