This topic describes the billable items, pricing formulas, and refunding rules of ApsaraDB for OceanBase.
The charge for an ApsaraDB for OceanBase instance depends on the following characteristics of the instance: region, deployment solution, node specifications, usage duration, and the storage space and duration of data and log disks.
Deployment solutions
ApsaraDB for OceanBase supports three deployment solutions: multi-Internet data center (IDC) deployment, dual-IDC deployment, and single-IDC deployment. For more information, see Deployment solutions.
Multi-IDC deployment: three full-featured replicas
Dual-IDC deployment: two full-featured replicas and one log-only replica
Single-IDC deployment: two full-featured replicas and one log-only replica
Billable items
The following table describes the billable items of ApsaraDB for OceanBase and the billing rules.
Billable item | Description | Supported billing method | Pricing formula |
Compute node |
|
| Total price of compute nodes = Catalog unit price × Number of nodes/3 × Usage duration |
[Storage] Data disk (Storage size on the purchase page) |
| The billing method for storage space is the same as the billing method you selected for compute nodes when you purchased the cluster.
| Total price of the data disk = Catalog unit price × Number of full-featured replicas/3 × Usage duration |
[Storage] Log disk | Backup files will occupy storage space. The charge for backup space depends on the size of occupied space and the storage duration. |
| Total price of the log disk = Catalog unit price × Number of nodes × Usage duration |
[Storage] Data disk for tenant instances (postpaid) |
| The billing method for storage space is the same as the billing method you selected for compute nodes when you purchased the tenant instance.
| Total price of the data disk for a tenant instance = Catalog unit price × Number of full-featured replicas/3 × Usage duration |
Total price of a cluster instance = Total price of compute nodes + Total price of the data disk + Total price of the log disk
Total price of a tenant instance = Total price of compute nodes (prepaid) + Total price of the data disk for the tenant instance (postpaid)
Refunding rules
The following table describes the refunding rules of ApsaraDB for OceanBase.
Billing method | Refunding rule |
Subscription | When you purchase a cluster instance billed in Subscription mode, you must make an instant payment for the purchased duration. If you no longer needs this instance due to business adjustment, you can apply for a refund. Before you apply for a refund, familiarize yourself with the Rules for unsubscribing from resources. Then, log on to the Unsubscribe page and apply for a refund. The system will settle the refund based on the usage of your instance. The prepaid items of the tenant instance are refunded, and the postpaid items will no longer be billed after the instance is stopped. |
Pay-as-you-go | Bills are generated for pay-as-you-go cluster instances and tenant instances based on the usage in real time. Therefore, such instances do not involve refunding. If you no longer needs such an instance, you can release the instance after you confirm that the data has been backed up or migrated and that your business is not affected. A released instance does not incur charges. |
Refunding may be involved if the billing method is changed or instance specifications are downgraded.
Scenario | Refunding rule |
Change the billing method | After the billing method is changed from Subscription to Pay-as-you-go for an instance, any unused prepaid payment is refunded. Formula for calculating the refund amount: Refund amount = Paid amount - Consumed amount |
Downgrade a Subscription instance | After the specifications of a Subscription instance are downgraded, the price gap between the new and original specifications is refunded. Formula for calculating the refund amount: Refund amount = Paid amount - Consumed amount |
Cancel renewal | If a renewal order for a Subscription instance is canceled before it takes effect, the renewal amount is refunded. For more information, see the "Cancel the cloud resource renewal order that has not taken effect" topic in Rules for unsubscribing from resources. |