This topic describes the offset rules of storage plans in ApsaraDB for MyBase.
Offset rules
After you purchase a storage plan in a region, ApsaraDB for MyBase automatically calculates the amount of storage used by your pay-as-you-go instances that are deployed in the region. Then, the system uses the storage plan to offset your storage costs before the storage plan expires. If the amount of the storage that is used exceeds the capacity of your storage plan, you are billed for the additional storage based on the Bills method.
Storage type | Offset factor |
PL1 ESSD | 1 |
PL2 ESSD | 2 |
PL3 ESSD | 4 |
The following offset rules of storage plans apply in terms of offset factors:
Basic Edition instance: Offset factor × 1.
High-availability Edition instance: Offset factor × 2.
Examples
Assume that you purchase a storage plan of 10 TB in a region, you can use the storage plan to offset a pay-as-you-go bill for the following instances:
Basic Edition instance that uses a PL1 enhanced SSD (ESSD) of up to 10 TB, a PL2 ESSD of up to 5 TB, or a PL3 ESSD of up to 2.5 TB.
High-availability Edition instance that uses a PL1 ESSD of up to 5 TB, a PL2 ESSD of up to 2.5 TB, or a PL3 ESSD of up to 1.25 TB.
If you purchase a Basic Edition instance that uses multiple ESSDs, you can use the storage plan to offset the total costs of ESSDs in the following cases:
The total capacity of PL1 ESSDs is 10 TB.
The total capacity of PL3 ESSDs is 1 TB, the total capacity of PL2 ESSDs is 2 TB, and the total capacity of PL1 ESSDs is 2 TB.
You can view the hourly offset records of storage plans in the Billing Management console.