Use network plans

A network plan is a subscription resource pack offered by Database Backup Service (DBS) that offsets network traffic fees for cross-region backups in the ApsaraDB RDS and PolarDB consoles, or for backup set downloads in the ApsaraDB RDS console, under the same account. Traffic covered by the plan is not billed; only excess traffic is charged on a pay-as-you-go basis. Supported products include ApsaraDB RDS for MySQL, ApsaraDB RDS for PostgreSQL, ApsaraDB RDS for SQL Server, and PolarDB for MySQL.

Scenarios

If you incur network traffic fees for cross-region backups in the ApsaraDB RDS and PolarDB consoles, or for backup set downloads in the ApsaraDB RDS console, and you handle a large volume of data, consider purchasing a DBS network plan. A subscription network plan is more cost-effective than pay-as-you-go billing.

Notes

A network plan is valid for one year and offsets network traffic fees during that period.
Network plans cannot be upgraded. Unsubscribing is not supported in all regions.
You can purchase and use multiple network plans at the same time. For example, purchase one 50 TB and one 10 TB plan to get a total of 60 TB.
If your network traffic exceeds the plan quota, the excess is charged on a pay-as-you-go basis.

Important

A network plan automatically becomes invalid upon expiration and no longer offsets network traffic fees.

Offset objects

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
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:

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).
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.
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.
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

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
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
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

Offset factors of cross-region backups for PolarDB for MySQL clusters, PolarDB for PostgreSQL clusters, and ApsaraDB for MongoDB instances

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.

Offset factors of backup set downloads

Source region	Offset factor
Regions in the Chinese mainland	1
China (Hong Kong) Regions outside China	1.25

Purchase a network plan

Go to the network plan buy page.
Select the Specifications and Quantity based on your requirements.

Other parameters include Region (Global), Type (General-purpose network plan), and Validity Period (1 year). Available specifications include 1 TB, 5 TB, 10 TB, 50 TB, 100 TB, and 500 TB.
Click Buy Now.