Overview
The backup space is used to store the backup files (automatic data backups, manual data backups, and log backups) of all TencentDB for MySQL instances in a region. TencentDB for MySQL supports transition-to-cold storage, so automatic data backups include non-archive data backups, standard storage backups, and archive storage backups, and log backups include non-archive log backups, standard storage log backups, and archive storage log backups.
For two-node and three-node instances of local disk edition, TencentDB for MySQL offers free-of-charge backup space per region, which equals to the sum of the storage space of all two-node and three-node instances (including the source and disaster recovery instances) in the region. For calculation examples, see Calculation Formula. Note:
Free backup space will be provided when you purchase a source or disaster recovery instance but not a read-only instance.
The free space is not applicable to transition-to-cold storage.
For both single-node (cloud disk edition) instances and Cluster Edition (cloud disk edition) instances,TencentDB for MySQL offers a free tier of backup space at the instance level, which equals to 200% of the storage space of each instance.
Note:
The backup space of instances of cloud disk edition can be viewed on the Backup and Restoration tab.
Free Tier Comparison
|
| 200% of the storage space | Regarding instance dimensions, such as a single-node cloud disk edition instance or a Cluster Edition instance with a storage space of 50 GB, the instance is granted a free backup space of 100 GB. |
| 100% of the storage space | Region level. For example, if Tencent Cloud account A has two two-node instances in Beijing region with a storage space of 50 GB and 80 GB respectively, the account enjoys a free tier of backup space of 130 GB in Beijing region. |
Backup Pricing of Single-Node Instances of Cloud Disk Edition
Backup space in excess of the free tier is priced at 0.00003676 USD/GB/hour in the Chinese mainland and 0.00004118 USD/GB/hour outside the Chinese mainland.
Single-node instances of cloud disk edition are currently supported in Shanghai, Beijing, Guangzhou, Chengdu, Hong Kong of China, Singapore, Frankfurt, with more regions to come in the future.
Cluster Edition (Cloud Disk Edition) Backup Pricing
For backup space exceeding the free quota, charges in Chinese Mainland regions are at a rate of $0.00003676 per GB per hour, while other regions are charged at $0.00004118 per GB per hour.The Cluster Edition (cloud disk edition) instances are currently available in the following regions: Shanghai, Beijing, Guangzhou, Chengdu, Hong Kong of China, Singapore, and Frankfurt, with other cities to be available gradually in the future.
Local Disk Backup Pricing
For backup storage exceeding the free quota, charges in Chinese Mainland regions are at a rate of $0.00000003 per GB per second, while other regions are charged at $0.00000004 per GB per second.If the charged space is less than 1 GB, no actual fees are incurred, and periods less than one hour are billed as one hour. TencentDB for MySQL offers a flexible gifting policy, meaning the vast majority of instances do not require payment for backup space.
Notes on Cross-Region Backup and Billing
TencentDB for MySQL supports cross-region backup for compliance or disaster recovery. You can enable this feature in the console as instructed in Cross-Region Backup. Once enabled, cross-region backup doesn't affect the local default backup, and they can both coexist with their own retention periods. Upon completion, the automatic backup is dumped to the storage device for cross-region backup. Note:
Cross-region backup and log files cannot use the free storage space; instead, they use the space in the backup region of the source instance.
Cross-region backup space is priced at 0.000113 USD/GB/hour in the Chinese mainland and 0.000127 USD/GB/hour outside the Chinese mainland.
The cross-region backup feature is currently available in Beijing, Shanghai, Guangzhou, Shenzhen, and Chengdu, with more regions to come in the future.
Transition-to-Cold Storage Billing
TencentDB for MySQL supports transition-to-cold storage for backup files to reduce the backup storage costs. You can configure to transition backup files to standard storage and then to archive storage in the console as instructed in Configuring Transition-to-Cold Storage. The prices of these two storage types are as follows: Note:
The free space is not applicable to transition-to-cold storage.
The archive storage type isn't available yet.
Standard storage pricing
Standard storage fees are charged in a pay-as-you-go (postpaid) manner at the storage price of the region as listed below:
|
Beijing, Nanjing, Shanghai, Guangzhou | |
| |
| |
| |
Tokyo, Frankfurt | |
| |
Hong Kong (China), Seoul, Bangkok, São Paulo, Jakarta | |
Shenzhen Finance, Shanghai Finance | |
Archive storage pricing
Archive storage fees are charged in a pay-as-you-go (postpaid) manner at the storage price of the region as listed below:
|
Beijing, Nanjing, Shanghai, Guangzhou | |
Chengdu, Chongqing, Silicon Valley, Virginia | |
Frankfurt | |
Hong Kong (China), Tokyo, Seoul, Bangkok, São Paulo, Singapore | |
| |
Billing Schedule for Backup Space
Billing officially started from 00:00 on December 2, 2019 for Hong Kong (China), Macao (China), Taiwan (China), and other regions outside the Chinese mainland.
Billing officially started from 00:00 on December 2, 2019 for Southwest China (Chengdu and Chongqing regions), South China (Shenzhen Finance), East China (Shanghai Finance), and North China (Beijing Finance).
Billing officially started from 00:00 on December 5, 2019 for South China (Guangzhou region).
Billing officially started from 00:00 on December 9, 2019 for North China (Beijing region).
Billing officially started at 00:00 on December 10, 2019 for East China (Shanghai region).
Billing is started by default for regions added after 00:00 on December 10, 2019.
Backup space calculation formula for instances of local disk edition:
Free backup space in one region = Sum of storage space of all TencentDB for MySQL two-node and three-node instances in that region
Paid backup space in one region = Data backup volume + log backup volume - free backup space (all values are for that region)
Backup space calculation formula for instances of cloud disk edition:
Free backup space of one instance = 200% of the storage space of that instance
Paid backup space of one instance = data backup volume + log backup volume - free backup space (all values are for that instance)
Note:
Backups of TencentDB for MySQL instances in the recycle bin will also be counted into the total backup space.
Calculation Example
If you have a running a TencentDB for MySQL two-node instance with a purchased database storage space of 500 GB/month in Guangzhou Zone 3 and another such instance with a purchased database storage space of 200 GB/month in Guangzhou Zone 4, you will get a free backup space of 700 GB/month in the Guangzhou region.
If your data backups reach 800 GB and log backups reach 100 GB in the current hour, your total backup space used in Guangzhou region will exceed 700 GB, and you will be billed for the excess of 200 GB (800 + 100 - 700 = 200) for the current hour and so on.
Backup Lifecycle
Monthly subscribed instance
Backups are subject to change over the instance lifecycle.
The backup feature can be used normally within seven days after an instance expires, during which backups beyond the free tier will still be billed.
From the eighth day after expiration, the instance is isolated and moved into the recycle bin. At this time, automatic backup stops, and rollback and manual backup are prohibited, but backups can still be downloaded in the Backup List page. Excessive backup space will still be billed until the instance is eliminated. You can renew the instance in the recycle bin in the console to recover it. After seven days since the instance has been isolated in the recycle bin, the instance is eliminated (i.e., deleted completely) along with all data backups. Save the needed backups in a timely manner.
Backups are subject to change over the instance lifecycle.
Backups can work normally within 24 hours after the instance payment becomes overdue.
After 24 hours since the instance payment has been overdue, the instance is isolated and moved into the recycle bin. At this time, automatic backup stops, and rollback and manual backup are prohibited, but backups can still be downloaded on the Backup List page. Excessive backup space will still be billed until the instance is eliminated. You can renew the instance in the recycle bin in the console to recover it. After three days since the instance has been isolated in the recycle bin, the instance is eliminated (i.e., deleted completely) along with all data backups. Save the needed backups in a timely manner.
Payment Overdue
Monthly subscribed instance
If the instance has not expired but your account has overdue payments, the backup service is downgraded, rollback, manual backup, and backup download are prohibited, but automatic backup continues, where excessive backup space is still billed.
If you need to perform rollback, manual backup, or backup download, top up your account to a positive balance.
Pay-as-you-go instance
After the account has overdue payments, the backup will change with the lifecycle of the instance. For more information, see the backup lifecycle of pay-as-you-go instances as described above.
Upgraded Services Available After Backup Billing Starts
Note:
The values listed in the table below are the maximum values supported in the same region under a single Tencent Cloud account.
|
Data backup retention period | | |
Log backup retention period | | |
| | |
| | |
Suggestions for Reducing Backup Costs
Delete manual backups that are no longer used. You can log in to the TencentDB for MySQL console, click an instance ID or Manage in the Operation column to access the instance management page, and delete manual backups on the Backup and Restore tab. Automatic backups cannot be manually deleted in the console. Instead, they are automatically deleted after they expire. Reduce the frequency of automatic data backup for non-core businesses. You can adjust the backup cycle and backup file retention period in the console, which should be at least twice a week.
Note:
The rollback feature relies on the backup cycle and retention days of data backups and log backups (binlog). Rollback will be affected if you reduce the automatic backup frequency and retention period. You can select the parameters as needed. For more information, see Rolling back Databases. Shorten the retention period of data and log backups for non-core businesses. A retention period of seven days can meet the needs in most cases.
|
| It is recommended to set the retention period to 7 to 3650 days, and to enable regular backups for the long-term preservation of data. |
Non-core, non-data businesses | 7 days |
| 7 days. We recommend that you manually back up data based on your actual business needs and delete the backups promptly after use |
| 7 days. We recommend that you manually back up data based on your actual business needs and delete the backups promptly after use |
Was this page helpful?