- Release Notes and Announcements
- User Guide
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Access Management
- Instance Management
- Node Management
- Version Upgrade
- Monitoring
- Backup and Rollback
- Data Security
- SSL Authentication
- Database Management
- Multi-AZ Deployment
- Public Network Access
- Disaster Recovery/Read-Only Instances
- Parameter Configuration
- Recycle Bin
- Task Management
- Performance Optimization
- Data Migration Guide
- Best Practice
- Optimizing Indexes to Break Through Read/Write Performance Bottlenecks
- Troubleshooting Mongos Load Imbalance in Sharded Cluster
- Troubleshooting Excessive Slow Queries
- Fixing High CPU Utilization in MongoDB Instance Based on DBbrain
- Troubleshooting Excessive Connections
- Troubleshooting High Request Latency Based on Slow Log
- Troubleshooting High CPU Utilization
- Considerations for Using Shard Clusters
- Sample of Reading and Writing Data in MongoDB Instance
- Export and Import
- Troubleshooting MongoDB Connection Failures
- Performance Fine-Tuning
- Ops and Development Guide
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- RenameInstance
- OfflineIsolatedDBInstance
- ModifyDBInstanceSpec
- IsolateDBInstance
- DescribeSpecInfo
- DescribeDBInstances
- DescribeClientConnections
- CreateDBInstanceHour
- AssignProject
- RenewDBInstances
- DescribeSlowLogs
- DescribeSlowLogPatterns
- InquirePriceRenewDBInstances
- InquirePriceModifyDBInstanceSpec
- InquirePriceCreateDBInstances
- DescribeDBInstanceDeal
- DescribeSecurityGroup
- DescribeInstanceParams
- ModifyDBInstanceSecurityGroup
- ModifyDBInstanceNetworkAddress
- Backup APIs
- Account APIs
- Task APIs
- Other APIs
- Data Types
- Error Codes
- Instance Connection
- FAQs
- Service Agreement
- Glossary
- Contact Us
- Release Notes and Announcements
- User Guide
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Access Management
- Instance Management
- Node Management
- Version Upgrade
- Monitoring
- Backup and Rollback
- Data Security
- SSL Authentication
- Database Management
- Multi-AZ Deployment
- Public Network Access
- Disaster Recovery/Read-Only Instances
- Parameter Configuration
- Recycle Bin
- Task Management
- Performance Optimization
- Data Migration Guide
- Best Practice
- Optimizing Indexes to Break Through Read/Write Performance Bottlenecks
- Troubleshooting Mongos Load Imbalance in Sharded Cluster
- Troubleshooting Excessive Slow Queries
- Fixing High CPU Utilization in MongoDB Instance Based on DBbrain
- Troubleshooting Excessive Connections
- Troubleshooting High Request Latency Based on Slow Log
- Troubleshooting High CPU Utilization
- Considerations for Using Shard Clusters
- Sample of Reading and Writing Data in MongoDB Instance
- Export and Import
- Troubleshooting MongoDB Connection Failures
- Performance Fine-Tuning
- Ops and Development Guide
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- RenameInstance
- OfflineIsolatedDBInstance
- ModifyDBInstanceSpec
- IsolateDBInstance
- DescribeSpecInfo
- DescribeDBInstances
- DescribeClientConnections
- CreateDBInstanceHour
- AssignProject
- RenewDBInstances
- DescribeSlowLogs
- DescribeSlowLogPatterns
- InquirePriceRenewDBInstances
- InquirePriceModifyDBInstanceSpec
- InquirePriceCreateDBInstances
- DescribeDBInstanceDeal
- DescribeSecurityGroup
- DescribeInstanceParams
- ModifyDBInstanceSecurityGroup
- ModifyDBInstanceNetworkAddress
- Backup APIs
- Account APIs
- Task APIs
- Other APIs
- Data Types
- Error Codes
- Instance Connection
- FAQs
- Service Agreement
- Glossary
- Contact Us
Terminated instances will be put into the recycle bin and can be restored.
Overview
Tencent Cloud recycle bin offers a mechanism for repossessing cloud services. If your account balance is sufficient, you can restore terminated instances that are still in the recycle bin.
Version Description
Currently, TencentDB for MongoDB 3.2, 3.6, 4.0, 4.2, 4.4, and 5.0 support instance repossession.
Note
The repossession of instances in different billing modes is as described below:
Retention period: Instances will be retained in the recycle bin for 7 calendar days.
Expiration processing: Instances that are not renewed within 7 calendar days will be released and cannot be restored.
Note:
The system will send you a renewal notification 7 days before the expiration of a TencentDB instance. On the 8th day after expiration, the instance will become unavailable and be moved to the recycle bin.
Retention period: If your account has no overdue payments, terminated instances will be retained in the recycle bin for 3 days.
Expiration processing: Instances that are not renewed before the retention period ends will be released and cannot be restored.
Note:
After the account balance becomes 0, instances will be automatically shut down and moved from the instance list to the recycle bin, and the billing will stop in 24 hours.
You cannot restore pay-as-you-go instances from the recycle bin if your account has overdue payments. You need to top up your account first.
Pay-as-you-go instances are retained in the recycle bin for a maximum of 3 days. You need to top up your account in time to restore the instances.
Prerequisites
The TencentDB for MongoDB instance has been terminated.
Your Tencent Cloud account balance is sufficient.
Directions
Instances in the recycle bin can be renewed, restored, or eliminated.
Viewing an instance in the recycle bin
1. Log in to the TencentDB for MongoDB console.
2. On the left sidebar, select MongoDB > Recycle Bin.
3. Above the Instance List on the right, select the region.
4. On the Recycle Bin page on the right, you can see the list of instances in the recycle bin.
Restoring one instance
1. In the instance list in the recycle bin, find the target instance and click Restore in the Operation column.
2. In the Restore Instance window, confirm the instance information and click OK.
The instance will return to their original instance list from the recycle bin.
Batch restoring instances
1. In the instance list in the recycle bin, select the target instances.
2. Click Batch Restore above the list, confirm the instance information in the Restore Instance window, and click OK.
The instance will return to their original instance list from the recycle bin.
Eliminating an instance
1. In the instance list in the recycle bin, find the target instance and click Eliminate Now in the Operation column.
2. In the Instance Elimination window, confirm the instance information and click OK.
Note:
The instance will be completely eliminated, and its data will not be recoverable. Therefore, you need to back up the data in advance.
Yes
No
Was this page helpful?