ApsaraDB RDS for MySQL provides the high-frequency physical backup feature by using incremental backups. You can enable the high-frequency physical backup feature for your ApsaraDB RDS for MySQL instance to increase the backup frequency and ensure data timeliness.
Your RDS instance must meet the following requirements:
Your RDS instance runs MySQL 5.6, MySQL 5.7, or MySQL 8.0.
Your RDS instance runs RDS High-availability Edition.
Your RDS instance uses local disks.
You can go to the Basic Information page of your RDS instance to view the preceding information.
If your RDS instance runs MySQL 8.0, make sure that the minor engine version is 20220830 or later. For more information, see Update the minor engine version.
Your RDS instance resides in one of the following regions: China (Hangzhou), China (Shanghai), China (Nanjing-Local Region), China (Qingdao), China (Beijing), China (Hohhot), China (Ulanqab), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Chengdu), China (Hong Kong), China (Fuzhou-Local Region), Japan (Tokyo), South Korea (Seoul), Singapore, Australia (Sydney), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila), Thailand (Bangkok), India (Mumbai), Germany (Frankfurt), UK (London), US (Silicon Valley), and US (Virginia).
If this is the first time you use the backup feature of ApsaraDB RDS, you must attach the AliyunServiceRoleForDBS policy by using your Alibaba Cloud account. For more information, see How do I create a service-linked role for DBS?
High-frequency physical backup disabled
High-frequency physical backup enabled
Once a day.
Every 1 to 12 hours.
Recovery time objective (RTO)
If the interval between two consecutive backups is long, the RTO is high. The longer the interval, the larger the amount of data that is generated within the interval.
The RTO is low.
Recovery point objective (RPO)
If you disable the log backup feature, only full backup files are generated. The RPO is subject to the points in time for full backups.
The number of backup files within a specific period of time increases with the backup frequency. The RPO is subject to the points in time for high-frequency physical backups.
Policy of backup file retention
A full backup file is automatically deleted after the expiration date.
A full backup file is not deleted after the expiration date because the incremental backup files that depend on the full backup file are valid. When all incremental backup files that depend on the full backup file expire, the full and incremental backup files are deleted.
Policy of backup file deletion
A full backup file can be deleted.
After you enable the high-frequency physical backup feature, a full backup is initiated only at the specified point in time, and incremental physical backups are performed based on the backup frequency that you specify.
If the secondary RDS instance is faulty, high-frequency backup tasks may fail.
Incremental physical backups are performed on the secondary RDS instance. If the secondary RDS instance is migrated or re-created, incremental physical backups can be performed on the new secondary RDS instance only after a full physical backup is performed on the new secondary RDS instance. This helps ensure data integrity.
Incremental backup files generated by the high-frequency physical backup feature cannot be used for cross-region backups. Only full backup file can be used for cross-region backups.
Backup storage fee
After the high-frequency physical backup feature is enabled, incremental physical backup files are generated. If the total size of the backup files of your RDS instance does not exceed the free quota on backup file storage, no fees are charged. For more information, see View and manage the size of backup files for an ApsaraDB RDS for MySQL instance. If the total size exceeds the free quota, you are charged for the excess backup storage that you use. For more information, see Backup storage pricing of an ApsaraDB RDS for MySQL instance.
In most cases, the size of an incremental physical backup file is smaller than the size of a full physical backup file.
The size of an incremental backup file varies based on the actual volume of the data that is modified or written to your RDS instance. If a small amount of data is written or modified, the size of the incremental backup file is small.
Enable or disable the high-frequency physical backup feature
- Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.
In the left-side navigation pane, click Backup and Restoration.
On the Backup and Restoration page, click the Backup Strategy tab.
In the Basic Backup section, click Edit to enable the high-frequency incremental backup feature.Note
After you turn on High-frequency Incremental Backup, you can configure the Frequency parameter. You can select Every 1 Hour for this parameter.
Before you can use this feature, make sure that your RDS instance runs MySQL 5.6, MySQL 5.7, or MySQL 8.0 on RDS High-availability Edition and uses local disks.
For more information about other parameters, see Use the automatic backup feature.
In the message that appears, click OK.