After you release or unsubscribe from an RDS instance, if the RDS instance meets the recycling requirements, it is moved to the recycle bin. You can unlock or rebuild the RDS instance in the recycle bin within a specific period of time to ensure business continuity. If the RDS instance is locked due to overdue payments or expiration, you can 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 Renew and unlock an RDS instance.
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 RDS instance. The data of the RDS instance cannot be restored.
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
ApsaraDB RDS for PostgreSQL determines whether to move an instance to the recyle bin based on its billing method and instance type. The following table describes the instances that are moved and not moved to the recycle bin.
Instances that are moved to the recycle bin | Instances that are not moved to the recycle bin |
|
|
The RDS instances that run SQL Server 2008 R2 are no longer available for purchase. If your existing RDS instance that runs SQL Server 2008 R2 is locked due to expiration or is released, you can only unlock the instance in the recycle bin. You cannot rebuild the instance. For more information, see Unlock an RDS instance that has expired and [EOS/Discontinuation] Supplementary service terms for ApsaraDB RDS instances that run SQL Server 2008 R2.
If your RDS instance is moved to the recycle bin, the database accounts that are created for the RDS instance are released. If you renew your RDS instance that is moved to the recycle bin to unlock the RDS instance, you can re-create database accounts after the RDS instance is restored.
Top up your account balance and unlock an RDS instance
If your pay-as-you-go RDS instance is locked due to overdue payments, log on to the Billing Management console and verify that a valid payment method is specified for your Alibaba Cloud account.
For more information, see Overdue payments.
Renew and unlock an RDS instance
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.
Log on to the ApsaraDB RDS console.
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 manage.
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 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.
After the eight-day retention period elapses, the system permanently deletes the backup files of the instance. The data of the RDS instance 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
Log on to the ApsaraDB RDS console.
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.
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.
After you destroy an RDS instance, all data backup files of the instance are destroyed. Proceed with caution.
Go to the Instances page.
In the left-side navigation pane, click Recycle Bin. In the top navigation bar of the page that appears, select the region of the required RDS instance.
Find the required RDS instance and click Destroy in the Operation column. In the message that appears, click OK.
What to do next
If you store backup files of an RDS instance on a local device, you can upload the backup files to your Object Storage Service (OSS) bucket. Then, you can restore the data of a backup file from the OSS bucket to an RDS instance. For more information, see Migrate the full backup data of a self-managed SQL Server instance to an ApsaraDB RDS instance that runs SQL Server 2008 R2 with cloud disks or runs SQL Server 2012 or later and Overview of data migration methods.
If you want to release a pay-as-you-go RDS instance or unsubscribe from a subscription RDS instance, you can follow the instructions in Release or unsubscribe from an RDS instance.