Starting from August 17, 2023, PolarDB storage plans can offset the storage usage of level-2 backups, log backups, cold data, and PL0 enhanced SSDs (ESSDs), and adjustments to specific offset factors take effect.
Storage plans that are involved
Item
Storage plans can be used to offset the storage usage of the following items in PolarDB Enterprise Edition clusters:
Level-2 backups: The offset ratio is 0.043 for regions in the Chinese mainland and 0.054 for regions outside the Chinese mainland.
Log backups: The offset ratio is 0.043 for regions in the Chinese mainland and 0.054 for regions outside the Chinese mainland.
Cold data: The offset ratio is 0.045.
For more information about the rules, see the Offset items of storage plans section of this topic.
Involved regions
All regions
Start time
August 17, 2023
Offset items of storage plans
A PolarDB storage plan can be used to offset a cluster's storage usage billed on a pay-as-you-go basis, and the storage usage of level-1 backups beyond the free quota, level-2 backups, log backups, and cold data for a PolarDB cluster.
Offset the pay-as-you-go data storage usage of a PolarDB Enterprise Edition cluster
Storage type | Offset factor | Storage usage offset by a 1 GB of storage plan (Regions in the Chinese mainland) | Storage usage offset by a 1 GB of storage plan (Regions outside the Chinese mainland) |
PSL4 (with hot standby storage cluster enabled) | 0.65 | 1.54 GB | 1.54 GB |
PSL4 (with hot standby storage cluster disabled) | 0.325 | 3.08 GB | 3.08 GB |
PSL5 (with hot standby storage cluster enabled) | 1 | 1 GB | 1 GB |
PSL5 (with hot standby storage cluster disabled) | 0.5 | 2 GB | 2 GB |
For example, for a PSL4 cluster in a region inside the Chinese mainland with hot standby storage cluster enabled, a 50 GB of storage plan can be used to offset a storage usage of 76.92 GB (1/0.65 × 50). Excess storage usage over 76.92 GB is billed on a pay-as-you-go basis.
Offset the storage usage of level-1 backups that exceed the free quota of a PolarDB Enterprise Edition cluster
Region type | Offset factor | Level-1 backup storage usage offset by a 1 GB of storage plan |
Regions in the Chinese mainland (PSL4) | 0.41 | 1/0.41=2.44 GB |
Regions in the Chinese mainland (PSL5) | 0.617 | 1/0.617=1.62 GB |
Regions outside the Chinese mainland (PSL4) | 0.41 | 1/0.41=2.44 GB |
Regions outside the Chinese mainland (PSL5) | 0.617 | 1/0.617=1.62 GB |
For example, you purchase a storage plan with a capacity of 100 GB and 50 GB is left after you offset the storage usage (PSL5). Your cluster uses 50 GB of storage for level-1 backups (outside the free quota) in a region outside the Chinese mainland. In this case, the storage plan automatically uses 31.25 GB (50/1.6=31.25) to offset the backup storage usage. As a result, the storage plan has 18.75 GB of capacity left.
If the remaining capacity of the storage plan is insufficient to offset the storage usage of level-1 backups, you are charged for the excess storage usage on a pay-as-you-go basis.
Offset the storage usage of level-2 backups of a PolarDB Enterprise Edition cluster (New)
Region type | Offset factor | Level-2 backup storage usage offset by a 1 GB of storage plan |
Chinese mainland regions | 0.043 | 1/0.043=23.26 GB |
Regions outside the Chinese mainland | 0.054 | 1/0.054=18.52 GB |
For example, you purchase a storage plan with a capacity of 100 GB, and 50 GB is left after it offsets the data storage usage. Your cluster uses 50 GB of storage for level-2 backups in a region inside the Chinese mainland. In this case, the storage plan automatically uses 2.15 GB (50/23.26) to offset the backup storage usage and the storage plan has 47.85 GB of capacity left.
If the remaining capacity of the storage plan is insufficient to offset the storage usage of level-2 backups, you are charged for the excess storage usage on a pay-as-you-go basis.
Offset the storage usage of log backups of a PolarDB Enterprise Edition cluster (New)
Region type | Offset factor | Log backup storage usage offset by a 1 GB of storage plan |
Chinese mainland regions | 0.043 | 1/0.043=23.26 GB |
Regions outside the Chinese mainland | 0.054 | 1/0.054=18.52 GB |
For example, you purchase a storage plan with a capacity of 100 GB, and 50 GB is left after it offsets the data storage usage. Your cluster uses 50 GB of storage for log backups in a region inside the Chinese mainland. In this case, the storage plan automatically uses 2.15 GB (50/23.26) to offset the backup storage usage and the storage plan has 47.85 GB of capacity left.
If the remaining capacity of the storage plan is insufficient to offset the storage usage of log backups, you are charged for the excess storage usage on a pay-as-you-go basis.
Offset the Object Storage Service (OSS) storage usage of cold data of a PolarDB Enterprise Edition cluster (New)
Region type | Offset factor | OSS storage usage offset by a 1 GB of storage plan |
Chinese mainland regions | 0.045 | 1/0.045=22.22 GB |
Regions outside the Chinese mainland | 0.045 | 1/0.045=22.22 GB |
For example, you purchase a storage plan with a capacity of 100 GB, and 50 GB is left after it offsets the data storage usage. The cold data of your cluster occupies 50 GB of OSS storage space in a region inside the Chinese mainland. In this case, the storage plan automatically uses 2.25 GB (50/22.22) to offset the backup usage of the cold data and the storage plan has 47.75 GB of capacity left.
If the remaining capacity of the storage plan is insufficient to offset the storage usage of cold data, you are charged for additional storage usage on a pay-as-you-go basis.
Offset order
Storage spaces are offset based on the following order:
PolarDB Enterprise Edition clusters > PolarDB Standard Edition clusters
PolarDB Enterprise Edition: Cluster storage usage (PSL5 and PSL4) > Storage usage of level-1 backups beyond the free quota > Storage usage of cold data archived to OSS > Storage usage of level-2 backups > Storage usage of log backups beyond the free quota (If multiple clusters are of the same priority, cluster's creation time determines which cluster's storage usage is offset first. That is, the older cluster takes precedence.)