How to operate expired, overdue, and released instances in the recycle bin - ApsaraDB for MongoDB

The recycle bin for ApsaraDB for MongoDB retains expired, overdue, and released MongoDB instances. In the Recycle Bin, you can renew and unlock, rebuild, or destroy these instances.

Notes

Released standalone instances cannot be recovered from the Recycle Bin.
Local disk sharded cluster instances cannot be recovered from the Recycle Bin after they are released.
Released instances for which Transparent Data Encryption (TDE) is enabled cannot be recovered from the Recycle Bin.
To recover instances for which disk encryption is enabled from the recycle bin, you need to ensure that the KMS keys of the instances are available. Otherwise, the instances cannot be recovered properly.

Supported operations and impacts

You can find recently expired, overdue, and manually released instances in the Recycle Bin.

Architecture	Storage class	Operation
ReplicaSet	Local disks	Renew the instance from the recycle bin. Rebuild the instance from the recycle bin.
ReplicaSet	Enterprise SSDs (ESSDs)	Renew the instance from the recycle bin. Rebuild the instance from the recycle bin. Modify the deleted backup retention policy of the instance from the recycle bin.
Sharded cluster instance	Local disks	Renew the instance from the recycle bin.
Sharded cluster instance	ESSDs	Renew the instance from the recycle bin. Rebuild the instance from the recycle bin. Modify the deleted backup retention policy of the instance from the recycle bin.

The supported operations and impacts vary based on the instance architecture and billing method.

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.	Renew: Renew the instance to ensure the normal running status of the MongoDB instance.
		From days 16 to 30 after the instance expires, it is locked and cannot be accessed.	Renew: The instance resumes normal operation after successful renewal. Destroy: Releases the computing resources and data of the instance. This operation cannot be undone. To perform the destroy operation, you can modify the backup retention policy to Delete all backup sets when you release the instance.
		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: If your backup retention policy is Delete all backup sets when you release the instance: The most recent backup remains in the recycle bin for 0 to 7 days after the instance is released. You can restore data to a new instance before this backup is permanently deleted. If your backup retention policy is Automatically back up data when you release the instance and retain the backup set for the instance for a long time: The backup is retained long-term, and the recycle bin displays the most recent backup set of the instance. You can restore data to a new instance. If your backup retention policy is Automatically back up data when you release the instance and retain all backup sets for the instance for a long time: The backups are retained long-term, and the recycle bin displays all backup sets of the instance. You can restore data to a new instance.	Rebuild: Restore data to a new instance. The time required depends on the instance performance and data volume. Destroy: Release the computing resources and data of the instance, which cannot be recovered. To perform the destroy operation, you can modify the backup retention policy to Delete all backup sets when you release the instance.
		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.	Top Up: Add funds to your Alibaba Cloud account to ensure the normal operating status of your MongoDB instances.
		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.	Add Funds: Add funds to your Alibaba Cloud account to restore your MongoDB instance to Normal status. Destroy: Release the computing resources and data of the instance, which cannot be recovered. To perform the destroy operation, you can modify the backup retention policy to Delete all backup sets when you release the instance.
		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. If your backup retention policy is Delete all backup sets when you release the instance, the most recent backup remains in the recycle bin for 7 days after the instance is released. You can restore data to a new instance before this backup is permanently deleted. If your backup retention policy is 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 retained long-term in the recycle bin. You can restore data to a new instance at any time during this retention period. If your backup retention policy is 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 retained long-term in the recycle bin. You can restore data to a new instance at any time during the retention period.	Rebuild: After adding funds to your Alibaba Cloud account, click Rebuild to rebuild instances that have been transferred to the recycle bin due to overdue payment or manual release. This is achieved by restoring the data to a newly created instance. Destroy: Release the computing resources and data of the instance, which cannot be recovered. To perform the destroy operation, you can modify the backup retention policy to Delete all backup sets when you release the instance.
		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.	Renew: Renew the instance to ensure the normal running status of your MongoDB instance.
		From the 16th to the 30th day after the instance expires, the instance is in a locked state and cannot be accessed.	Renew: The instance returns to Normal status after renewal is successful. Destroy: Releases the computing resources and data of the instance. The instance cannot be recovered.
		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.	Rebuild: Restores data to a newly created instance. The restoration time depends on the instance performance and data volume. Destroy: Releases the computing resources and data of the instance, which cannot be recovered.
		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.	Top Up: Add funds to your Alibaba Cloud account to ensure the normal operating status of your MongoDB instances.
		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.	Add Funds: Add funds to your Alibaba Cloud account to restore the MongoDB instance to Normal running status. Destroy: Release the computing resources and data of the instance. The instance cannot be recovered.
		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.	Rebuild: After you recharge your Alibaba Cloud account, click Rebuild to rebuild instances that were transferred to the recycle bin due to overdue payment or manual release. This is done by restoring data to newly created instances. Destroy: Releases the computing resources and data of the instance, which cannot be recovered.
		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.	Renew: Renew the instance to ensure the normal running status of the MongoDB instance in the future.
	Subscription	From the 16th to the 30th day after the instance expires, the instance is in a locked state and cannot be accessed.	Renew: After successful renewal, the instance returns to Normal status. Destroy: Releases the computing resources and data of the instance, which cannot be recovered.
	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.	Top Up: Add funds to your Alibaba Cloud account to ensure the normal operating status of your MongoDB instances.
	Pay-as-you-go	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.	Add Funds: Add funds to your Alibaba Cloud account to restore your MongoDB instance to Normal status. Destroy: Release the computing resources and data of the instance. This operation cannot be undone.

Procedure

Log on to the MongoDB console.
In the navigation pane on the left, click Recycle Bin.
In the upper-left corner of the page, select the resource group and region where the instance is located.
On the Recycle Bin page, select Replica Set Instances or Sharded Cluster Instances.
On the Recycle Bin page, you can perform Renew, Rebuild, and Destroy operations.
Renew
Note
You can click Renew to renew only expired or overdue instances in the Locking state.
1. On the right side of the target instance, select > Renew.
2. On the Renew page, specify a subscription duration.
3. Read the Terms of Service and click Buy Now.
4. On the Purchase page, complete the payment by following the on-screen instructions.
Rebuild
Note
You can Rebuild only instances in the Released state.
1. To the right of the target instance, select > Rebuild.
2. On the Clone Instance page, specify the region, zone, and specifications for a new instance, and click Buy Now.
3. On the Confirm Order page, view the configuration details, read the Terms of Service, and complete the payment by following the on-screen instructions.
Destroy
Warning
After an instance is destroyed, the instance data is cleared and cannot be restored.
You can destroy an instance by changing the backup retention policy to Delete all backup sets when you release the instance. The steps are as follows:
1. Click the icon on the left side of the target instance to expand the backup list.
2. Click Modify Backup Retention Policy.
3. In the Modify Backup Retention Policy dialog box, select Delete all backup sets when you release the instance, and click OK.

Notes

Supported operations and impacts

Enterprise SSD (ESSD)

Local disks

Procedure

Renew

Rebuild

Destroy