The Recycle Bin retains expired, overdue, and released ApsaraDB for MongoDB instances so you can recover or permanently destroy them without immediate data loss.
Limitations
The following instance types cannot be recovered from the Recycle Bin:
Released standalone instances
Local disk sharded cluster instances that have been released
Released instances with Transparent Data Encryption (TDE) enabled
Instances with disk encryption enabled whose KMS keys are unavailable cannot be recovered properly
Supported operations by architecture
The operations available in the Recycle Bin depend on the instance architecture and storage class.
| Architecture | Storage class | Available operations |
|---|---|---|
| Replica set | Local disks | Renew, Rebuild |
| Replica set | Enterprise SSD (ESSD) | Renew, Rebuild, Modify backup retention policy |
| Sharded cluster | Local disks | Renew |
| Sharded cluster | ESSD | Renew, Rebuild, Modify backup retention policy |
Available operations also vary by billing method. See the lifecycle tables below for details.
Enterprise SSD (ESSD)
Architecture | Billing method | Instance status | Operation and impact |
ReplicaSet Sharded cluster | Subscription | Within 1 to 15 days after the instance expires, the instance runs normally. |
|
From days 16 to 30 after the instance expires, it is locked and cannot be accessed. |
| ||
On the 31st day after the instance expires, its computing resources are released. The retention of data backups depends on your configured Backup Retention Policy:
|
| ||
After the backup retention period specified by your policy expires, all backups and data are permanently deleted. | The instance is completely destroyed, and the data cannot be recovered. | ||
Pay-as-you-go | From day 1 to day 15 after an Alibaba Cloud account has an overdue payment, the instance continues to run in the Normal state. |
| |
From the 16th to the 30th day after the Alibaba Cloud account has an overdue payment, the MongoDB instance is displayed as disabled in the instance list and locked in the recycle bin. Data cannot be read or written. |
| ||
On the 31st day after the Alibaba Cloud account becomes overdue or at the moment when the pay-as-you-go instance is manually released, its computing resources are released. The retention of data backups depends on your configured Backup Retention Policy.
|
| ||
After the instance backup retention policy expires, the instance data is no longer retained. | The instance is completely destroyed, and the data cannot be recovered. |
Local disks
Architecture | Billing method | Instance status | Operation and impact |
ReplicaSet | Subscription | Within the first 15 days after the instance expires, the instance runs normally. |
|
From the 16th to the 30th day after the instance expires, the instance is in a locked state and cannot be accessed. |
| ||
On the 31st day after the instance expires, the computing resource of the instance is released. The data is retained for another 7 days. You will receive a text message or email notification at this time. |
| ||
On the 38th day after the instance expires, the instance data is no longer retained. | The instance is completely destroyed, and the data cannot be recovered. | ||
Pay-as-you-go | From day 1 to day 15 after your Alibaba Cloud account has an overdue payment, your instances continue to run normally. |
| |
From the 16th to the 30th day after the Alibaba Cloud account has an overdue payment, the MongoDB instance is displayed as Disabled in the instance list and Locked in the recycle bin. The data cannot be read or written. |
| ||
On the 31st day after an Alibaba Cloud account has an overdue payment, the computing resources of the instance are released, but the data is retained for 7 more days. |
| ||
On the 38th day after an Alibaba Cloud account has an overdue payment, the data of the instance is no longer retained. | The instance is completely destroyed and the data cannot be recovered. | ||
Sharded cluster | Subscription | Within days 1 to 15 after the instance expires, the instance runs normally. |
|
From the 16th to the 30th day after the instance expires, the instance is in a locked state and cannot be accessed. |
| ||
Pay-as-you-go | Within days 1 to 15 after an Alibaba Cloud account has an overdue payment, the instance continues to run in the Normal state. |
| |
From days 16 to 30 after the Alibaba Cloud account becomes overdue, the MongoDB instance is displayed as Disabled in the instance list and Locked in the recycle bin, and you cannot read from or write to the data. Note Pay-as-you-go instances that are manually released are not retained in the recycle bin and cannot be rebuilt. |
|
Instance lifecycle by storage type
ESSD instances
Subscription
| Instance status | Available operations |
|---|---|
| Days 1–15 after expiry: instance runs normally. | Renew: Keep the instance running past its expiry date. |
| Days 16–30 after expiry: instance is locked and cannot be accessed. | Renew: Restore the instance to Normal status. Destroy: Release computing resources and data permanently. To destroy, first set the backup retention policy to Delete all backup sets when you release the instance. |
| Day 31 after expiry: computing resources are released. Data retention depends on your Backup Retention Policy: Delete all backup sets when you release the instance — the most recent backup is kept for 0–7 days. Automatically back up data when you release the instance and retain the backup set for the instance for a long time — the most recent backup is kept long-term. Automatically back up data when you release the instance and retain all backup sets for the instance for a long time — all backup sets are kept long-term. In all cases, you can rebuild a new instance from the retained backup. | Rebuild: Restore data to a new instance. Time varies by instance performance and data volume. Destroy: Release all remaining backups and data permanently. To destroy, set the backup retention policy to Delete all backup sets when you release the instance. |
| After the backup retention period expires. | The instance is completely destroyed and data cannot be recovered. |
Pay-as-you-go
| Instance status | Available operations |
|---|---|
| Days 1–15 after account becomes overdue: instance runs in Normal status. | Top Up: Add funds to your Alibaba Cloud account to keep instances running. |
| Days 16–30 after account becomes overdue: instance shows as Disabled in the instance list and Locked in the Recycle Bin. Data cannot be read or written. | Add Funds: Restore the instance to Normal status. Destroy: Release computing resources and data permanently. To destroy, set the backup retention policy to Delete all backup sets when you release the instance. |
| Day 31 after account becomes overdue, or when the instance is manually released: computing resources are released. Data retention depends on your Backup Retention Policy: Delete all backup sets when you release the instance — the most recent backup is kept for 7 days. Automatically back up data when you release the instance and retain the backup set for the instance for a long time — the most recent backup is kept long-term. Automatically back up data when you release the instance and retain all backup sets for the instance for a long time — all backup sets are kept long-term. In all cases, you can rebuild a new instance from the retained backup at any time during the retention period. | Rebuild: After adding funds, click Rebuild to restore data to a new instance. Destroy: Release all remaining backups and data permanently. To destroy, set the backup retention policy to Delete all backup sets when you release the instance. |
| After the backup retention period expires. | The instance is completely destroyed and data cannot be recovered. |
Local disk instances
Replica set
Subscription
| Instance status | Available operations |
|---|---|
| Days 1–15 after expiry: instance runs normally. | Renew: Keep the instance running past its expiry date. |
| Days 16–30 after expiry: instance is locked and cannot be accessed. | Renew: Restore the instance to Normal status after renewal. Destroy: Release computing resources and data. This operation cannot be undone. |
| Day 31 after expiry: computing resources are released. Data is retained for 7 more days. You will receive a notification by SMS or email. | Rebuild: Restore data to a new instance. Time varies by instance performance and data volume. Destroy: Release the remaining data permanently. This operation cannot be undone. |
| Day 38 after expiry. | The instance is completely destroyed and data cannot be recovered. |
Pay-as-you-go
| Instance status | Available operations |
|---|---|
| Days 1–15 after account becomes overdue: instance runs normally. | Top Up: Add funds to keep instances running. |
| Days 16–30 after account becomes overdue: instance shows as Disabled in the instance list and Locked in the Recycle Bin. Data cannot be read or written. | Add Funds: Restore the instance to Normal running status. Destroy: Release computing resources and data. This operation cannot be undone. |
| Day 31 after account becomes overdue: computing resources are released. Data is retained for 7 more days. | Rebuild: After adding funds, click Rebuild to restore data to a new instance. Destroy: Release the remaining data permanently. This operation cannot be undone. |
| Day 38 after account becomes overdue. | The instance is completely destroyed and data cannot be recovered. |
Sharded cluster
Subscription
| Instance status | Available operations |
|---|---|
| Days 1–15 after expiry: instance runs normally. | Renew: Keep the instance running past its expiry date. |
| Days 16–30 after expiry: instance is locked and cannot be accessed. | Renew: Restore the instance to Normal status after renewal. Destroy: Release computing resources and data. This operation cannot be undone. |
Pay-as-you-go
| Instance status | Available operations |
|---|---|
| Days 1–15 after account becomes overdue: instance runs in Normal status. | Top Up: Add funds to keep instances running. |
| Days 16–30 after account becomes overdue: instance shows as Disabled in the instance list and Locked in the Recycle Bin. Data cannot be read or written. Pay-as-you-go instances that are manually released are not retained in the Recycle Bin and cannot be rebuilt. | Add Funds: Restore the instance to Normal status. Destroy: Release computing resources and data. This operation cannot be undone. |
Access the Recycle Bin
Log on to the MongoDB console.
In the left navigation pane, click Recycle Bin.
In the upper-left corner, select the resource group and region where the instance is located.
Select the Replica Set Instances or Sharded Cluster Instances tab.
Renew
Only instances in the Locking state (expired or overdue) can be renewed.
To the right of the target instance, click  > Renew.
On the Renew page, specify a subscription duration.
Read the Terms of Service and click Buy Now.
On the Purchase page, complete the payment.
Rebuild
Only instances in the Released state can be rebuilt.
To the right of the target instance, click  > Rebuild.
On the Clone Instance page, specify the region, zone, and specifications for the new instance, then click Buy Now.
On the Confirm Order page, review the configuration details, read the Terms of Service, and complete the payment.
Destroy
Destroying an instance permanently deletes all instance data. This operation cannot be undone.
To destroy an instance, change its backup retention policy to Delete all backup sets when you release the instance:
Click the  icon to the left of the target instance to expand 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 click OK.