tencent cloud

TencentDB for MongoDB

Release Notes and Announcements
Release Notes
Announcements
User Guide
Product Introduction
Overview
Strengths
Use Cases
Cluster Architecture
Product Specifications
Features
Regions and AZs
Terms
Service Regions and Service Providers
Purchase Guide
Billing Overview
MongoDB Pricing
Billing Formula
Payment Overdue
Backup Space Billing
Configuration Adjustment Billing
Getting Started
Quickly Creating an Instance
Connecting to a TencentDB for MongoDB Instance
Reading/Writing Database
Operation Guide
Access Management
Instance Management
Node Management
Version Upgrade
Network Configuration
Monitoring
Backup and Rollback
Database Audit
Data Security
SSL Authentication
Log Management
Database Management
Multi-AZ Deployment
Disaster Recovery/Read-Only Instances
Parameter Configuration
Recycle Bin
Task Management
Performance Optimization
Data Migration Guide
Practical Tutorial
Optimizing Indexes to Break Through Read/Write Performance Bottlenecks
Troubleshooting Mongos Load Imbalance in Sharded Cluster
Considerations for Using Shard Clusters
Sample of Reading and Writing Data in MongoDB Instance
Methods for Importing and Exporting Data Based on CVM Connected with MongoDB
What to Do for Errors of Repeated Instance Creation and Deletion of Databases with the Same Names?
Troubleshooting MongoDB Connection Failures
Shard Removal Task: Guide for Confirming the Progress and Troubleshooting Issues
Performance Fine-Tuning
Ops and Development Guide
Development Specifications
Command Support in Sharded Cluster v3.2
Command Support in v3.6
Development Ops
Troubleshooting
Increased Slow Queries
Number of Connections Exceeding Limit
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Backup APIs
Account APIs
Other APIs
Task APIs
Introduction
Data Types
Error Codes
Instance Connection
Shell Connection Sample
PHP Connection Sample
Node.js Connection Sample
Java Connection Sample
Python Connection Sample
Python Read/Write Sample
Go Connection Sample
PHP Reconnection Sample
Product Performance
Test Environment
Test Method
Test Result
FAQs
Cost
Features
Sharded Cluster
Instance
Rollback and Backup
Connection
Data Migration
Others
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us

Batch Rollback

PDF
Focus Mode
Font Size
Last updated: 2026-02-06 21:18:05

Operation scenarios

Batch rollback refers to the process of rolling back the database collection data of multiple instances at once, restoring the data of multiple instances to the source instance in a single batch operation. Database collections rollback or Key Flashback to the current instance supports batch operations, allowing multiple instance database collections to be rolled back at once. The newly rolled back collections are named with the suffix _bak. After the rollback is complete, the database name can be changed as needed to improve the efficiency and accuracy of data recovery and avoid the cumbersome process of manual individual recovery. Moreover, MongoDB supports peeking at all batch rollback historical tasks under the current account, helping you to quickly understand past operation records for convenient unified operation and management.

Starting batch rollback task

1. Sign in to the MongoDB Console.
2. In the MongoDB dropdown menu on the left navigation bar, select Batch Rollback.
3. On the Rollback Task page, click Initiate Rollback to enter the Batch Rollback Database Table Data Configuration Wizard. Here, you can configure the batch rollback database table task and initiate a rollback task. For specific operations, please refer to Database Table Rollback.


Peek Batch Rollback Tasks

1. Sign in to the MongoDB Console.
2. In the MongoDB dropdown menu on the left navigation bar, select Batch Rollback.
3. On the Rollback Task page, you can find all batch rollback tasks under the current account, as shown below. You can filter the tasks you want to peek at by selecting a time range in the time box.


Batch Modify Rollback Collection Names

Database collection rollback does not directly roll back data to the original table, but instead creates a Backup file. For example, if the original database table is named test, a new table named test_bak will be created. As shown in the figure below, Rollback Collection Name is the name of the newly created table. After the rollback task is completed, you can batch modify the table names as needed.

1. Sign in to the MongoDB Console.
2. In the MongoDB dropdown menu on the left navigation bar, select Batch Rollback.
3. On the Batch Modify Collection Names tab in Batch Collection Rollback, find the rolled-back tasks and select the instances whose table names you intend to modify. In their Operations column, click Batch Modify Collection Names to see the information of the collections to be modified on the right zone, including Original Collection Name, New Original Table Name, Rollback Collection Name, and New Rollback Collection Name. Confirm the modifications, click the Batch Modify Collection Names button at the bottom left to complete the modifications. As illustrated below.
Note:
Batch renaming collections can only modify all tables under a single instance of a single rollback task. If a user initiates a batch rollback task involving collections from multiple instances, the collection names must be modified one by one.
Bulk Modify Collection Names includes changing the Original Collection Name and Rollback Collection Name.
For Original Collection, the mark _ori is added to its Original Collection Name.
For Rollback Collection, change the Rollback Collection Name to the Original Collection Name.



Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback