All Products
Search
Document Center

Database Backup:Storage fees

Last Updated:Mar 13, 2024

You can pay storage fees on a pay-as-you-go basis or purchase subscription storage plans. By default, Database Backup (DBS) built-in storage pools and ApsaraDB storage pools are charged on a pay-as-you-go basis. If you want to reduce storage fees, you can use subscription storage plans.

Pay-as-you-go storage fees

If you perform backup operations in the DBS console, ApsaraDB RDS console, PolarDB console, or ApsaraDB for MongoDB console, the generated backup files are stored in the region in which the destination instance resides. You are charged storage fees. The following tables describe the billing details of backup storage in different scenarios for your reference. The actual fees on your bills prevail.

Important
  • If a large amount of data needs to be stored during a backup, we recommend that you purchase subscription DBS storage plans to offset the storage fees. For more information, see Use storage plans. Storage plans are more cost-efficient than the pay-as-you-go billing method.

  • The unit prices in this topic are for reference only. The actual purchase price may be different. The actual fees on the buy page and your bills prevail.

DBS backup schedules

DBS provides two types of storage pools: DBS built-in storage pools and self-managed Object Storage Service (OSS) storage pools. If you set the backup storage type to DBS Storage when you configure a backup schedule in the DBS console, you are charged storage fees. You do not need to specify the storage capacity when you purchase a backup schedule. The storage capacity is automatically increased when the amount of data increases. You are charged based on the storage space that you use and the storage duration. The following table describes the billing details.

Formula: Storage fees per hour = Storage volume in GB × Unit price per GB-hour

Region

Unit price (USD per 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), India (Mumbai), and Thailand (Bangkok)

0.019

China (Hong Kong), Singapore, US (Silicon Valley), Indonesia (Jakarta), and Germany (Frankfurt)

0.02

SAU (Riyadh)

0.02412

Japan (Tokyo) and Australia (Sydney)

0.0209

Note

The bill of the previous day is generated and fees are deducted at 00:00:00 every day.

Cross-region backup for an ApsaraDB RDS for 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 generated backup files are stored in the region in which the destination instance resides. You are charged for backup storage in the destination region. The following table describes the billing details.

Destination region

Unit price (USD per 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), Australia (Sydney), Malaysia (Kuala Lumpur), Indonesia (Jakarta), India (Mumbai), Philippines (Manila), UK (London), South Korea (Seoul), and Thailand (Bangkok)

0.001125

Note

Storage plans are used to offset the storage fees that are generated if you perform a cross-region backup for an ApsaraDB RDS for MySQL instance that uses cloud disks in the ApsaraDB RDS console.

Cross-region backup for a PolarDB for MySQL cluster

If you perform a cross-region backup for a PolarDB for MySQL cluster in the PolarDB console, the generated backup files are stored in the region in which the destination cluster resides. You are charged for backup storage in the destination region. The following table describes the billing details.

Region in the Chinese mainland

Region outside the Chinese mainland

Billing rule (daily)

USD 0.0000325 per GB-hour

USD 0.0000455 per GB-hour

  • Storage fees per hour = Total size of level-2 backup × Unit price per hour

  • For example, you back up the data of a PolarDB for MySQL cluster between regions in the Chinese mainland. If the total size of level-2 backup is 100 GB, the storage fees per hour are calculated by using the following formula: 100 GB × USD 0.0000325 per GB-hour = USD 0.00325 per hour.

Note
  • Cross-region backups are billed on a daily basis. In this topic, the daily price is converted to the hourly price. For more information, see Billing rules.

  • Fees for cross-region backups are recorded in DBS bills.

Backup sets of an ApsaraDB RDS for MySQL instance that is deleted

After you delete an ApsaraDB RDS for MySQL instance that uses local SSDs in the ApsaraDB RDS console, the backup sets of the deleted instance are retained free of charge for seven days. After seven days, you are charged for backup storage. For more information, see the Method 2: Configure the backup retention policy after the instance is released section of the "Retain backup files for a long period of time" topic.

Billing rules: You are charged based on the size and storage duration of backup sets. The following table describes the billing details.

Type

Region

Unit price (USD per GB-day)

Public cloud

China (Hangzhou), China (Beijing), China (Shanghai), China (Shenzhen), China (Qingdao), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Heyuan), China (Ulanqab), and China (Guangzhou)

0.00058

China (Hong Kong), Singapore, US (Silicon Valley), Germany (Frankfurt), Indonesia (Jakarta), Philippines (Manila), and Thailand (Bangkok)

0.00067

Japan (Tokyo), South Korea (Seoul), and Australia (Sydney)

0.0007

US (Virginia)

0.00062

India (Mumbai)

0.00063

Malaysia (Kuala Lumpur)

0.00064

UK (London)

0.00065

UAE (Dubai)

0.00072

Backup for an ApsaraDB for MongoDB instance

If you configure automatic backup for an ApsaraDB for MongoDB instance or manually back up the data of an ApsaraDB for MongoDB instance in the ApsaraDB for MongoDB console, the generated backup files are stored in the region in which the ApsaraDB for MongoDB instance resides. You are charged for backup storage.

Note

You can purchase storage plans to offset the storage fees that are generated if you configure automatic backup for an ApsaraDB for MongoDB instance or manually back up the data of an ApsaraDB for MongoDB instance in the ApsaraDB for MongoDB console.

Billing rules: If your backup storage (both full backup and log backup) falls within the free quota, no fees are charged. For excess backup storage, you are charged backup fees on an hourly basis. The backup fees are calculated by using the following formula: Backup fees per hour = (Backup storage - Free quota) × Unit price for backup files. The following tables describe the billing details.

Storage type

Free quota

View the backup storage and free quota

Instance that uses cloud disks

The free quota is equal to 200% of the storage capacity that you purchase for your instance.

You can view the backup storage and free quota in the Specification Information section of the Basic Information page of your instance.

Instance that uses local disks

The free quota is equal to 50% of the storage capacity that you purchase for your instance.

The following table describes the billing details of the excess backup storage.

Storage type

Unit price of backup (USD per GB-day)

Instance that uses cloud disks

0.00096

Instance that uses local disks

0.0048

Use subscription storage plans

If you have a large amount of data to store, we recommend that you purchase DBS storage plans to offset storage fees. This section describes the prices of storage plans for backup instances and copy data management (CDM) sandbox storage plans. For information about the usage notes and purchase methods of DBS storage plans, see Use storage plans.

Important

The prices in this section are for reference only. The prices displayed on the buy page prevail.

Prices of storage plans for backup instances

Plan specifications

Unit price (USD per 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

Prices of CDM sandbox storage plans

For more information, see DBS sandbox fees.

Offset objects

The following table describes the two types of DBS storage plans. You can purchase storage plans of various specifications such as 100 GB, 500 GB, 1 TB, and 500 TB. You can also purchase storage plans of various validity periods such as one month, six months, and one year. If your storage plans are used up, you are charged fees for excess storage on a pay-as-you-go basis.

Plan type

Offset object

CDM sandbox storage plans

CDM sandbox storage plans are used to offset the storage fees for the sandbox instances that are created within the same Alibaba Cloud account.For information about the billing details of the CDM sandbox feature, see DBS sandbox fees.

Storage plans for backup instances

Storage plans for backup instances are used to offset the built-in DBS storage fees for backup schedules within the same Alibaba Cloud account. For more information, see Built-in storage and OSS.

Offset rules

Item

Description

Offset methods

  • DBS calculates the total backup storage space used by your instances on a daily basis. Offset factors are used to calculate the storage space that can be offset by the purchased storage plans. The excess storage is charged by using the pay-as-you-go billing method.

  • The quota of a storage plan is used to offset the storage space that you use on a daily basis.

    For example, you purchase a storage plan of 100 GB whose validity period is one month. In this case, 100 GB of storage space is available for offsetting the storage space that you use every day within one month. For more information about offset examples, see the Offset examples of storage plans section of this topic.

Offset order

Fees are offset from bills based on the order in which the bills are issued.

Offset examples of storage plans

For example, you purchase a storage plan of 100 GB to offset the storage fees for a backup schedule of 120 GB in the China (Hong Kong) region. The following list describes the offset details:

  1. The built-in storage space that can be offset by the storage plan is about 88.4956 GB (100 GB/1.13). The storage plan cannot offset all the storage space of 120 GB. In this case, the system first uses the storage plan to offset the storage space of 88.4956 GB. The storage space used in this example is for reference only. The actual storage space in the bill prevails.

  2. The remaining storage space is 31.5044 GB (120 GB - 88.4956 GB), which is charged on a pay-as-you-go basis.

Note

The offset factor in the China (Hong Kong) region is 1.13. For more information, see the Offset factors of storage plans section of this topic.

Offset factors of storage plans

The following table describes the offset factors that you can use if you want to use storage plans to offset storage fees in different regions.

Offset factors of storage plans for backup instances

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) and India (Mumbai)

1.08

China (Hong Kong), Singapore, US (Silicon Valley), Indonesia (Jakarta), and Germany (Frankfurt)

1.13

Japan (Tokyo) and Australia (Sydney)

1.18