All Products
Search
Document Center

ApsaraDB RDS:Manage ApsaraDB RDS for SQL Server instances in the recycle bin

Last Updated:Feb 18, 2024

If an ApsaraDB RDS for SQL Server instance is released due to expiration or overdue payments, the RDS instance is moved to the recycle bin. You can unlock or rebuild the RDS instance in the recycle bin within a period of time to ensure business continuity. You can also destroy the RDS instance in the recycle bin to ensure data security.

Example

You have a subscription RDS instance that is automatically locked due to expiration. To restore business data, you can use the following methods:

  • You can renew and unlock the RDS instance within 15 days after it is locked. For more information, see Unlock an RDS instance that has expired.

  • If the RDS instance is not renewed within 15 days after its expiration, it will be released and can no longer be renewed or unlocked. The backup files of the RDS instance are retained for eight days. During the eight-day retention period, you can restore the data of the RDS instance to a new RDS instance by using the backup files. For more information, see Rebuild an RDS instance.

  • After the eight-day retention period elapses, the system permanently deletes the backup files of the instance. The backup files cannot be restored.

Note

You can go to the recycle-bin page in the ApsaraDB RDS console to view the Last Recoverable Time of the RDS instance.

Usage notes

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 is a read-only RDS instance.

Important

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.

For more information, see Overdue payments.

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 or subscription RDS instance that is created seven days ago or earlier is manually released, the backup files of the RDS instance are retained for eight days. During the eight-day retention period, you can restore the data of the RDS instance to a new RDS instance by using the backup files.

Important
  • After the eight-day retention period elapses, the system permanently deletes the backup files of the instance. The backup files cannot be restored.

  • However, the backup files that are generated by using the cross-region backup feature for the RDS instance are retained. For more information about the cross-region backup feature, see Use the cross-region backup feature.

  • After the RDS instance is rebuilt, the data of the original RDS instance is restored to a new RDS instance. By default, the system 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. After an RDS instance is rebuilt, the new RDS instance does not inherit the ID and 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 of an instance, see View and change the endpoints and port numbers.

Limits

  • 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.

  • Serverless RDS instances cannot be rebuilt from the recycle bin. For more information, see Overview.

Procedure

  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 that is locked and click Rebuild.

Destroy an RDS instance

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

Warning

After you destroy an RDS instance, all data backup files of the instance are destroyed. Proceed with caution.

  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.

What to do next