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 |
Instance Type | Version | Backup Implementation Mechanism |
Local Disk | Versions 3.2 and 3.6 | Logical backup |
| 4.0 and later versions | Logical backup and physical backup |
Cloud disk | 4.0 and later versions | Snapshot backup and physical backup |
Advanced Backup | 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 tasks to be executed on the backup day (N). The value range is 1 or 2. | |
Incremental Backup | Incremental backup can be enabled for automatic backup to back up data changed since the last full backup. | |
Backup Retention Policy | Backup files support retention policies of different durations. Default policy: Auto-backup is enabled by default with a retention period of 7 days, and the value range is [7, 365]. Manual backup: The value range is [1, 1095]. Long-term backup retention: You can select backup files from specific dates on a weekly or monthly basis to retain them for a longer period, with a value range of [30, 1075] days. Standalone backup retention: When an instance is terminated, its backup files are retained independently without any retention period limit until they are manually deleted. | |
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. | |
フィードバック