After an RDS-PostgreSQL instance is frozen or unsubscribed, it enters the instance recycle bin, where you can recover or rebuild the instance.
Scenario Example
If a user has an RDS-PostgreSQL instance in Package Cycle mode which is frozen due to expiration, the user can renew and unfreeze the instance in the recycle bin to restore it within seven days.
If a user unsubscribes an instance, the instance will enter the instance recycle bin, which can be rebuilt and restored within seven days.
A user has an RDS-PostgreSQL instance in Payment by Volume mode. When it enters the recycle bin, it can automatically unfreeze and restore, and be moved out from the recycle bin if the account is recharged.
Constraint Conditions
The following instances cannot be recovered from the recycle bin:
1. De-registered instances.
2. Unsubscribed read-only instances.
3. Database proxy instances.
Instance Restoration
1. Log in to the eSurfing Cloud Portal. Click Console and select the corresponding resource pool, such as East China 1.
2. In the upper left corner of the Console, click
and select Region and Project.
3. Select Database > RDS-PostgreSQL and go to the PostgreSQL Console.
4. Click Instance Recycle Bin in the left sidebar to go to the page.
5. Find the instance you want to operate and click the Restore button.
6. For an unsubscribed instance (the status is displayed as Unsubscribed), the system will jump to the Rebuild Instance page.
7. For a frozen instance (the status is displayed as Frozen), the system will jump to the Renew Instance page.
Note
• For Payment by Volume frozen instances, you do not need to restore them from the recycle bin. They can be automatically restored after the account is recharged with sufficient amounts.