Use network plans

Updated at: 2025-02-17 09:58

Database Backup (DBS) provides subscription network plans. After you purchase network plans by using an Alibaba Cloud account, you can use the network plans to offset the network traffic fees that are generated for backing up data across regions in the ApsaraDB RDS and PolarDB consoles, and the network traffic fees that are generated for downloading backup sets in the ApsaraDB RDS console. You are no longer charged for the network traffic for which fees are offset by network plans. You are charged only for the excess network traffic on a daily basis. You can use network plans to offset the network traffic fees for instances of the following types: ApsaraDB RDS for MySQL, ApsaraDB RDS for PostgreSQL, ApsaraDB RDS for SQL Server, and PolarDB for MySQL.

Scenarios

If you back up a large amount of data across regions in the ApsaraDB RDS and PolarDB consoles or download a large number of backup sets in the ApsaraDB RDS console, we recommend that you purchase network plans to offset the network traffic fees that are generated during the backup or download. Subscription network plans are more cost-effective than the pay-as-you-go billing method. Network plans of higher specifications provide larger discounts.

Usage notes

  • The validity period of a network plan is one year. During the validity period, the network plan can be used to offset network traffic fees.

  • Network plans cannot be upgraded or unsubscribed.

  • You can purchase multiple network plans and use them together. For example, you can purchase a network plan of 50 TB and a network plan of 10 TB for the equivalent of a network plan of 60 TB.

  • If the network traffic that you use exceeds the quotas of your network plans, you are charged for the excess network traffic on a pay-as-you-go basis.

Important

Network plans become invalid after they expire. Expired network plans cannot be used to offset network traffic fees.

Offset objects

Offset object

Description

Offset object

Description

Network traffic for cross-region backups

DBS network plans can be used in all regions worldwide. After you purchase a network plan, you can use the network plan to offset the network traffic consumed by cross-region backups of ApsaraDB RDS for MySQL, ApsaraDB RDS for PostgreSQL, ApsaraDB RDS for SQL Server, PolarDB for MySQL, PolarDB for PostgreSQL, and ApsaraDB for MongoDB databases in all regions. The network traffic is offset by the network plan based on the offset factors in different regions.

Network traffic for backup set downloads

DBS network plans can be used in all regions worldwide. After you purchase a network plan, you can use the network plan to offset network traffic consumed by backup set downloads of ApsaraDB RDS for MySQL, ApsaraDB RDS for PostgreSQL, and ApsaraDB RDS for SQL Server databases in all regions. The network traffic is offset by the network plan based on the offset factors in different regions.

Offset rules

Item

Description

Item

Description

Offset method

  • DBS calculates the total network traffic consumed by your cross-region backups and backup set downloads on a daily basis. Offset factors are used to calculate the network traffic that can be offset by the purchased network plans. The excess network traffic is billed by using the pay-as-you-go billing method.

  • The quota of a network plan is used to offset the actual volume of consumed network traffic.

    For example, you purchase a network plan of 1 TB whose validity period is one year. In this case, 1 TB of network traffic can be used to offset the consumed network traffic within one year. For more information about offset examples, see the Offset example section of this topic.

Offset order

Network traffic is offset based on the order in which bills are issued in chronological order.

Offset example

For example, you purchase a network plan of 1 TB to offset the network traffic consumed by cross-region backups and backup set downloads for an ApsaraDB RDS for MySQL instance in the China (Hangzhou) region. 1,000 GB of traffic is consumed for cross-region backups and 800 GB of traffic is consumed for backup set downloads. In this example, the bill of the cross-region backups is issued first. The following content describes the offset details:

  1. Quota of the network plan that can be used to offset the traffic of cross-region backups: 1 TB/0.625 = 1.6 TB (1,638.4 GB).

  2. The traffic of cross-region backups is offset by the network plan first. Remaining quota of the network plan: (1,638.4 GB - 1,000 GB) x 0.625 = 399 GB.

  3. Quota of the network plan that can be used to offset the traffic of backup set downloads: 399 GB/1 = 399 GB. This is insufficient to offset the 800 GB of traffic consumed by backup set downloads.

  4. Remaining traffic of backup set downloads after the offset: 800 GB - 399 GB = 401 GB. This volume of traffic is billed on a pay-as-you-go basis.

Note

In the China (Hangzhou) region, the offset factor for cross-region backups is 0.625, and the offset factor for backup set downloads is 1. For more information, see the Offset factors section of this topic.

Offset factors

Offset factors of cross-region backups for ApsaraDB RDS in dedicated mode
Offset factors of cross-region backups for PolarDB for MySQL clusters, PolarDB for PostgreSQL clusters, and ApsaraDB for MongoDB instances
Offset factors of backup set downloads

Source region

Destination region

Offset factor

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

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

0.625

China (Hong Kong)

4.625

China (Hong Kong)

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

4.625

Thailand (Bangkok), South Korea (Seoul), Philippines (Manila), Japan (Tokyo), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), US (Silicon Valley), US (Virginia), Germany (Frankfurt), UK (London), and UAE (Dubai)

8

Thailand (Bangkok), South Korea (Seoul), Philippines (Manila), Japan (Tokyo), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), US (Silicon Valley), US (Virginia), Germany (Frankfurt), UK (London), and UAE (Dubai)

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

4.625

  • China (Hong Kong)

  • Thailand (Bangkok), South Korea (Seoul), Philippines (Manila), Japan (Tokyo), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), US (Silicon Valley), US (Virginia), Germany (Frankfurt), UK (London), and UAE (Dubai)

8

For more information about the offset factors of cross-region backups for PolarDB for MySQL clusters, PolarDB for PostgreSQL clusters, and ApsaraDB for MongoDB instances, see the Network traffic fees of cross-region backups for PolarDB for MySQL and PolarDB for PostgreSQL clusters section of this topic.

Source region

Offset factor

Regions in the Chinese mainland

1

  • China (Hong Kong)

  • Regions outside China

1.25

Purchase a network plan

  1. Go to the buy page of network plans.

  2. Configure the Specifications and Quantity parameters based on your business requirements.

    image.png

  3. Click Buy Now.
  • On this page (1, O)
  • Scenarios
  • Usage notes
  • Offset objects
  • Offset rules
  • Offset example
  • Offset factors
  • Purchase a network plan
Feedback
phone Contact Us