If you enable the Database Backup (DBS) sandbox feature, DBS charges you for the usage of sandbox storage and the creation of temporary sandbox instances. This topic describes the billable items and pricing of the DBS sandbox feature.
Background information
DBS provides a complete sandbox solution for MySQL and Oracle databases based on copy data management (CDM). The DBS sandbox feature allows you to quickly create a temporary sandbox instance in the DBS console. This way, data can be restored from a backup set within a short period of time. Read and write operations performed on temporary sandbox instances do not affect source databases. You can perform various operations within temporary sandbox instances, such as data restoration, recovery drills, R&D and testing, queries and analysis, and disaster recovery. For more information, see DBS sandbox overview and Limits on the DBS sandbox feature.
Billable items
If you use the DBS sandbox feature, you are charged for the usage of sandbox storage and the creation of temporary sandbox instances. The following table describes the supported features and billable items of the DBS sandbox feature.
Data source type | Supported feature | Billable item |
MySQL |
| |
Oracle |
|
Sandbox storage fees
After you enable the DBS sandbox feature for a database instance, sandbox storage is allocated for the database instance. DBS automatically synchronizes the data of the database instance to the sandbox storage and generates sandbox snapshots for the data. DBS charges you for sandbox storage based on the size of data that is stored in the sandbox storage. Sandbox storage fees are calculated based on the following rules:
Data size of sandbox storage
The DBS sandbox feature has some limits. When log files are generated for a database instance, such as binary log files that are generated for a MySQL instance, the system creates a sandbox snapshot at a specific point in time based on the log files.
The first snapshot in the sandbox storage is a full snapshot. The size of the first snapshot is close to the size of data in the database instance. The minimum size of the first snapshot is 20 GB. Subsequent snapshots are incremental snapshots. The size of subsequent snapshots varies based on the data change rate between the points in time when two consecutive snapshots are created. In most cases, the data change rate of a binary log of a MySQL instance ranges from 3% to 10%.
You can use the following formula to calculate the required capacity of sandbox storage after the DBS sandbox feature is enabled: Capacity of sandbox storage = Data size of a database instance × (1 + Data change rate × Average number of logs generated per day × Retention period of sandbox data).
A reference value of the data change rate is 5%. For example, the data size of a database instance is 1 TB, the average number of logs generated per day is 50, and the retention period of sandbox data is seven days. In this case, the capacity of sandbox storage is estimated to be 18.5 TB.
Unit price of pay-as-you-go sandbox storage
USD 0.008 per GB-day
You are charged for the actual amount of data that you use on an hourly basis.
Subscription CDM sandbox storage plans
If you want to store a large amount of data, we recommend that you purchase CDM sandbox storage plans to offset sandbox storage fees. The following table describes the prices of storage plans of different specifications. For more information, see Use storage plans.
The prices are for reference only. The prices displayed on the buy page of DBS prevail.
If your storage plans are used up, you are charged for excess storage on a pay-as-you-go basis.
Specifications | Unit price (USD per day) |
100 GB | 23 |
500 GB | 111 |
1 TB | 221 |
2 TB | 442 |
5 TB | 1,044 |
10 TB | 2,089 |
20 TB | 4,178 |
50 TB | 9,830 |
100 TB | 19,661 |
200 TB | 39,322 |
300 TB | 58,982 |
500 TB | 92,160 |
Fees of temporary sandbox instances
After you create a temporary sandbox instance, DBS charges you based on the specifications and usage duration of the sandbox instance on an hourly basis. If you do not create temporary sandbox instances, you are not charged for sandbox instance resources. The following table describes the billing standards of temporary sandbox instances.
Instance specifications | Unit price for regions in the Chinese mainland (USD per day) | Unit price for regions outside the Chinese mainland (USD per day) |
1 CPU core and 1 GB of memory | 0.346 | 0.346 |
1 CPU core and 2 GB of memory | 0.864 | 0.864 |
2 CPU cores and 4 GB of memory | 2.203 | 4.104 |
2 CPU cores and 8 GB of memory | 2.678 | 4.709 |
4 CPU cores and 8 GB of memory | 5.160 | 9.559 |
4 CPU cores and 16 GB of memory | 6.739 | 11.923 |
8 CPU cores and 16 GB of memory | 10.264 | 19.157 |
8 CPU cores and 32 GB of memory | 13.522 | 23.846 |