You can recover the data in TencentDB for MongoDB by following the steps below。
Step 1: In the backup recovery list, click Rollback for any backup file to open the rollback page, where you can specify the time and type of the rollback (instance rollback and table rollback). See below figure for details.
- Click the Instance Rollback button:
- Select rollback time:
- Select rollback type:
Step 2: When you select Instance Rollback, the system creates a temporary instance free of charge to store the rollback data. The user name and password of the temporary instance are the same as those of the original instance. The original instance remains unchanged and the business will not be affected.
Step 3: When you select Table Rollback, the system performs rollback in the original instance according to the database table selected and the name of the rolled-back table and the rollback time. You’ll need to confirm that the rolled-back data is correct after the table rollback finishes.
Step 4: You’ll need to access the temporary instance to confirm the rolled-back data is correct within 48 hours after the instance rollback is completed.
For the temporary instance created for the rollback, you can perform:
- Conversion: Convert the temporary instance to a formal business instance independent of the original instance.
- Replacement: Replace the original instance with the temporary instance (bind the private IP of the original instance to the temporary instance).
If no action is performed within 48 hours, the temporary instance will be terminated.
- The oplog space of an instance is a capped collection. When the collection space is used up, new inserted elements will overwrite the initial head elements. To avoid backup and recovery failures caused by overwritten oplog space, set a reasonable oplog space size.
- When you frequently write, delete or update the data in the instance, you can schedule multiple backups per day to prevent the oplog from being overwritten during the gap time between two backup.
- If the oplog space is overwritten during the gap time between two backup, the data recovery time may not be guaranteed.
