You are charged for the network traffic generated when you back up data across regions in the ApsaraDB RDS console, PolarDB console, and ApsaraDB for MongoDB console, or download backup sets by using the public URLs provided in the ApsaraDB RDS console. You are charged for network traffic for the following types of databases: ApsaraDB RDS for MySQL, ApsaraDB RDS for PostgreSQL, ApsaraDB RDS for SQL Server, PolarDB for MySQL, and ApsaraDB for MongoDB.
Usage notes
If you perform management operations related to the change of cloud disks on an ApsaraDB RDS instance that uses cloud disks, such as recreating a secondary database, the network traffic consumed for cross-region backups of the instance increases. Therefore, the network traffic fees of cross-region backups increase. The code of the billable item is NetworkOutDuplicationSize.
For example, if you perform DDL operations on an ApsaraDB RDS instance that uses cloud disks, and these operations cause high latency between the primary and secondary databases. To ensure service stability, the system may automatically recreate the secondary database. This increases the network traffic fees for cross-region backups.
Pay network traffic fees on a pay-as-you-go basis
Cross-region backup
References
Backup set download
Download backup sets over an internal network: You are not charged for downloading regular backup sets or cross-region backup sets over an internal network.
Download backup sets over the Internet: The free quota for backup set downloads over the Internet is 500 GB per instance-month. If the free quota is used up, you are charged for the excess traffic consumed to download backup sets over the Internet. Fees are deducted on a daily basis. To view the bills, go to the Bill Details page of the Expenses and Costs console and click the Billing Details tab.
Source region
Price (USD per GB)
Region in the Chinese mainland
0.125
China (Hong Kong)
Regions outside China
0.15
NoteTo view the volume of traffic that you consumed to download backup sets over the Internet, you can log on to the ApsaraDB RDS console, click the ID of your ApsaraDB RDS instance to go to the Basic Information page, and then view the Backup Downloads parameter in the Usage Statistics section.
The free quota for backup set downloads over the Internet is calculated by calendar month. The free quota for a month is effective as of the first day of the month. If the free quota is not used up in a month, the remaining quota becomes invalid at the end of the month.
If the backup sets fail to be downloaded, no network traffic fees are generated.
References
Use subscription network plans
If you need to back up or download a large amount of data, we recommend that you purchase DBS network plans to offset the network traffic that you consume to back up data across regions and download backup sets over the Internet. The validity period of a network plan is one year. A network plan with a larger capacity provides a higher discount. If your network plan is used up, you are charged for the excess traffic on a pay-as-you-go basis.
The following prices are for reference only. The prices displayed on the buy page prevail.
Network plan specification | Price (USD per year) |
1 TB | 102 |
5 TB | 448 |
10 TB | 832 |
50 TB | 3,520 |
100 TB | 6,400 |
500 TB | 25,600 |
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, and ApsaraDB for MongoDB databases in all regions. The consumed 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 the 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 consumed network traffic is offset by the network plan based on the offset factors in different regions. |
Offset rules
Item | Description |
Offset method |
|
Offset order | Fees are offset from bills based on the order in which the bills are issued. |
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. The cross-region backups consume 1,000 GB traffic and the backup set downloads consume 800 GB traffic. In this example, the bill of the cross-region backups is issued first. The following list describes the offset details:
Cross-region backup traffic that can be offset by the network plan: 1 TB/0.625 = 1.6 TB (1,638.4 GB).
The cross-region backup traffic is offset by the network plan first. Remaining quota of the network plan after the cross-region backup traffic is offset: (1,638.4 GB - 1,000 GB) x 0.625 = 399 GB.
Backup set download traffic that can be offset by the remaining quota of the network plan: 399 GB/1 = 399 GB. This is insufficient to offset the 800 GB traffic consumed by the backup set downloads.
Remaining backup set download traffic after the offset: 800 GB - 399 GB = 401 GB. This traffic is billed on a pay-as-you-go basis.
In the China (Hangzhou) region, the offset factor for cross-region backup is 0.625, and the offset factor for backup set download is 1. For more information, see the Offset factors section of this topic.
Offset factors
Offset factors for cross-region backup for ApsaraDB RDS instances
Source region | Destination region | Offset factor |
Chinese mainland | Chinese mainland | 0.625 |
China (Hong Kong) | 4.625 | |
China (Hong Kong) | Chinese mainland | 4.625 |
Regions outside China | 8 | |
Regions outside China | Chinese mainland | 4.625 |
| 8 |
Offset factors for cross-region backup for PolarDB for MySQL clusters and ApsaraDB for MongoDB instances
For more information about the offset factors for cross-region backup for PolarDB for MySQL clusters and ApsaraDB for MongoDB instances, see the Pay network traffic fees on a pay-as-you-go basis section of this topic.
Offset factors for backup set downloads
Source region | Offset factor |
Region in the Chinese mainland | 1 |
| 1.25 |