This topic describes how to manage the ApsaraDB RDS for MySQL instances that are moved to the recycle bin. You can unlock, rebuild, or destroy these instances in the recycle bin.

Functionality

All ApsaraDB RDS for MySQL instances that are manually released, automatically released due to expiration, or payment refunded are moved to the recycle bin. An RDS instance is not moved to the recycle bin in the following scenarios:
  • The RDS instance is payment refunded or manually released within seven days after the instance is created.
  • The RDS instance is a pay-as-you-go RDS instance and is automatically released due to overdue payments.
  • The RDS instance runs the RDS Cluster Edition or is a read-only RDS instance.

Unlock an RDS instance whose payment is overdue

If a pay-as-you-go RDS instance is locked due to overdue payments, log on to the Billing Management console. Then, verify that a valid payment method is specified for your Alibaba Cloud account.

Unlock an RDS instance that has expired

If a subscription RDS instance is locked due to expiration, you can renew the instance in the recycle bin within the next 15 days. If you do not renew the instance within 15 days, the instance is released.

  1. Log on to the RDS management console.
  2. In the left-side navigation pane, click Locked Instances. In the top navigation bar, select the region where the RDS instance resides.
  3. Find the RDS instance and click Unlock to renew the RDS instance.

After the RDS instance is renewed, it is immediately restored to normal.

Rebuild an RDS instance

After a subscription RDS instance is automatically released due to expiration or a pay-as-you-go RDS instance that is created seven days ago or earlier is manually released, the backup files of the instance are retained for eight days. During the eight-day retention period, you can restore the data of the backup files to a new RDS instance by using the rebuild feature. After the eight-day retention period elapses, only the backup files that meet specified conditions are retained and all the other backup files are deleted.
Note The backup files that can be retained after the eight-day retention period elapses must meet the following conditions:
  • The instance runs MySQL, PostgreSQL, or SQL Server, and the cross-region backup retention period that you specify has not elapsed. In this case, the cross-region backup files of the instance are retained within the specified cross-region backup retention period.
  • The instance runs MySQL, and you have specified to retain the backup files of the instance even after the instance is released. In this case, the backup files of the instance are retained. For more information, see Enable automatic backups for an ApsaraDB RDS for MySQL instance.
  1. Log on to the ApsaraDB RDS console.
  2. In the left-side navigation pane, click Locked Instances. In the top navigation bar, select the region where the RDS instance resides.
  3. Find the RDS instance and click Recreate Instance.

By default, ApsaraDB RDS creates an RDS instance that has the same specifications in the same zone as the original RDS instance. You can also create an RDS instance that has different specifications in a different zone than the original RDS instance.

Destroy an RDS instance

If an RDS instance is locked due to overdue payments or expiration, you can destroy the RDS instance in the recycle bin.

Warning After you destroy an RDS instance, only the cross-region backup files of the instance are retained. All regular data backup files, archived backup files, and log backup files of the instance are destroyed. Proceed with caution when you destroy an RDS instance. For more information about cross-region backup files, see Enable cross-region backups for an ApsaraDB RDS for MySQL instance.
  1. Log on to the RDS management console.
  2. In the left-side navigation pane, click Locked Instances. In the top navigation bar, select the region where the RDS instance resides.
  3. Find the RDS instance and click Destroy.

References