You can pay for storage on a pay-as-you-go basis or use a subscription-based storage plan. By default, the pay-as-you-go billing method is used for Data Disaster Recovery built-in storage pools and ApsaraDB storage pools. To reduce storage costs, you can purchase storage plans.
Pay-as-you-go storage fees
When you perform backups in the Data Disaster Recovery console, RDS console, PolarDB console, or MongoDB console, the resulting backup files are stored in the destination region and incur storage fees. The backup storage pricing for the scenarios described in the following tabs is for reference only. The prices on your bill are final.
If you have a large data volume, we recommend that you purchase storage plans (subscription) to offset backup storage fees. These plans are more cost-effective than the pay-as-you-go billing method.
The unit prices in this topic are for reference only. The actual prices may vary. The prices on the buy page and in your bill are final.
Backup plans
Data Disaster Recovery provides two types of storage pools: Data Disaster Recovery built-in storage pools and self-managed Object Storage Service (OSS) storage pools. If you select built-in storage as the backup storage type when you configure a backup schedule, a storage fee is incurred. The built-in storage pool does not require a purchase. Its capacity automatically scales as your data grows. Storage fees are calculated based on the actual size of your stored data and the retention period. The following table details the pricing.
Calculation formula: Daily storage fee = Storage volume (GB) × Daily unit price
The bill for the previous day is generated and the fee is deducted at 00:00 each day. Bills are generated daily.
Storage region | Storage fee (USD/GB/month) |
China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Shenzhen), and Zhengzhou (CUCC Joint Venture) | 0.0173 |
US (Virginia) | 0.0185 |
Malaysia (Kuala Lumpur) and Thailand (Bangkok) | 0.019 |
China (Hong Kong), Singapore, US (Silicon Valley), Indonesia (Jakarta), Germany (Frankfurt) | 0.02 |
SAU (Riyadh - Partner Region) | 0.02412 |
Japan (Tokyo) | 0.0209 |
Cross-region backup for an RDS MySQL instance that uses cloud disks
If you perform a cross-region backup for an ApsaraDB RDS for MySQL instance that uses cloud disks in the ApsaraDB RDS console, the resulting backup files are stored in the destination region. You are charged for backup storage in the destination region. The following table details the pricing.
Destination region | Storage fee (USD/GB/day) |
China (Beijing), China (Hohhot), China (Ulanqab), China (Hangzhou), China (Shanghai), China (Shenzhen), China (Heyuan), China (Chengdu), China (Qingdao), China (Guangzhou), and China (Zhangjiakou) | 0.0009375 |
China (Hong Kong), US (Silicon Valley), US (Virginia), Singapore, Japan (Tokyo), Germany (Frankfurt), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila), UK (London), South Korea (Seoul), and Thailand (Bangkok) | 0.001125 |
Cross-region backup for a PolarDB for MySQL instance
When you perform a cross-region backup for a PolarDB for MySQL cluster in the PolarDB console, you are charged for cross-region backup storage. The following table details the pricing.
Chinese mainland | China (Hong Kong) and other regions outside China | Storage cost calculation method (billed daily) |
0.00021 CNY/GB/hour 0.0000325 USD/GB/hour | 0.000294 CNY/GB/hour 0.0000455 USD/GB/hour |
|
Cross-region backup storage is billed on a daily basis. The hourly unit price used in this section is converted from the daily unit price. For more information, see Billing rules for backup storage.
The charges for cross-region backups are displayed on your Database Backup (DBS) bill.
Backup sets of a deleted RDS MySQL instance
After you delete an ApsaraDB RDS for MySQL instance that uses local SSDs in the RDS console, the backup sets of the deleted instance are retained free of charge for seven days. After this period, you are charged for backup storage. For more information, see Configure a backup retention policy for released instances or Method 2: Configure a backup retention policy for released instances.
In your bills, the resource ID of this billing item is in the dbs:<instance ID>;RDS format, for example, dbs:rm-xxxxxx;RDS. This resource ID cannot be located directly on the Resource Management page. The fee corresponds to the backup sets of a released ApsaraDB RDS for MySQL instance and does not represent a standalone Database Backup (DBS) resource. To manage the backup sets and stop incurring charges, go to the Backups page in the RDS console. Click the Deleted Instance Backups tab, and then set the retention policy to Do Not Retain.
Billing method: Backup sets of deleted instances are stored free of charge for seven days. After this period, you are charged a storage fee based on the storage size and storage duration. The following table details the pricing.
Billing Site | Storage Region | Unit Price (USD/GB/Day) |
Public Cloud | China (Hangzhou), China (Beijing), China (Shanghai), China (Shenzhen), China (Qingdao), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Heyuan), China (Ulanqab), China (Guangzhou) | 0.00058 |
China (Hong Kong), Singapore, US (Silicon Valley), Germany (Frankfurt), Indonesia (Jakarta), Philippines (Manila), Thailand (Bangkok) | 0.00067 | |
Japan (Tokyo), South Korea (Seoul) | 0.0007 | |
US (Virginia) | 0.00062 | |
Malaysia (Kuala Lumpur) | 0.00064 | |
UK (London) | 0.00065 | |
UAE (Dubai) | 0.00072 |
MongoDB backup
When you perform an automatic backup or a manual backup in the MongoDB console, the resulting backup files are stored in the same region as the instance and incur storage fees.
You can purchase a Cloud Database Backup storage plan to offset the backup storage fees for automatic backups or manual backups in the MongoDB console.
Billing method: If your backup storage usage (including full backup and log backup) is within the free quota, you do not incur backup storage costs. Backup storage that exceeds the free quota is charged on an hourly basis. The hourly backup storage cost is calculated using the following formula: Hourly backup storage cost = (Backup storage capacity - Free quota) × Unit price per hour. Bills are generated daily. The following table details the pricing.
|
Storage type |
Free quota |
Usage and quota |
|
Cloud disk-based |
200% of the storage capacity |
View backup storage usage and free quota in the Specification Information section on the Basic Information page. |
|
Local disk-based |
50% of the storage capacity |
Unit prices for excess backup storage:
|
Storage type |
Unit price (USD/GB/day) |
|
Cloud disk-based |
Varies by region:
|
|
Local disk-based |
Varies by region:
|
Use storage plans (subscription)
If you have a large data volume, you can purchase storage plans to offset the storage fees for your instances. This section describes the pricing for backup instance storage plans and CDM sandbox storage plans. For more information about storage plans, see Use storage plans.
The prices provided are for reference only. For the actual prices, see the buy page.
Backup instance storage plan prices
Storage plan size | USD/month |
100 GB | 1.56 |
500 GB | 7.80 |
1 TB | 15.97 |
2 TB | 31.95 |
5 TB | 79.87 |
10 TB | 159.74 |
20 TB | 319.49 |
50 TB | 798.72 |
100 TB | 1,597.44 |
200 TB | 3,194.88 |
300 TB | 4,792.32 |
500 TB | 7,987.20 |
CDM sandbox storage plan prices
For more information, see Sandbox billing.
Offsettable items
Data Disaster Recovery offers the following two types of storage plans. These plans are available in various storage sizes, such as 100 GB, 500 GB, 1 TB, and 500 TB, and for various subscription periods, such as 1 month, 6 months, and 1 year. If your storage usage exceeds your storage plan quota, the excess storage is charged on a pay-as-you-go basis.
Storage plan type | Offsettable items |
CDM sandbox storage plan | These storage plans can be used to offset the fees incurred for your account when you use sandbox storage. For pricing details, see Sandbox billing. |
Backup instance storage plan | Offsets the built-in storage fees for backup schedule instances within the same Alibaba Cloud account. For more information, see Built-in storage and OSS. |
Offset rules
Rule item | Rule description |
Offset method |
|
Offset order | The offset is applied based on the billing time of the instance bills. Bills that are generated earlier are offset first. |
Storage plan offset example
Assume that a user purchases a 100 GB backup instance storage plan and has a backup plan in the China (Hong Kong) region that uses 120 GB of built-in storage. The storage plan offsets the fees as follows:
The amount of built-in storage that the plan can offset is 100 GB / 1.13 = 88.4956 GB. (This is an approximate value. The actual value is subject to your bill.) This is not enough to offset the total 120 GB of built-in storage. The storage plan first offsets 88.4956 GB of usage.
The remaining 31.5044 GB of built-in storage (120 GB - 88.4956 GB) is billed on a pay-as-you-go basis.
The offset factor for the China (Hong Kong) region is 1.13. For more information, see the Offset factors of storage plans section of this topic.
Storage plan offset factors
The following tables list the offset factors for Backup instance storage plans in different regions.
Backup instance storage plan offset factors
Backup plan region | Offset factor |
China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Chengdu), and China (Shenzhen) | 1 |
US (Virginia) | 1.05 |
Malaysia (Kuala Lumpur) | 1.08 |
China (Hong Kong), Singapore, US (Silicon Valley), Indonesia (Jakarta), Germany (Frankfurt) | 1.13 |
Japan (Tokyo) | 1.18 |
CDM sandbox storage plan offset factors
Offset factor: 1