The recycle bin of ApsaraDB for MongoDB is used to retain expired, overdue, and released MongoDB instances. You can renew, unlock, rebuild, or destroy the instances in the Recycle Bin.
Usage notes
Released standalone instances cannot be restored from the Recycle Bin.
Instances for which transparent data encryption (TDE) is enabled cannot be restored from the Recycle Bin after the instances are released.
To restore instances for which disk encryption is enabled from the recycle bin, make sure that the Key Management Service (KMS) keys of the instances are available.
Supported operations and impacts
On the Recycle Bin page, you can view all expired, overdue, and manually released instances.
Architecture | Storage type | Operation |
Replica set instance | Local disks |
|
Enterprise SSDs (ESSDs) |
| |
Sharded cluster instance | Local disks |
|
ESSDs |
|
The supported operations and impacts vary based on the instance architecture and billing method.
ESSDs
Architecture | Billing method | Instance status | Operation and impact |
Replica set instance Sharded cluster instance | Subscription | For the first 15 days after a subscription instance expires, the instance is locked and cannot be accessed. |
|
On the 16th day after the instance expires, ApsaraDB for MongoDB releases the computing resources of the instance but retains the instance data based on the backup retention policy that you configure.
|
| ||
If the policy specifies that instance data does not need to be retained, the data is not retained. | The instance is permanently deleted, and the instance data cannot be restored. | ||
Pay-as-you-go | For the first 15 days after the instance becomes overdue, the instance is displayed as Disabled in the instance list and Locked in the recycle bin. In this case, you cannot read data from or write data to the instance. |
| |
ApsaraDB for MongoDB releases the computing resources of an instance that runs as expected on the 16th day after the instance becomes overdue or an instance that is manually released, but retains the instance data based on the backup retention policy that you configure.
|
| ||
If the policy specifies that instance data does not need to be retained, the data is not retained. | The instance is permanently deleted, and the instance data cannot be restored. |
Local disks
Architecture | Billing method | Instance status | Operation and impact |
Replica set instance | Subscription | For the first 15 days after a subscription instance expires, the instance is locked and cannot be accessed. |
|
On the 16th day after the instance expires, ApsaraDB for MongoDB releases the computing resources of the instance but retains the instance data for another seven days. The system notifies you about the status of the instance by SMS or email. |
| ||
On the 23rd day after the instance expires, the instance data is cleared. | The instance is permanently deleted, and the instance data cannot be restored. | ||
Pay-as-you-go | For the first 15 days after the instance becomes overdue, the instance is displayed as Disabled in the instance list and Locked in the recycle bin. In this case, you cannot read data from or write data to the instance. |
| |
On the 16th day after the instance becomes overdue, ApsaraDB for MongoDB releases the computing resources of the instance but retains the instance data for another seven days. |
| ||
On the 23rd day after the instance becomes overdue, the instance data is cleared. | The instance is permanently deleted, and the instance data cannot be restored. | ||
Sharded cluster instance | Subscription | For the first 15 days after a subscription instance expires, the instance is locked and cannot be accessed. |
|
Pay-as-you-go | For the first 15 days after the instance becomes overdue, the instance is displayed as Disabled in the instance list and Locked in the recycle bin. In this case, you cannot read data from or write data to the instance. Note Pay-as-you-go instances that are manually released are not retained in the recycle bin and cannot be rebuilt. |
|
Procedure
Log on to the ApsaraDB for MongoDB console.
In the left-side navigation pane, click Recycle Bin.
In the upper-left corner of the page that appears, select the resource group and region to which the instance belongs.
On the Recycle Bin page, click the Replica Set Instances or Sharded Cluster Instances tab.
On the Recycle Bin page, click Renew, Rebuild, or Destroy.
Renew an instance
NoteYou can click Renew to renew only expired or overdue instances in the Locking state.
Find the instance that you want to renew and click the
icon in the Actions column. Then, select Renew. On the Renew page, specify a subscription duration.
Read and select the Terms of Service, and then click Buy Now.
On the Purchase page, complete the payment by following the on-screen instructions.
Rebuild an instance
NoteYou can click Rebuild to rebuild only instances in the Released state.
Find the instance that you want to rebuild and click the
icon in the Actions column. Then, select Rebuild. On the Clone Instance page, specify the region, zone, and specifications for a new instance, and then click Buy Now.
On the Confirm Order page, view configurations that you specify, read and select the Terms of Service, and then complete the payment by following the on-screen instructions.
Destroy an instance
WarningAfter an instance is destroyed, the instance data is cleared and cannot be restored.
To destroy an instance, change the backup retention policy to Delete all backup sets when you release the instance.
Find the instance that you want to destroy and then click the
icon on the left side of the instance to view the backup list. Click Modify Backup Retention Policy.
In the Modify Backup Retention Policy dialog box, select Delete all backup sets when you release the instance and then click OK.