This document describes how to restore TencentDB for MongoDB data in the console.
- The oplog space of an instance is a capped collection. When the collection space is used up, newly inserted elements will overwrite the initial header elements. If the oplog space is overwritten, backup and restoration may fail, and it will be impossible to guarantee the time point for data restoration. Therefore, please set a reasonable oplog space size based on your business conditions.
- Please pay close attention to the Oplog Time Difference metric in System Monitoring on the instance management page. The smaller the metric value is, the greater the risk of oplog being overwritten when your business has frequent write, update, and deletion operations.
The instance data has been backed up. For more information, please see Backing up Data.
Within 48 hours after the rollback of entire instance is completed, you need to access the temp instance and confirm the data rolled back. For the temp instance, you can choose to perform:
- "Promotion": promote the temp instance to a formal instance independent of the original instance for use by the business.
- "Replacement": replace the original instance with the temp instance (the private IP of the original instance will be bound to the temp instance).
If no operation is performed after 48 hours, the temp instance will be terminated by the system.
- As physical backup does not support database table rollback, you cannot select database table rollback if there is a physical backup in the current backup list.
- A single database table rollback task currently supports up to 20 database tables.
- Sharded clusters v3.6 do not support database table rollback.