Backup Space Billing
Last updated: 2025-11-25 11:00:18
Overview
Backup space is a logical storage container in the TencentDB for MongoDB service, used for persistently storing backup data of all instances in a specific region. The stored content includes but is not limited to:
Full backup data: A complete copy of all data at a specific time point using logical, physical, and snapshot backups.
Incremental backup data: Backup of incremental data modifications recorded in the form of Oplog.
Billing Mode
Billing Information | Description | |
Billing mode | Pay-as-you-go (postpaid): Fees are settled on the hour (UTC+8) with billing granularity accurate to seconds. | |
Billable resource | Storage space for backup data: full backup and incremental backup data. | |
Billable instance | General Edition instances: version 3.2 and later. Cloud Disk Edition instances are currently not billed. | |
Billing Formula
Backup fees settled on the hour = Billable backup volume x Unit price for backup x Retention time of the backup set
Parameter in Billing Formula | Description |
Billable backup volume (GB) | Billable backup volume = MAX (Volume of full backup data + Volume of incremental backup data – Free tier, 0) Note: Free tier: General Edition instances are entitled to free backup space equivalent to 100% of the total storage space. For example, a General Edition instance with 100 GB storage has a free tier of 100 GB for data backup. The backup volume of read-only instances and disaster recovery instances is calculated separately and does not consume the free tier of the primary instance. |
Unit price for backup (USD/GB/hour) | |
Retention time of the backup set (hours) | The storage duration of backup data is calculated in seconds if it is less than one hour. |
Billing Unit Price
For General Edition instances, backup fees are calculated based on the storage price of the region. The following table shows the price for different regions.
Region | Price (USD/GB/Hour) |
Chinese mainland regions (excluding Finance and Autonomous Driving regions) | 0.000113 |
Shanghai Autonomous Driving Cloud | 0.0001695 |
Shanghai Finance, Beijing Finance, and Shenzhen Finance | 0.0002034 |
Other regions | 0.000127 |
Backup Lifecycle
The billing status of backups is closely related to the lifecycle of the instance, as detailed below:
Note:
After an instance is isolated to the recycle bin due to overdue payments or expiration, although backup billing is suspended, backup features will be subject to strict restrictions, and only the ability to download the latest full backup will be retained.
After an instance remains in the recycle bin for a specified number of days, it will be permanently deleted, and all backups will be destroyed accordingly. If you have important backups that need long-term retention, be sure to save them using the download feature before the instance is eliminated.
Instance Type | Instance Status | Backup Feature | Billed | Key Operation and Subsequent Status |
Pay-as-you-go instance | Running/Overdue (within 24 hours) | Automatic backup, manual backup, and rollback features are functioning normally. | Yes | Backup and billing proceed as usual. |
| Within 7 days after shutdown (isolation period in the recycle bin) | Stop automatic backup. Prohibit rollback and manual backup. Only the most recent full backup can be downloaded. | No | When an instance is isolated in the recycle bin, backups are not billed during this period. You can top up your account to restore the instance from the recycle bin. |
| 7 days after being isolated in the recycle bin | None | None | The instance is officially eliminated, and all data backups are destroyed. |
Backup Cost Suggestions
To help you manage backup storage space more cost-effectively while ensuring data security, we provide the following recommendations.
Proactively clean up invalid backups (most direct and effective): Regularly delete unused full backup sets.
Note:
Each full backup set occupies significant storage space. Promptly clean up temporary backups created for testing and version updates, or obsolete backups. To perform this operation, log in to the TencentDB for MongoDB console, and navigate to the Full Backup Task List tab on the Backup and Rollback page.
Configure backup policies based on business criticality levels.
Note:
The rollback feature relies on full backups and incremental backups within the backup cycle and retention time. Reducing automatic backup frequency and retention days may affect rollback efficiency and the available rollback time range for the instance data. Configure backup settings based on your business requirements.
Business Type | Recommended Backup Retention Time | Backup Frequency and Method Recommendation | Description |
Core business | 7 to 365 days | Maintain a high frequency (for example, daily) for automatic backups. It is strongly recommended to enable the Long-Term Backup Retention feature to archive backup sets from critical points in time for 7 to 1,095 days. | While ensuring high data recoverability, the long-term retention feature meets compliance requirements and core data archiving needs. |
Non-core and non-data business | Recommended: 7 days | Reduce the frequency of automatic backups (for example, twice per week, meeting the minimum requirements). | A retention time of 7 days can meet most fault recovery scenarios, significantly reducing the storage space occupied by regular backups. |
Testing business | Recommended: 7 days | Perform manual backups based on your actual needs, and promptly delete temporary backups after testing is completed. | Prevent temporary data in test environments from persistently occupying backup storage space, achieving "use on demand and release after use". |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback