- Release Notes and Announcements
- Release Notes
- Open-Source Plugin Privilege Escalation Has Vulnerability Risk for PostgreSQL
- Announcements
- Security Risk Statement for Creating Partial Plugins in PostgreSQL Cloud Database
- TencentDB for PostgreSQL Will Start Billing for Backup Space
- Some Extensions on Lower Kernel Version Can't Be Created and Upgraded in TencentDB for PostgreSQL
- Announcement on the Risk of Privilege Escalation Vulnerability in Cloud Database PostgreSQL Open Source Plugin
- Product Introduction
- Purchase Guide
- Getting Started
- Kernel Version Introduction
- Operation Guide
- Instance Management
- Instance Lifecycle
- Setting Instance Maintenance Time
- Modifying Instance Configuration
- Setting instance availability zone for disaster recovery or region disaster recovery
- Modifying AZs
- Terminating Instances
- Restoring Instances
- Eliminating Instances
- Restarting Instances
- Modifying Data Replication Mode
- Switch Source-Replica Instance
- Upgrading Instance
- Read-Only Instance
- Account Management
- Database Management
- Database Optimization
- Parameter Management
- Log management
- Backup and Restoration
- Backup Principles and Solutions
- Backing up Data
- Downloading Backup
- Cloning Instance
- Automatic Backup Settings
- Restoring PostgreSQL Data on CVMs
- Deleting Backup
- Viewing Backup Space
- Setting Backup Download Rules
- Use Serverless Cloud Function to Transfer Historical Backups of PostgreSQL
- Rollback to the Original Instance
- Physical Migration
- Database Audit
- Extension Management
- Network Management
- Access Management
- Data Encryption
- Tenant and Resource Isolation
- Security Groups
- Monitoring and Alarms
- Tag
- Instance Management
- PostgreSQL for Serverless
- MSSQL Compatible Version
- Practical Tutorial
- postgres_fdw Extension for Cross-database Access
- Automatically Creating Partition in PostgreSQL
- Searching in High Numbers of Tags Based on pg_roaringbitmap
- Querying People Nearby with One SQL Statement
- Configuring TencentDB for PostgreSQL as GitLab's External Data Source
- Supporting Tiered Storage Based on cos_fdw Extension
- Implement Read/Write Separation via pgpool
- Analyzing Slow SQL Using the auto_explain Plugin
- Using pglogical for Logical Replication
- Performance White Paper
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- CreateInstances
- DescribeDBInstances
- DescribeDBInstanceAttribute
- DescribeEncryptionKeys
- DescribeDBInstanceHAConfig
- SwitchDBInstancePrimary
- ModifyDBInstanceName
- ModifyDBInstanceSpec
- ModifyDBInstanceDeployment
- UpgradeDBInstanceKernelVersion
- ModifyDBInstanceHAConfig
- ModifyDBInstanceChargeType
- ModifyDBInstancesProject
- ModifySwitchTimePeriod
- RenewInstance
- SetAutoRenewFlag
- RestartDBInstance
- IsolateDBInstances
- DisIsolateDBInstances
- DestroyDBInstance
- CreateDBInstances
- InitDBInstances
- UpgradeDBInstance
- UpgradeDBInstanceMajorVersion
- Read-only Replica APIs
- Backup and Recovery APIs
- DescribeAvailableRecoveryTime
- DescribeCloneDBInstanceSpec
- CloneDBInstance
- RestoreDBInstanceObjects
- DescribeBackupOverview
- DescribeBackupSummaries
- DescribeBackupPlans
- ModifyBackupPlan
- CreateBaseBackup
- DescribeBaseBackups
- ModifyBaseBackupExpireTime
- DeleteBaseBackup
- DescribeLogBackups
- DeleteLogBackup
- DescribeBackupDownloadURL
- DescribeBackupDownloadRestriction
- ModifyBackupDownloadRestriction
- DescribeDBXlogs
- DescribeDBBackups
- Parameter Management APIs
- Security Group APIs
- Performance Optimization APIs
- Account APIs
- Specification APIs
- PostgreSQL for Serverless APIs
- Network APIs
- Data Types
- Error Codes
- FAQs
- Service Agreement
- Glossary
- Contact Us
- Release Notes and Announcements
- Release Notes
- Open-Source Plugin Privilege Escalation Has Vulnerability Risk for PostgreSQL
- Announcements
- Security Risk Statement for Creating Partial Plugins in PostgreSQL Cloud Database
- TencentDB for PostgreSQL Will Start Billing for Backup Space
- Some Extensions on Lower Kernel Version Can't Be Created and Upgraded in TencentDB for PostgreSQL
- Announcement on the Risk of Privilege Escalation Vulnerability in Cloud Database PostgreSQL Open Source Plugin
- Product Introduction
- Purchase Guide
- Getting Started
- Kernel Version Introduction
- Operation Guide
- Instance Management
- Instance Lifecycle
- Setting Instance Maintenance Time
- Modifying Instance Configuration
- Setting instance availability zone for disaster recovery or region disaster recovery
- Modifying AZs
- Terminating Instances
- Restoring Instances
- Eliminating Instances
- Restarting Instances
- Modifying Data Replication Mode
- Switch Source-Replica Instance
- Upgrading Instance
- Read-Only Instance
- Account Management
- Database Management
- Database Optimization
- Parameter Management
- Log management
- Backup and Restoration
- Backup Principles and Solutions
- Backing up Data
- Downloading Backup
- Cloning Instance
- Automatic Backup Settings
- Restoring PostgreSQL Data on CVMs
- Deleting Backup
- Viewing Backup Space
- Setting Backup Download Rules
- Use Serverless Cloud Function to Transfer Historical Backups of PostgreSQL
- Rollback to the Original Instance
- Physical Migration
- Database Audit
- Extension Management
- Network Management
- Access Management
- Data Encryption
- Tenant and Resource Isolation
- Security Groups
- Monitoring and Alarms
- Tag
- Instance Management
- PostgreSQL for Serverless
- MSSQL Compatible Version
- Practical Tutorial
- postgres_fdw Extension for Cross-database Access
- Automatically Creating Partition in PostgreSQL
- Searching in High Numbers of Tags Based on pg_roaringbitmap
- Querying People Nearby with One SQL Statement
- Configuring TencentDB for PostgreSQL as GitLab's External Data Source
- Supporting Tiered Storage Based on cos_fdw Extension
- Implement Read/Write Separation via pgpool
- Analyzing Slow SQL Using the auto_explain Plugin
- Using pglogical for Logical Replication
- Performance White Paper
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- CreateInstances
- DescribeDBInstances
- DescribeDBInstanceAttribute
- DescribeEncryptionKeys
- DescribeDBInstanceHAConfig
- SwitchDBInstancePrimary
- ModifyDBInstanceName
- ModifyDBInstanceSpec
- ModifyDBInstanceDeployment
- UpgradeDBInstanceKernelVersion
- ModifyDBInstanceHAConfig
- ModifyDBInstanceChargeType
- ModifyDBInstancesProject
- ModifySwitchTimePeriod
- RenewInstance
- SetAutoRenewFlag
- RestartDBInstance
- IsolateDBInstances
- DisIsolateDBInstances
- DestroyDBInstance
- CreateDBInstances
- InitDBInstances
- UpgradeDBInstance
- UpgradeDBInstanceMajorVersion
- Read-only Replica APIs
- Backup and Recovery APIs
- DescribeAvailableRecoveryTime
- DescribeCloneDBInstanceSpec
- CloneDBInstance
- RestoreDBInstanceObjects
- DescribeBackupOverview
- DescribeBackupSummaries
- DescribeBackupPlans
- ModifyBackupPlan
- CreateBaseBackup
- DescribeBaseBackups
- ModifyBaseBackupExpireTime
- DeleteBaseBackup
- DescribeLogBackups
- DeleteLogBackup
- DescribeBackupDownloadURL
- DescribeBackupDownloadRestriction
- ModifyBackupDownloadRestriction
- DescribeDBXlogs
- DescribeDBBackups
- Parameter Management APIs
- Security Group APIs
- Performance Optimization APIs
- Account APIs
- Specification APIs
- PostgreSQL for Serverless APIs
- Network APIs
- Data Types
- Error Codes
- FAQs
- Service Agreement
- Glossary
- Contact Us
Overview
The backup space is used to store the backup files (automatic data backups, manual data backups, and log backups) of all TencentDB for PostgreSQL instances in a region. TencentDB for PostgreSQL offers a free tier of backup capacity based on the region. During the beta test of the backup billing, the free tier is equivalent to 700% of the total storage capacity of all the primary instances in your region, but the multiple will change to 100% after the backup billing official starts. For calculation examples, see Calculation Formula.
Note:
Free backup space is only available when you purchase a primary instance.
The backup space can be viewed on the database backup page in the [TencentDB for MySQL console].
Comparison of the free tier between during beta test and official start of the backup billing
Billed Period | Free Tier |
During the beta test of backup billing | 700% of storage space |
After the backup billing officially starts | 100% of storage space |
Backup pricing
Backup space in excess of the free tier is priced at 0.000118 USD/GB/hour in the Chinese mainland and 0.000133 USD/GB/hour outside the Chinese mainland.
If the excessive backup space is less than 1 GB, no fees will be charged. If the time period is less than one hour, it will be calculated as one hour. TencentDB for PostgreSQL adopts a flexible giveaway policy, so you generally don't need to pay for the backup space for most instances.
Billing schedule for backup space
From 00:00 on July 1, 2023, the beta test of backup billing will officially carried out in all regions.
From 0:00 on August 1, 2023, the backup billing will be officially carried out in all regions.
Calculation formula
During the beta test of backup billing:
Free backup capacity in one region = Sum of storage capacity of all TencentDB for PostgreSQL primary instances in that region * 700%
Paid backup capacity in one region = Data backup volume + log backup volume - free backup capacity (all values are for that region)
After the backup billing officially starts:
Free backup capacity in one region = Sum of storage capacity of all TencentDB for PostgreSQL primary instances in that region * 100%
Paid backup capacity in one region = Data backup volume + log backup volume - free backup capacity (all values are for that region)
Billing examples
After the backup billing officially starts, the calculation method is as follows:
You have purchased three instances in Guangzhou region, named A, B, and C, and their configurations are as follows:
A (Running):
1-Primary-1-standby, 4-core 8 GB memory per node, 200 GB storage
Backup space occupied: 5000 GB
B (Running):
1-Primary-1-standby, 4-core 8 GB memory per node, 300GB storage
Backup space occupied: 200GB
C (Isolated):
1-Primary-1-standby, 4-core 8 GB memory per node, 200GB storage
Backup space occupied: 100GB
The calculation formulas for free backup space, occupied paid space, and occupied free space are as follows:
Free backup space = (backup space purchased by A + backup space purchased by B + backup space purchased by C) 100% = (200+300+200) 100% = 700 GB.
Occupied paid space = paid space occupied by A + paid space occupied by B + paid space occupied by C = (5000-200) + 0 + 0 = 4800 GB.
Occupied free space = free space occupied by A + free space occupied by B + free space occupied by C = 200 + 200 + 100 = 500 GB.
Note
The free space occupied by an instance is the minimum value of purchased and occupied storage for the instance.
The paid space occupied by an instance is the excess beyond the purchased storage space. If the occupied space does not exceed the purchased space, the paid space of the instance is 0.
During the beta test of the backup billing, the calculation method is as follows:
You have purchased three instances in Guangzhou region, named A, B, and C, and their configurations are as follows:
A (Running):
1-Primary-1-standby, 4-core 8 GB memory per node, 200 GB storage
Backup space occupied: 5000GB
B (Running):
1-Primary-1-standby, 4-core 8 GB memory per node, 300GB storage
Backup space occupied: 200GB
C (Isolated):
1-Primary-1-standby, 4-core 8 GB memory per node, 200 GB storage
Backup space occupied: 100GB
The calculation formulas for free backup space, occupied paid space, and occupied free space are as follows:
Free backup space = (backup space purchased by A + backup space purchased by B + backup space purchased by C) 100% = (200+300+200) 700% = 4900 GB.
Occupied paid space = paid space occupied by A + paid space occupied by B + paid space occupied by C = (5000-200 * 7) + 0 + 0 = 3600 GB.
Occupied free space = free space occupied by A + free space occupied by B + free space occupied by C = (200 * 7) + 200 + 100 = 500 GB.
Backup lifecycle
Backups are not subject to change over the instance lifecycle.
After an instance is moved into the recycle bin, the automatic backup continues. Rollback and manual backup are not allowed, but backups can be downloaded. The excess beyond the free tier is still billed.
After the instance is terminated, the backup data will not be deleted, and the system will continue to provide you with 7-day free quota. If you no longer need the backup data of this instance, you can delete it by yourself, and the data cannot be recovered after deletion.
Note
When a monthly subscribed instance or a pay-as-you-go instance is terminated, the system will provide you with an additional "final" full physical backup to avoid nonrecovery events due to misoperation. The "final" backup capacity is not included in the backup space statistics, hence no fees are charged. You can download it in the data backup list. The "final" physical backups are automatically deleted seven days after the instance is terminated.
Overdue payments
Monthly subscribed instance
If the instance has not expired but your account has overdue payments, the backup service is downgraded, manual backup and backup download are not allowed, but automatic backup continues, where excessive backup space is still billed. If you need to perform manual backup, top up your account to a positive balance.
Pay-as-you-go instance
If your account has overdue payments, the backup service is downgraded, manual backup and backup download are not allowed, but automatic backup continues, where excessive backup space is still billed. Backups are not subject to change over the instance lifecycle. For more information, see Backup Lifecycle.
Suggestions for reducing backup costs
Delete unnecessary manual backup
Reduce the backup frequency for non-core businesses. You can adjust the backup cycle in the console, and the frequency should be at least twice a week.
Yes
No
Was this page helpful?