This topic describes how to manage ApsaraDB RDS for PostgreSQL instances in the recycle bin.
Overview
You can unlock, rebuild, or destroy the RDS instances that are moved to the recycle bin.
For example, your subscription RDS instance is locked due to expiration and moved to the recycle bin. You can unlock the RDS instance by renewing it within seven days. 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.
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 |
|
|
Unlock an RDS instance
Unlock a pay-as-you-go RDS instance whose payment is overdue
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.
Renew and unlock a subscription RDS instance
If your subscription RDS instance is locked due to expiration, you can renew the RDS instance in the recycle bin within seven days. If you do not renew the RDS instance within seven days, the RDS instance is released.
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 RDS instance that you want to renew.
Find the required RDS instance and click Unlock in the Operation column to renew the RDS instance.
After the RDS instance is renewed, the RDS instance is immediately restored to normal.
Rebuild an RDS instance
If the RDS instance that is moved the recycle bin is in the Released state, its backup data is retained for eight days. During this period, you can rebuild the instance and restore the data to a new RDS instance. For more information, see Overdue payments.
Log on to the ApsaraDB RDS console.
In the left-side navigation pane, click Recycle Bin. In the top navigation bar, select the region in which the RDS instance resides.
Find the RDS instance and click Rebuild.
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 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 View and change the endpoints and port numbers of an ApsaraDB RDS for PostgreSQL instance.
You cannot rebuild an RDS instance that uses a phased-out instance type, database version, or storage type from the recycle bin. For more information, see the following topics:
Destroy an RDS instance
If the RDS instance that is moved the recycle bin is in the Released state, you can destroy the instance.
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 RDS instance are destroyed. Proceed with caution. For more information about cross-region backup files, see Enable cross-region backups for an ApsaraDB RDS for MySQL instance.
Log on to the ApsaraDB RDS console.
In the left-side navigation pane, click Recycle Bin. In the top navigation bar, select the region in which the RDS instance resides.
Find the RDS instance and click Destroy in the Actions column.