This topic describes how to manage ApsaraDB MyBase for PostgreSQL instances in the recycle bin. You can unlock, recreate, or destroy instances in the recycle bin.

Description

An ApsaraDB MyBase for PostgreSQL instance is moved to the recycle bin in the following situations:
  • The instance is deleted.
  • The host on which the instance is deployed expires or has overdue payments.

Recreate an instance

After the host on which a subscription ApsaraDB MyBase for PostgreSQL instance is deployed expires, the instance is retained for a specified period of time. After the specified retention period ends, the instance is released. However, the data backup files of the instance are retained for eight more days. During the eight-day retention period, you can recreate an instance and restore the data of the original instance to the new instance. For more information, see Unlock or rebuild an expired or overdue ApsaraDB RDS instance.

Destroy an instance

If an ApsaraDB MyBase for PostgreSQL instance is deleted or if the host on which an ApsaraDB MyBase for PostgreSQL instance is deployed expires or has overdue payments, you can destroy the instance in the recycle bin.

Warning After you destroy an ApsaraDB MyBase for PostgreSQL instance, all the backup files except the Enable cross-region backups for an ApsaraDB RDS for PostgreSQL instance files of the instance are destroyed. The backup files that are destroyed include regular data backup files, archived backup files, and log backup files. Proceed with caution.
  1. Log on to the RDS management console.
  2. In the left-side navigation pane, click Locked Instances. In the upper-left corner of the page, select the region where the ApsaraDB MyBase for PostgreSQL instance that you want to destroy resides.
  3. Find the instance and click Destroy in the Actions column.