ApsaraDB RDS:Retain the backup files of an ApsaraDB RDS for MySQL instance for a long period of time

Background information

When you use ApsaraDB RDS, you may encounter the following issues:

• Your data is unexpectedly deleted. However, only the backup files that are generated over the most recent seven days are retained. As a result, you cannot restore the data that was generated seven days ago.

• Your RDS instance has been released due to unintended operations or overdue payments for a long period of time. As a result, you cannot recover your data or backup files.

• You want to release your RDS instance but retain its backup files for future use.

Method 1: Increase the backup retention period

You can increase the backup retention period to restore earlier data.

1. 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 ID of the instance.

2. In the left-side navigation pane of the page that appears, click Backup and Restoration.

3. On the Backup and Restoration page, click the Backup Strategy tab. In the Basic Backup section of the tab that appears, click Edit.

4. In the dialog box that appears, manually increase the data backup retention period or the log backup retention period. For example, you can increase the value from the default value 7 to 30.

   Note

   • The log backup retention period cannot be longer than the data backup retention period.

   • If your RDS instance uses local disks, you can select Permanently Retained before Instance Release. After you select Permanently Retained before Instance Release, you do not need to specify the data backup retention period. All data backup files are retained. For more information, see Use the automatic backup feature.

5. Click OK.

Method 2: Configure the backup retention policy after the instance is released

In most cases, after your RDS instance expires or becomes overdue, the system retains your RDS instance and its backup files based on the retention period that you specify. After the retention period elapses, the system releases your RDS instance and deletes its backup files. For more information, see Overdue payments. To resolve this issue, you can configure a backup retention policy for your RDS instance seven days after the RDS instance is created. After the configuration, the backup files of the RDS instance are retained for a long period of time even if the RDS instance is released.

Method 3: Download a backup file

You can download a backup file of your RDS instance to your computer or to your Elastic Compute Service (ECS) instance. The backup file can be stored on your computer or ECS instance for a long period of time. For more information, see What is ECS? and Download the backup files of an ApsaraDB RDS for MySQL instance.

FAQ

• The Retain Backup Files after Instance Release parameter is set to Latest for my RDS instance before the RDS instance is released. Where is the retained backup file stored?

  After your RDS instance is released, you can go to the Backup for Deleted Instances tab to download the backup file of your RDS instance. Then, you can use the backup file for restoration.

• My RDS instance is released but storage fees are still generated. Why?

  A backup retention policy may be configured for your released RDS instance. The backup files of the RDS instance are retained after the RDS instance is released, and fees are generated for the retention of the generated backup files. Therefore, even if your RDS instance is released, the storage fee will appear on the subsequent bills. For more information, see Retain the backup files of an ApsaraDB RDS for MySQL instance for a long period of time.

  Note

  If you do not want to retain the backup files after your RDS instance is released, you can go to the Backup for Deleted Instances tab to modify the backup retention policy of the RDS instance to Delete All Backups (Cannot be Restored) based on your business requirements.