MongoDB Backup
Last updated: 2025-07-10 14:54:18
Overview
MongoDB Backup is a SCF-based feature provided by COS. It allows you to back up data in TencentDB for MongoDB to COS so that data can be stored persistently and protected from data loss or corruption. After you set a backup function rule for a bucket, SCF will scan your MongoDB backup files periodically and store them in the bucket.
Notes
MongoDB Backup functions only back up the backup files of TencentDB for MongoDB. Therefore, if MongoDB backup has not been enabled, the functions cannot be executed. For more information about TencentDB for MongoDB backups, see Data Backup.
If you have added a MongoDB backup rule to your bucket in the COS console, the backup function will appear in the SCF console. DO NOT delete this function. Otherwise, your rule may not take effect.
MongoDB Backup is supported in SCF-enabled regions, including Guangzhou, Shanghai, Nanjing, Beijing, Chengdu, Hong Kong (China), Singapore, Bangkok, Seoul, Tokyo, Silicon Valley and Virginia. For more supported regions, see SCF Documentation.
The size of a single MongoDB backup file cannot exceed 300GB.
Directions
1. Log in to the COS console.
2. On the left sidebar, click Application Integration > Data Backup and find MongoDB Backup.
3. Click Configure Backup Rule to go to the rule configuration page.
4. Click Add Function.
Note:
If you haven't activated SCF, go to the SCF console to activate it and authorize the service as instructed.
5. In the pop-up window, configure the following items:
Function Name: Uniquely identifies a function and cannot be modified after being set. You can view the function in the SCF console.
Associated Bucket: A bucket to store the MongoDB backup files.
Trigger Period: Triggers the backup operation for the MongoDB Backup function. Every day and custom periods are supported.
Note:
For example, a user configures a MongoDB backup rule on July 3, 2023, specifying that the MongoDB instance files will be backed up to COS daily at 00:00.
The SCF will approximately start running on July 4, 2023, at 00:00:03 (there may be a few seconds delay in SCF startup), scanning MongoDB instance files from the past 3 days and uploading them to COS.
As the SCF execution time is 2023-07-04 00:00:03, the final backup file time range is: 2023-07-01 00:00:00 ~ 2023-07-04 00:00:03.
Cron Expression: If you use a custom period, you can use Cron to specify the trigger period rule. Cron is currently running in UTC +8 China Standard Time (CST), which is Beijing Time. For detailed configuration policies, see Timer Trigger Description.
Database Instance: MongoDB instance in the region where the current bucket resides
Delivery Path: Delivery path prefix of the backups. If not specified, backups will be stored in the root directory of the bucket.
SCF Authorization: SCF needs to be authorized so that it can read the MongoDB instances as well as their backup files, and store the backup files to the specified bucket.
6. Click Confirm.
You can perform the following operations on the created function:
Click Log to view the historical running status of MongoDB backup. If an error is reported, you can click Log to quickly redirect to the SCF console for viewing the error log details.
Click Details to view detailed information about the function and trigger.
Click More > Edit to modify the MongoDB data backup rule.
Click More > Trigger to immediately trigger the SCF without waiting for the specified period.
Click More > Delete to delete the unwanted MongoDB backup rule.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback