Starting December 1, 2023, the restoration feature for individual databases and tables for ApsaraDB RDS for MySQL instances that use cloud disks exits public preview and enters commercial release. Enabling the feature upgrades the backup architecture, which increases the amount of backup data by 30% to 80% and may generate backup fees.
Commercial release dates and regions
| Effective date | Involved instances | Regions |
|---|---|---|
| Commercially released in phases from December 1, 2023 | ApsaraDB RDS for MySQL instances that use cloud disks | All regions displayed in the ApsaraDB RDS console |
Billing
After you enable the restoration feature for individual databases and tables, the backup architecture is upgraded and the amount of backup data increases by 30% to 80%.
How fees are calculated:
If total backup storage does not exceed your free quota, no fees are charged.
If total backup storage exceeds your free quota, you are charged only for the excess.
To check your current backup storage usage and estimate cost impact, go to the Backup and Restoration page of your RDS instance and view backup file sizes. For details, see View and manage the size of backup files. For billing rates, see Backup storage fees.
Impact by instance creation date
After enabling the feature, you can restore backup data to the original RDS instance by backup set or by point in time. Restoring to a new RDS instance is not supported for instances that use cloud disks. For more information, see Restore individual databases and tables of an ApsaraDB RDS for MySQL instance.
Instances created on or after December 1, 2023
The restoration feature for individual databases and tables is automatically enabled and cannot be disabled.
Instances created before December 1, 2023
The restoration feature for individual databases and tables is forcefully disabled. To re-enable it, go to the Backup Strategy tab on the Backup and Restoration page of your RDS instance.
After you re-enable the feature:
All valid backup sets are immediately available for restoring individual databases and tables.
The feature cannot be disabled again.
What's next
After you restore data to the original RDS instance, run the
RENAME TABLEstatement to rename the restored table.ApsaraDB RDS for MySQL also supports full data restoration, emergency restoration, and restoration to the cloud or to an on-premises device using backup files. For an overview of all restoration methods, see Overview of data restoration methods.