This topic describes the billable items and pricing for the backup storage of an ApsaraDB RDS for MySQL instance.
Billable items
Billable item | Billable item code | Associated product | References |
RDS basic backup | BackupCharged | ApsaraDB RDS | |
Cross-region backup storage for instances that use local SSDs | DdrOssStorageSize | ||
Cross-region backup storage for instances that use cloud disks | BackupStorageSize | Database Backup (DBS) | |
Cross-region backup traffic | NetworkOutDuplicationSize | ||
Outbound public traffic for backup downloads | NetworkOutSize | ||
Backup conversion for instances that use cloud disks | BackupAnalyticSize | ||
Backup set retention for deleted instances that use local SSDs | StandardStorageSize | Configure the backup retention policy for an instance after the instance is released | |
Backup set retention for deleted instances that use cloud disks | BackupStorageSize | ||
Database and table recovery storage for instances that use local SSDs | CapacitySandboxStorageSize |
Description for fees
If the total size of backup files does not exceed the free quota, you are not charged for the backup storage. If the total size exceeds the free quota, you are charged for the excess based on the usage. Hourly backup fee = (Total size of backup files - Free quota) × Unit price.
Notes
Backup fees are related to the size of backup files, not to the storage usage. This is because backup files do not occupy the storage space of your RDS instance.
When you analyze the backup fees, you must check the total size of backup files. You do not need to check the storage usage.
Operations that involve cloud disk replacement, such as secondary database reconstruction, have the following impacts on instances that use cloud disks:
The backup storage of the RDS instance that uses cloud disks increases. As a result, the backup storage fees increase. The code of the billable item is BackupCharged.
The traffic consumed by cross-region backups of the RDS instance that uses cloud disks increases. As a result, the traffic fees of cross-region backups increase. The code of the billable item is NetworkOutDuplicationSize.
The cross-region backup storage of the RDS instance that uses cloud disks increases. As a result, the fees generated for cross-region backup storage increase. The code of the billable item is BackupStorageSize.
NoteFor example, if a DDL operation causes a long replication delay on the secondary database, the system may automatically trigger secondary database reconstruction, which increases the fees.
Methods to reduce the backup storage fee
Reduce the total size of backup files
You can delete or reduce backup files. For more information, see Size of backup files.
Increase the free quota
You can scale up the storage capacity. For more information, see Change the specifications of an ApsaraDB RDS for MySQL instance.
The free quota is related to the storage capacity. For example, if you scale up the storage capacity from 150 GB to 300 GB, the free quota increases from 75 GB to 150 GB.
Billing FAQ
Why am I charged for automatic backup storage even if the total size of the backup files of my RDS instance exceeds the free quota? How do I disable the backup feature?
A: The default backup feature of ApsaraDB RDS is enabled by default and cannot be disabled. However, you can delete existing backup files or reduce the generation of new backup files by modifying the automatic backup policy. For more information, see Delete or reduce backup files.
Why am I charged for backup storage even if the total size of the backup files of my RDS instance does not exceed the free quota for backup storage?
A: You are charged for backup storage because the size of the backup files exceeded the free quota in the past, and the system does not deduct the additional fee at the earliest opportunity.
Why is the size of backup files larger than the amount of data on my RDS instance?
A: Instances that use cloud disks use snapshot backups. The size of a snapshot backup file may be much larger than the amount of data. When the system calculates the size of a snapshot backup file, the system counts in all the non-empty blocks to which data is written. If the data is written in a scattered manner, more non-empty blocks are generated. As a result, the snapshot backup file is larger.
The backup retention period of my RDS instance is shortened from x days to y days. Why does the size of backup files remain unchanged?
A: If no backup files are retained for more than y days, no backup files are deleted and the size of backup files remains unchanged after you shorten the backup retention period.
My RDS MySQL instance is released. Why am I still charged for backup storage?
A: Even if your RDS MySQL instance is released, if you configured a backup retention policy before the instance was released, the backup files are still stored on the Backup Management page of the ApsaraDB RDS console. After the RDS instance is deleted, the backup files of the RDS instance are retained free of charge for seven days. After the seven-day retention period elapses, you are charged for the storage of the backup files.
If you are still charged for backup storage after your RDS instance is released, the backup files of the RDS instance may be retained for more than seven days. In this case, fees are generated based on the storage usage and region. For more information about the billing standards, see Billing. If you no longer need the backup files, you can change the retention policy of the instance to Not Retained on the Deleted Instance Backup tab to avoid backup storage fees.