All Products
Search
Document Center

ApsaraDB RDS:Manage ApsaraDB RDS for MySQL instances in the recycle bin

Last Updated:Nov 16, 2023

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 scenarios

Your subscription RDS instance is locked due to expiration and moved to the recycle bin. You can renew the RDS instance to unlock the RDS instance within seven days. For more information, see Unlock an RDS instance that has expired. If you do not renew the RDS instance within seven days, you can only rebuild the RDS instance from the recycle bin and restore the data of the RDS instance to a new RDS instance. For more information, see Rebuild an RDS instance.

Feature description

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 the RDS instance 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 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 Recycle Bin. In the top navigation bar of the page that appears, select the region of the RDS instance that you want to renew.

  3. Find the RDS instance and click Unlock in the Operation column 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:

    • The RDS instance runs MySQL, PostgreSQL, or SQL Server, and the cross-region backup retention period has not ended. The backup files are retained until the cross-region backup retention period ends. For more information, see Use the cross-region backup feature.

    • The RDS instance runs MySQL, and you have determined to retain the backup files of the RDS instance after the RDS instance is released. For more information, see Enable the automatic backup feature.

  • 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, see View and manage instance endpoints and ports.

Prerequisites

If the RDS instance uses cloud disks, the network type of the instance must be VPC.

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.

Procedure

  1. Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Recycle Bin.

  2. In the top navigation bar of the page that appears, select the region of the RDS instance that you want to renew.

  3. Find the RDS instance and click Rebuild in the Operation column.

  4. Read and select Terms of Service, and click Pay Now.

  5. Click Subscribe. This step is required only for subscription RDS instances.

By default, the rebuilt RDS instance uses the same specifications as the original RDS instance and resides in the same zone as 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. For more information, see Use the cross-region backup feature.

  1. Log on to the ApsaraDB RDS console.
  2. In the left-side navigation pane, click Recycle bin. In the top navigation bar of the page that appears, select the region of the RDS instance that you want to destroy.

  3. Find the RDS instance and click Destroy in the Operation column. In the message that appears, click OK.

References