Dear Tencent Cloud user,
The commercial edition of the TDSQL-C for MySQL backup feature has been released. The backup feature will be officially commercialized starting from 00:00:00 on July 1, 2026, Beijing Time, with charges applied to the portion of cluster backup storage that exceeds the free quota.
1. Commercial Billing Time
Commercial billing for TDSQL-C for MySQL backup storage will officially commence starting from 00:00:00 on July 1, 2026, Beijing Time.
2. Backup Commercial Billing Description
2.1 Billable Backup Scope
After commercialization, the following four types of backup usage will be included in the billing scope:
|
Local Region Data Backup | Data backup in the cluster's region, which includes logical backups and snapshot backups. |
Local Region Log Backup | Log backup in the cluster's region, which includes binlog and redo log backups. |
Cross-Region Data Backup | Data Backup Replicated to Other Regions |
Cross-Region Log Backup | Log Backup Replicated to Other Regions |
Note:After the commercial billing takes effect, the billing system will calculate the backup files that are still within the backup retention period and actually occupy backup space. Among them, backup files created before the commercial billing took effect but still retained and occupying backup space after it takes effect will also be included in the billable usage from the effective time of commercial billing according to this rule.
2.2 Free Quota
The method for granting the free quota varies depending on the storage billing mode you have purchased, as follows:
|
Local Region Data Backup | 50% of the prepaid storage capacity purchased for this cluster | 50% of the postpaid storage usage for this cluster |
Local Region Log Backup | 100 GB per cluster | 100 GB per cluster |
Cross-Region Data Backup | No free quota is provided. | No free quota is provided. |
Cross-Region Log Backup | No free quota is provided. | No free quota is provided. |
2.3 Billing Usage Calculation Logic
The total is calculated by summing the results computed for each cluster according to the following formula, grouped by account (UIN) + region.
Local-Region Data Backup Billable Usage: Calculate "(local data backup usage - 50% free quota of the cluster's storage)" for each cluster individually, then sum the results. If the result is less than 0, it is counted as 0. The free quotas for prepaid and postpaid clusters are calculated independently and cannot be offset across clusters or across billing modes.
Local-Region Log Backup Billable Usage: Calculate "(local log backup usage - 100 GB free quota)" for each cluster individually, then sum the results. If the result is less than 0, it is counted as 0.
Cross-Region Data Backup Billable Usage: Cross-region data backups are not eligible for any free quota. All usage is billed at the price of the target region where the backup files are stored.
Cross-Region Log Backup Billable Usage: Cross-region log backups are not eligible for any free quota. All usage is billed at the price of the target region where the backup files are stored.
2.4 Billing Price
Backup usage exceeding the free quota is billed on a pay-as-you-go basis and settled hourly according to the following prices:
|
Chinese mainland regions (excluding Hong Kong (China)) | 0.00003186 |
Hong Kong (China) and other overseas regions | 0.00003676 |
3. Commercial Impact Statement
To ensure a smooth transition for your business, we recommend that you complete the following tasks before the commercialization takes effect:
Backup Policy Adjustment: You can go to console to adjust the retention period for automatic backups and the cross-region backup policy, thereby controlling backup usage. Backup Usage Query: You can go to console to view the details of backup usage and billable usage for each cluster in real time. Historical Backup Cleanup: It is recommended to clean up invalid manual backups before commercialization to avoid unexpected charges. Deleting backups may affect the ability to restore data in the future. Please confirm that the relevant backups are no longer needed before performing the deletion. For details, refer to Deleting Backup.