ApsaraDB for MongoDB provides a recycle bin to store expired, overdue, and released instances. You can unlock, rebuild, or instantly delete instances in the recycle bin.

Prerequisites

The instance is a standalone or replica set instance.

Instance states and allowed operations

On the Recycle page, you can query all expired, overdue, and released instances.

  • The following table describes the expired and overdue instances that enter the Recycle.
    Billing method Instance status Operation and impact
    Subscription From the first to seventh day after an instance expires, the instance is locked and cannot be accessed.
    • Click Renew to renew the instance. The instance becomes running after it is renewed.
      Note You can change the instance configurations when you renew an instance.
    • Click Destroy to release the computing resources and data of the instance. This operation is irreversible.
    On the eighth day after the instance expires, ApsaraDB for MongoDB releases the computing resources of the instance, but keeps the data for another eight days. The system sends an SMS or email to notify you that the instance is released.
    • Click Rebuild to create an instance and restore the data to this new instance. The time that is required for the restoration varies based on the performance and data volume of your RDS instance.
      Note For a standalone instance, you cannot click Rebuild to restore the data or configurations.
    • Click Destroy to release the computing resources and data of the instance. This operation is irreversible.
    On the sixteenth day after an instance expires, the data of the instance is deleted. The instance is permanently deleted. Its data cannot be restored.
    Warning To retain the data in the instance, you must renew the instance before it is deleted. Otherwise, the data cannot be restored.
    Pay-as-you-go

    On the first day (within 24 hours) after your instance becomes overdue, the instance remains running and does not enter the recycle bin. The system sends an SMS or email to notify you that the instance is released.

    You can renew the instance to prevent it from being disabled.

    After 24 hours, the instance is Disabled in the instance list and Locked in the recycle bin. You cannot read or write data.

    • You can renew the instance to restore the instance to the running state.
    • Click Destroy to release the computing resources and data of the instance. This operation is irreversible.
    On the eighth day after the instance becomes overdue, ApsaraDB for MongoDB releases the computing resources of the instance, but keeps the data for another eight days.
    • After you renew the instance, click Rebuild to rebuild the instance that enters the recycle bin due to overdue payment or manual release. This method restores the data to a new instance.
      Note For a standalone instance, you cannot click Rebuild to restore the data or configurations.
    • Click Destroy to release the computing resources and data of the instance. This operation is irreversible.
    On the sixteenth day after an instance becomes overdue, the data of the instance is deleted. The instance is permanently deleted. Its data cannot be restored.
    Warning To retain the data in the instance, you must renew the instance before it is deleted. Otherwise, the data cannot be restored.
  • For a pay-as-you-go instance that you manually release, it is deleted eight days after it enters the recycle bin. You can click Rebuild or Destroy before the instance is deleted.

Procedure

  1. Log on to the ApsaraDB for MongoDB console.
  2. In the upper-left corner of the page, select the resource group and the region of the target instance.
  3. In the left-side navigation pane, click Recycle.
  4. On the Recycle page, perform the following operations:
    1. Click More icon > Renew in the Actions column corresponding to the Instance ID/Name to renew the instance.
      Note
      • You can click Renew within seven days after a subscription instance expires.
      • You can click Renew within 24 hours after a pay-as-you-go instance becomes overdue.
    2. Click More icon > Rebuild in the Actions column corresponding to the Instance ID/Name to clone a new instance and restore the data of the original instance.
      Note
      • You can click Rebuild from the eighth to fifteenth day after a subscription instance expires.
      • You can click Rebuild from the eighth to fifteenth day after a pay-as-you-go instance is released.
      • For a standalone instance, you cannot click Rebuild to restore the data or configurations.
    3. Click More icon > Destroy in the Actions column corresponding to the Instance ID/Name to delete the expired subscription instance.