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.

Important The system backs up an RDS instance when the RDS instance is being deleted. If the RDS instance is being backed up and the deletion process is not complete, the recycle bin feature of the RDS instance is unavailable.

Sample scenario

You have a subscription RDS instance that is locked due to expiration. You can unlock and renew the RDS instance in the recycle bin within seven days after the expiration. For more information, see Unlock an RDS instance that has expired. After the seven days, you can only rebuild the RDS instance in the recycle bin and restore the data of the RDS instance to a new RDS instance. For more information, see Rebuild an RDS instance.

Functionality

If you manually release a pay-as-you-go RDS instance or unsubscribe from a subscription RDS instance, or a subscription RDS instance is automatically released after expiration, the RDS instance is moved to the recycle bin. An RDS instance is not moved to the recycle bin in the following scenarios:
  • You manually release or unsubscribe from the RDS instance 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 belongs to a dedicated cluster or is a read-only RDS instance.
  • If your RDS instances uses a phased-out instance type and is moved to the recycle bin, you can rebuild the RDS instance from the recycle bin to an instance that uses an available instance type. You can also retain the last backup file of your RDS instance before the instance is released. Then, you can use the backup file to rebuild the RDS instance from the recycle bin to an instance that uses an available instance type.

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 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 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 is manually released, the backup files of the RDS instance are retained for eight days. During the eight-day retention period, you can use the rebuilding feature to restore the data of the RDS instance to a new RDS instance from the backup files. After the eight-day retention period elapses, only the backup files that meet the specified conditions are retained.
Note
  • After the retention period elapses, only the backup files that meet the following conditions are retained:
  • After an RDS instance is rebuilt, the data of the original RDS instance is restored to a new RDS instance. However, the new RDS instance does not inherit the ID or endpoint of the original RDS instance. You can change the endpoint of the new RDS instance to the endpoint of the original RDS instance. This way, your applications can connect to the new RDS instance by using the original endpoint. For more information about how to change the endpoint, see Change the internal or public endpoint and port number of an RDS instance.
Usage notes

If the Transparent Data Encryption (TDE) feature is enabled for an RDS instance, the backup files of the RDS instance cannot be used to rebuild the RDS instance. For more information, see Configure TDE for an ApsaraDB RDS for MySQL instance.

Procedure
  1. Log on to the ApsaraDB RDS console.
  2. In the left-side navigation pane, click Instances. In the top navigation bar, select the region in which the RDS instance resides.
  3. Find the RDS instance and click Rebuild.

By default, an RDS instance that uses the same specifications as the original RDS instance is created in the zone in which the original RDS instance resides.

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 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 instance and click Destroy.

References