Billable item | Description | Billing method |
Backup fees | After you purchase and configure a backup schedule in the DBS console, DBS charges you based on the amount of data that is backed up. Backup and restoration performance, free quota for data backup, and prices vary based on backup schedule specifications. For more information, see Backup fees. | Subscription |
Storage fees | DBS charges you the following backup storage fees: DBS storage fees: If you configure a backup schedule and set the storage type to DBS Built-in Storage in the DBS console, DBS charges you based on the amount of data that is backed up in the built-in storage and the storage duration. If you configure a backup schedule to back up data to a self-managed Object Storage Service (OSS) bucket or Apsara File Storage NAS (NAS) file system, you are not charged storage fees.
Note In most cases, if the stored data is compressed or the format of the stored data is optimized, the size of the stored data is smaller than the space that is occupied by the data on database disks. For more information, see Data amount. Storage fees for backing up an ApsaraDB RDS for MySQL instance that uses standard SSDs or enhanced SSDs (ESSDs) across regions: If you enable the cross-region backup feature for an ApsaraDB RDS for MySQL instance that uses standard SSDs or ESSDs in the ApsaraDB RDS console, the backup files that are generated are stored in the destination region. DBS charges you for the backup storage. For more information, see Storage fees. Storage fees for backing up a PolarDB for MySQL cluster across regions: If you enable the cross-region backup feature for a PolarDB for MySQL cluster in the PolarDB console, the backup files that are generated are stored in the destination region. DBS charges you for the backup storage. For more information, see Storage fees. Storage fees for storing backup sets of an ApsaraDB RDS for MySQL instance that uses local SSDs after the instance is deleted: The backup sets of an ApsaraDB RDS for MySQL instance that uses local SSDs are retained free of charge for seven days after the ApsaraDB RDS for MySQL instance is deleted in the ApsaraDB RDS console. Seven days later, you are charged for the resources that are used to store the backup sets. For more information, see Storage fees. Storage fees for backing up an ApsaraDB for MongoDB instance: If you configure automatic backup for an ApsaraDB for MongoDB instance or manually back up data of the instance in the ApsaraDB for MongoDB console, the backup files that are generated are stored in the region in which the instance resides. DBS charges you for the backup storage. For more information, see Storage fees.
| |
Network traffic fees | DBS charges you the following network traffic fees: | |
DBS sandbox fees | DBS charges you for the sandbox instances that you create in the DBS console. You can use the sandbox feature to restore backup sets. This way, your backup data become available within seconds. For more information, see Overview. | For more information, see DBS sandbox fees. |