Starting January 11, 2024, ApsaraDB RDS for MySQL is upgrading its log backup feature to provide enhanced point-in-time recovery (PITR). This new backup policy lets you configure your recovery window more clearly. After the upgrade, you no longer need to keep the retention periods for full and log backups consistent. You only need to configure the Time Range of Restoration Points, and the system automatically manages the backup dependencies to ensure your data is protected.
Rollout schedule and regions
-
This feature is rolling out in phases across regions. Support for upgrading both new and existing instances will also be enabled in phases. For the latest information, check the ApsaraDB RDS console.
-
For new instances, the point-in-time recovery feature may take several hours to become available after creation. We appreciate your patience.
|
Rollout date |
Instance type |
Region |
|
Phased rollout starting January 11, 2024 |
ApsaraDB RDS for MySQL with high-performance local disk |
China (Hohhot), China (Chengdu), China (Zhangjiakou), Singapore, Japan (Tokyo), South Korea (Seoul), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila), Thailand (Bangkok), Germany (Frankfurt), and UK (London). |
|
Phased rollout starting February 15, 2024 |
China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Shenzhen), China (Ulanqab), China (Heyuan), and China (Guangzhou). |
|
|
Phased rollout starting January 30, 2024 |
ApsaraDB RDS for MySQL with cloud disk (including serverless instances) |
China (Hohhot), China (Chengdu), China (Zhangjiakou), Singapore, Japan (Tokyo), South Korea (Seoul), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila), Thailand (Bangkok), Germany (Frankfurt), and UK (London). |
|
Phased rollout starting February 15, 2024 |
China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Shenzhen), China (Ulanqab), China (Heyuan), and China (Guangzhou). |
Upgrade
-
After you upgrade an ApsaraDB RDS for MySQL instance to use point-in-time recovery, the backup retention logic is also upgraded. The system retains backup sets based on your configured Time Range of Restoration Points.
-
For existing instances, before the upgrade, you can restore data only to a point in time later than the earliest full backup within the log backup retention period. After the upgrade, you can restore data to any point in time within your configured PITR retention period.
|
Instance storage type |
Affected scope |
Description |
|
high-performance local disk |
New instances |
For instances created on or after January 11, 2024, point-in-time recovery is enabled by default. If needed, you can disable the Point-in-time Restore feature, which also disables log backups. Disabling it makes point-in-time recovery unavailable. |
|
Existing instances |
For instances created before January 11, 2024, you can manually upgrade the log backup feature to point-in-time recovery. This action is irreversible. However, you can still disable the Point-in-time Restore feature if needed. This also disables log backups, making point-in-time recovery unavailable. For instructions, see Upgrade to point-in-time recovery. |
|
|
cloud disk |
New instances |
For instances created on or after January 30, 2024, point-in-time recovery is enabled by default. If needed, you can disable the Point-in-time Restore feature, which also disables log backups. Disabling it makes point-in-time recovery unavailable. |
|
Existing instances |
For instances created before January 30, 2024, you can manually upgrade the log backup feature to point-in-time recovery. This action is irreversible. However, you can still disable the Point-in-time Restore feature if needed. This also disables log backups, making point-in-time recovery unavailable. For instructions, see Upgrade to point-in-time recovery. |
Billing
The backup billing logic remains unchanged. To guarantee PITR, the system retains some backup sets beyond the Log Backup Retention Period that you configure. These backup sets count toward Total Backup Size. If the total backup size stays within the free quota, no backup charges apply. Any storage that exceeds the free quota is billed based on actual usage. For billing details, see Backup guide.
Upgrade to point-in-time recovery
To upgrade the log backup feature to point-in-time recovery for an existing instance, follow these steps. For more information, see Differences between point-in-time recovery and log backup.
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 Recovery. On the Backup and Recovery page, click the Backup Strategy tab, and then click Edit in the Basic Backup section.
-
In the dialog box that appears, read the feature description and click Enable now..
-
In the confirmation dialog box, read the pre-upgrade notice, select OK, and then click OK, Upgrade to Point-in-time Protection.
Related operations
-
You can modify your point-in-time recovery policy, such as the PITR retention period, or disable the feature. For more information, see Configure a point-in-time recovery policy.
-
You can use data backups and log backups to restore data to an existing instance, a new instance, or an on-premises database. See Overview of data restoration methods for details.
-
You can download data or log backups to a local device or upload them to Object Storage Service (OSS) for archiving. For more information, see Download a backup set.