Use the backup for deleted instances feature for an ApsaraDB RDS for MySQL instance - ApsaraDB RDS

ApsaraDB RDS for MySQL provides the backup for deleted instances feature. You can use the feature to configure a backup retention policy for your RDS instance before and after you delete or release the RDS instance. In this topic, the backup retention policy that you configure takes affect only after the RDS instance is deleted or released. This way, the backup files of the RDS instance are retained for a long period of time even if the RDS instance is unexpectedly released. You can download the backup files from the ApsaraDB RDS console to your on-premises computer or restore the backup files to a new RDS instance. This prevents data loss and ensures data security in a comprehensive manner.

Scenarios

Data restoration: If you delete an RDS instance, you can configure a backup retention policy for the RDS instance to Latest or All. This way, you can use the retained backup files to restore the data of the RDS instance to prevent data loss.
Data security: To ensure data security, you can configure a backup retention policy for an RDS instance before the RDS instance is deleted. This way, you can restore the data of the RDS instance from backup files when the RDS instance is deleted due to malicious attacks or other unknown reasons.
Data migration: You want to migrate the data of your RDS instance to another instance, but do not want to immediately delete the original RDS instance. In this case, you can retain the backup files of the original RDS instance before the RDS instance is deleted. If an error occurs during data migration, the migration can be rolled back at any time.

Limits

The 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 of the RDS instance are displayed with specific latencies. In most cases, the retained backup files are displayed within 30 minutes after the background task is completed.

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.

Unit price of the storage for the retention of backup sets for a deleted RDS instance that uses local disks

Type	Region	Unit price (USD per GB-day)
Public cloud	China (Hangzhou), China (Beijing), China (Shanghai), China (Shenzhen), China (Qingdao), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Heyuan), China (Ulanqab), and China (Guangzhou)	0.00058
	China (Hong Kong), Singapore, US (Silicon Valley), Germany (Frankfurt), Indonesia (Jakarta), Philippines (Manila), and Thailand (Bangkok)	0.00067
	Japan (Tokyo), South Korea (Seoul), and Australia (Sydney)	0.0007
	US (Virginia)	0.00062
	India (Mumbai) Closing Down	0.00063
	Malaysia (Kuala Lumpur)	0.00064
	UK (London)	0.00065
	UAE (Dubai)	0.00072

Unit price of the storage for the retention of backup sets for a deleted RDS instance that uses cloud disks

Region

Unit price (USD per GB-day)

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), Australia (Sydney), Malaysia (Kuala Lumpur), Indonesia (Jakarta), India (Mumbai) Closing Down, Philippines (Manila), UK (London), South Korea (Seoul), and Thailand (Bangkok)

0.001125

Note

You cannot purchase storage plans to offset the backup storage fees of deleted RDS instances.

Configure a backup retention policy after instance release

Important

If your RDS instance uses cloud disks and is created on or after February 1, 2024, the Backup Retention After Release parameter of the RDS instance is automatically set to Latest.
If the RDS instance is deleted, the backup files of the RDS instance are retained free of charge for seven days. After the seven-day retention period elapses, you are charged for the storage of the backup files. If you want to prevent the storage cost, 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 of the RDS instance 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 you create 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 Data Backup Retention Policy parameter and click OK. Valid values of the Data Backup Retention Policy parameter:
- Latest: After the RDS instance is released, the most recent backup file of the RDS instance is stored in the ApsaraDB RDS console. We recommend that you set the parameter to this value.
- All: After the RDS instance is released, all backup files of the RDS instance are stored in the ApsaraDB RDS console. We recommend that you set the parameter to this value.
- None: After the RDS instance is released, no backup files of the RDS instance are retained and the data of the RDS instance cannot be restored. Proceed with caution.
Important
- After the configuration is complete and your RDS instance is released, the backup files of the RDS instance are retained for a long period of time. You cannot specify the retention period.
- The backup files of the RDS instance are retained free of charge for seven days. After the seven-day retention period elapses, you are charged for the storage of the backup files. 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 retained 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. Valid values of the Data Backup Retention Policy parameter:
- Latest: After the RDS instance is released, the most recent backup file of the RDS instance is stored in the ApsaraDB RDS console. We recommend that you set the parameter to this value.
- All: After the RDS instance is released, all backup files of the RDS instance are stored in the ApsaraDB RDS console. We recommend that you set the parameter to this value.
- None: After the RDS instance is released, no backup files of the RDS instance are retained and the data of the RDS instance cannot be restored. Proceed with caution.
Important
- After the configuration is complete and your RDS instance is released, the backup files of the RDS instance are retained for a long period of time. You cannot specify the retention period.
- The backup files of the RDS instance are retained free of charge for seven days. After the seven-day retention period elapses, you are charged for the storage of the backup files. 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 retained backup files of an RDS instance after the RDS instance is deleted.

Use the retained backup files of an RDS instance after the RDS instance is deleted

After an RDS instance is released, you can click the Backup for Deleted Instances tab on the Backups page in the ApsaraDB RDS console to view the retained backup files. You can also manage the retained backup files on the tab.

Method 1: Download and archive the retained backup files

Note

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. You can use Method 2 to restore data to a new RDS instance.
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 tab, 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.

Method 2: Restore data from retained backup files to a new RDS instance

On the Backup for Deleted Instances tab, find the required RDS instance and click Restore in the Actions column to restore data from backup files to a new RDS instance.

Note

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 the RDS instance to view the restored data. For more information, see Connect to an ApsaraDB RDS for MySQL instance.

What to do next

View the backup retention policy of a deleted RDS instance

Method 1: View the backup retention policy on the instance details page before the RDS instance is released

Note

You can use this method only before RDS instances are deleted or released. If your RDS instance is deleted, you can use Method 2 to view the backup retention policy of the RDS instance 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 stored in the ApsaraDB RDS console.
- All: After the RDS instance is released, all backup files of the RDS instance are stored in the ApsaraDB RDS console.
- None: After the RDS instance is released, no backup files of the RDS instance are retained and the data of the RDS instance cannot be restored. Proceed with caution.

Method 2: View the backup retention policy on the Backups page after RDS the 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 stored in the ApsaraDB RDS console.
- All: After the RDS instance is released, all backup files of the RDS instance are stored in the ApsaraDB RDS console.
- None: After the RDS instance is released, no backup files of the RDS instance are retained and the data of the RDS instance cannot be restored. Proceed with caution.

Delete the backup files of a released RDS instance

If you do not want to retain the backup files of an RDS instance after the RDS instance 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.
Important
After 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.

FAQ

What is the backup for deleted instances feature and how do I use the feature?

The backup feature for deleted RDS instances is used to protect and restore data. After you enable this feature, you can retrieve data on the Backups page in the ApsaraDB RDS console even if your RDS instance is deleted or manually released. Then, you can download the backup files that are stored in the ApsaraDB RDS console to your on-premises computer or restore the backup files to a new RDS instance. For more information, see Configure a backup retention policy for an RDS instance and Use the retained backup files of an RDS instance after the RDS instance is deleted.

Why am I still charged for backup storage after I release my RDS instance?

If you configure a backup retention policy for your RDS instance before the RDS instance is released, the backup files of the RDS instance are stored on the Backups page in the ApsaraDB RDS console after the RDS instance is released. For more information, see Configure a backup retention policy after an RDS instance is deleted. After the RDS instance is deleted, the backup files of the RDS instance are retained free of charge for seven days. After the seven-day retention period elapses, you are charged for the storage of the backup files.

If you are still charged for backup storage after your RDS instance is released, the backup files of the RDS instance may be retained for more than seven days. In this case, fees are generated based on the storage usage and region. For more information, see Billing rules.

Why am I still charged for backup storage after I release my RDS instance even if I did not configure a backup retention policy before the RDS instance is released?

If your RDS instance uses cloud disks and is created on or after February 1, 2024, the backup retention policy of the RDS instance is automatically set to Latest when you create the RDS instance. In this case, the system retains the most recent backup file of your RDS instance after the RDS instance is released. The backup file of the RDS instance is retained free of charge for seven days. After the seven-day retention period elapses, you are charged for the storage of the backup files.

Note

To prevent unnecessary costs, we recommend that you check the backup retention policy of your RDS instance at regular intervals and modify the policy setting based on your business requirements. If you no longer require the backup files, you can manually delete the backup files of the deleted RDS instance to reduce storage costs. For more information, see Delete the backup files of an RDS instance after the RDS instance is released.

How do I delete retained backup files that are no longer required on the Backup for Deleted Instances tab?

If you no longer require the retained backup files of the deleted RDS instance and want to prevent backup storage fees, you can delete the retained backup files of a released RDS instance. For more information, see Delete the backup files of an RDS instance after the RDS instance is released.

Why is the retained backup set not displayed on the Backup for Deleted Instances tab after I release my RDS instance?