ApsaraDB RDS for MySQL retains automatic backups for 7 days by default. This page describes three ways to keep backups longer—so you can recover data after accidental deletion, instance release, or account expiry.
Choose a method
Method | Best for | Works after instance release? |
Recovering data deleted weeks or months ago | No — backups are tied to the instance | |
Keeping backups after the instance is released or expires | Yes | |
Archiving backups locally or on ECS for long-term storage | Yes |
Method 1: Increase the backup retention period
Extend the number of days RDS retains backup files. This lets you restore data from further back in time while the instance is running.
Increasing the retention period adds to your backup size and may increase your backup storage costs.
Log on to the ApsaraDB RDS console and go to the Instances page. In the top navigation bar, select the region where the instance resides. Find the instance and click its ID.
In the left 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, increase the data backup or log backup retention period. For example, change the default value from 7 days to 30 days.
- The log backup retention period cannot exceed the data backup retention period. - For instances using Premium Local SSDs, select Permanently retained before instance release. All data backups are then retained until the instance is released, with no retention period to configure. For details, see Automatic backup.
Click OK.
Method 2: Configure a retention policy for released instances
By default, backups are deleted when an instance is released or expires. Configuring a retention policy keeps those backups available even after the instance is gone—so you can download them or restore to a new instance.
Limitations
This feature is not supported for RDS for MySQL instances that use Premium Local SSDs and run on RDS Enterprise Edition.
Default policies
Cloud disk instances purchased on or after February 1, 2024: The default retention policy is Lastest (the last backup is retained automatically). Storage is free for 7 days after release; charges apply after that. To avoid unexpected costs, set the policy to Do Not Retain if you don't need post-release backups.
New instances with Premium Local SSDs: The default retention policy is Do Not Retain.
Billing
Storage is free for 7 days after the instance is released. After that, pay-as-you-go charges apply based on the storage region and disk type.
Storage plans cannot offset backup storage fees for released instances.
You cannot purchase storage plans to offset backup storage fees for deleted RDS for MySQL instances.
Pricing for instances with high-performance local disks
Billing Site | Storage Region | Unit Price (USD/GB/Day) |
Public Cloud | China (Hangzhou), China (Beijing), China (Shanghai), China (Shenzhen), China (Qingdao), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Heyuan), China (Ulanqab), China (Guangzhou) | 0.00058 |
China (Hong Kong), Singapore, US (Silicon Valley), Germany (Frankfurt), Indonesia (Jakarta), Philippines (Manila), Thailand (Bangkok) | 0.00067 | |
Japan (Tokyo), South Korea (Seoul) | 0.0007 | |
US (Virginia) | 0.00062 | |
Malaysia (Kuala Lumpur) | 0.00064 | |
UK (London) | 0.00065 | |
UAE (Dubai) | 0.00072 |
Pricing for instances with cloud disks
Storage Region | Unit Price (USD/GB/Day) |
China (Beijing), China (Hohhot), China (Ulanqab), China (Hangzhou), China (Shanghai), China (Shenzhen), China (Heyuan), China (Chengdu), China (Qingdao), China (Guangzhou), China (Zhangjiakou) | 0.0009375 |
China (Hong Kong), US (Silicon Valley), US (Virginia), Singapore, Japan (Tokyo), Germany (Frankfurt), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila), UK (London), South Korea (Seoul), Thailand (Bangkok) | 0.001125 |
Usage notes
Backup files appear on the Backups > Backup for Deleted Instances page typically within 30 minutes after the instance release task completes.
If your account remains overdue for more than 30 days, Alibaba Cloud stops the backup retention service for released instances and permanently deletes all retained backups.
Configure the retention policy
Select the option that matches your situation.
Option 1: At purchase (subscription instances with Premium Local SSDs only)
On the purchase page, set the Backup Retention After Release parameter.
Option 2: Before release — on the instance details page
Log on to the ApsaraDB RDS console and go to the Instances page. Select the region where the instance resides. Find the instance and click its ID.
In the left 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, set the Retain Backup Files After Instance Release parameter and click OK.
Lastest or All: Completed backups are retained after the instance is released, based on your selection.
Do Not Retain: No backups are retained after release. Data cannot be recovered. Use this option with caution.
Important- After release, the system retains backup files for the long term based on the configured policy. You cannot specify a retention period. - Storage is free for 7 days. Charges apply after that. For pricing details, see Billing. - To use retained backup files after the instance is released, see Use backup files from a released instance.
Option 3: After release — on the Backup Management page
Log on to the ApsaraDB RDS console. In the left navigation pane, click Backups. In the top navigation bar, select the region where the instance resided.
On the Backups for Deleted Instances tab, find the instance and click Settings in the Retention Policy column.
In the dialog box, set the Data Backup Retention Policy and click OK.
Lastest or All: Completed backups are retained after the instance is released, based on your selection.
Do Not Retain: No backups are retained after release. Data cannot be recovered. Use this option with caution.
Important- After release, the system retains backup files for the long term based on the configured policy. You cannot specify a retention period. - Storage is free for 7 days. Charges apply after that. For pricing details, see Billing. - To use retained backup files after the instance is released, see Use backup files from a released instance.
For a full reference, see Configure the backup retention policy after instance release.
Method 3: Download backups
Download backup files to a local machine or an Elastic Compute Service (ECS) instance for long-term storage. For instructions, see Download backups.