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

Backup Introduction

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2025-11-21 20:50:16

Introduction

To prevent data loss or damage caused by hardware or software exceptions, misoperations, or disasters, TencentDB for MongoDB provides the full backup feature, which ensures that the database can be restored to a specific historical time point in case of unexpected situations, maximizing the integrity and availability of business data.

Backup Type

Backup Type
Description
Feature
Backup methods classified based on the backup operation triggering mechanism
Automatic backup
A method that periodically and automatically performs backup operations based on a preset backup policy (such as initiating backup tasks at 2:00 to 3:00 AM every day)
Automatic backup execution based on a preset policy
Manual backup
A method that sets backup parameters and performs a full backup operation immediately based on business, Ops, troubleshooting, or other immediate requirements
Immediate backup task initiation
Backup methods classified based on the backup implementation mechanism

Physical backup
A method that directly copies the underlying physical files of the database (such as data files, index files, and log files)
Fast backup speed, direct file copying without parsing database content, and high backup and rollback efficiency
Logical backup
A method that backs up data based on the logical structure of the database, such as table structures and data records
Note:
TencentDB for MongoDB uses the mongodump tool to store the database operation logs to logical backup files for data backup. During data recovery, the operation records are rolled back through the operation logs to restore data.
Slow backup speed, good portability, able to restore logical backups to different database versions, more storage space required, and database performance affected in the backup process
Snapshot backup
A method that creates snapshots for Cloud Block Storage (CBS) instances at the storage layer to capture the disk data status at a specific time point
Fast backup speed, minimal impact on database performance, no downtime, and easy data recovery from snapshots
Backup methods classified based on the backup data integrity requirements
Full backup
A method that saves a complete copy of all data at a specific time point using logical, physical, and snapshot backups
Long backup time, large storage space occupation, and fast data recovery
Incremental backup
A method that modifies backup data using incremental data recorded using Oplogs
Short backup time, less storage space occupation (only the changed data), and slow data recovery

Version Description

Instance Type
Version
Backup Implementation Mechanism
General Edition
3.2 and 3.6
Logical backup
4.0 and later versions (4.0, 4.2, 4.4, 5.0, 6.0, and 7.0)
Logical backup and physical backup
Cloud Disk Edition
4.0,4.2,4.4,5.0
Snapshot backup and physical backup

Advanced Backup

The backup service of TencentDB for MongoDB General Edition (3.2 and later versions) will be officially commercialized starting from 00:00:00 on November 20, 2025 (UTC+8), and advanced backup features (such as customizing the backup retention period, incremental backup downloading, full backup set deletion, and backup alarm reporting) are launched. The storage capacity occupied by backup data that exceeds the free backup storage quota will be billed in pay-as-you-go mode. You can select whether to enable Advanced Backup in the console based on your data protection requirements. Once it is enabled, it will be billed based on the standard rate.
Supported Feature
Feature Description
Specific Operation
Backup Cycle
Sets the specific date for automatic backup tasks by week. For example, backup is performed on Monday and Thursday every week.
Backup Frequency
Sets the number of backup execution times (N) on a backup day, which can be set to 1 or 2. When Backup Frequency is set to 1, the backup operation is performed once every day. When Backup Frequency is set to 2, a second backup operation is executed approximately 24 hours after the first backup operation.
Backup Retention Period
Sets the retention period for backup files flexibly.
Automatic Backup: Backup files are retained for seven days by default. It can be configured flexibly, and the value range is 7 to 365.
Manual Backup: The retention period can be configured as required. The value range is 1 to 1095.
Long-Term Backup
Selects backup files on specific dates by week or month (such as backup data on the 1st and 15th days of each month) and retains them for a longer period.
Incremental Backup
Incremental backup can be enabled for automatic backup to back up data changed since the last full backup.
Excessive Backup Alarm
Sets the alarm threshold for storage utilization of the backup data set. By default, an alarm is triggered when the backup data volume reaches 100% of the storage capacity (for instances of the General Edition).
Pay-as-you-go
Full and incremental backups are billed in pay-as-you-go mode for the occupied storage space. The fees are settled on the hour (UTC+8), accurate to seconds.
Billing description for backup space

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백