This topic describes the release notes for Database Backup (DBS) and provides links to the relevant references.

2022

Release date Feature Description References
May 2022 Fixed issues
  • The issue that an exception occurs when you unlock a DBS instance is fixed.
  • The issue of incorrect configuration logic that occurs when you modify an Object Storage Service (OSS) lifecycle rule is fixed.
  • The issue of incorrect logic for determining network changes during periodic scheduling by some sites is fixed.
  • The issue that cloud disks and snapshots cannot be created in the sandbox feature is fixed.
  • The issue that the emergency disaster recovery feature fails to be enabled for some sites is fixed.
N/A
April 2022 Optimization Refined management of whitelists is supported. N/A
Fixed issues
  • The issue that full backup sets are issued repeatedly for CDM sandbox instances is fixed.
  • The issue that some RDS whitelists are deleted by the system by mistake due to overwriting when the whitelists are refreshed is fixed.
N/A
March 2022 Frequent backup within single-digit seconds and backup file download ApsaraDB RDS for MySQL instances with standard or enhanced SSDs support frequent backup within single-digit seconds. You can implement frequent backups at intervals of 15 minutes, which improves the backup efficiency. This type of instance also allows you to convert a backup file into a CSV file and download the file to an on-premises device. This helps you analyze data or archive data to an on-premises device.
Fast restoration of individual databases and tables ApsaraDB RDS for MySQL supports fast restoration of individual databases and tables. Compared with the regular restoration feature, this new restoration feature improves the restoration speed by two to ten times for instances with local SSDs. Restore individual databases and tables of an ApsaraDB RDS for MySQL instance
Optimization A workaround is added for the issue that data backups are performed at a time beyond the specified time windows in the China (Hohhot) and central sites. N/A
Fixed issues
  • The issue that MySQL table partitions cannot be sorted in the ascending order after a schema restoration is fixed.
  • The issue of security vulnerability caused by PostgreSQL connection strings is fixed.
N/A
February 2022 Fixed issue The issue that data sets fail to be downloaded and restored is fixed. N/A
January 2022 Fixed issues
  • A workaround is added for the issue that a DRDS backup set loses its unique constraint.
  • The issue that a MySQL table fails to be created because the partition order does not comply with MySQL rules when MySQL data is being restored is fixed.
  • The issue that CDM sandbox instances do not release ZFS file systems properly is fixed.
  • The issue that TAR files fail to be downloaded and IDs of Elastic Cloud Service (ECS) instances fail to be obtained after DBS restarts in the China (Hangzhou) site is fixed.
  • The issue that the value of the live_mount parameter is invalid fixed.
N/A

2021

Release date Feature Description References
December 2021 Optimization Physical backup gateways are upgraded to improve the security of physical backup data. Add a backup gateway
November 2021 Backup set download fees Fees are charged for the downloads of backup sets over the Internet. Network traffic fees
August 2021 Optimization The emergency disaster recovery feature is further enhanced to allow you to create a privileged account in a sandbox instance. Create a sandbox instance for emergency disaster recovery of an ApsaraDB RDS for MySQL database
July 2021 Deletion of backup sets You can delete backup sets. Delete a backup set
June 2021 Emergency disaster recovery The emergency disaster recovery feature is enhanced. Create a sandbox instance for emergency disaster recovery of a self-managed MySQL database
Optimization For emergency instances, reading of binary log files is accelerated at the backend, and snapshots can be generated based on binary log files without processing at the backend. N/A
Fixed issues
  • The issue that the error message "dataset not exist" is displayed when you release a DBS sandbox instance is fixed.
  • The issue of failing to restore a data source based on a backup schedule is fixed.
  • The issue of failing to specify the port number of a public endpoint in the console when you restore databases is fixed.
  • The issue of failing to obtain valid instance and remap information when you perform logical backups for PolarDB for Oracle databases is fixed.
N/A
May 2021 Network-attached storage (NAS) storage pool Self-managed Object Storage Service (OSS) buckets and NAS file systems are supported in addition to the built-in storage space of DBS. This facilitates backup management. What is a storage pool?
Fixed issues
  • The issue of failing to delete expired backup sets is fixed.
  • The issue of failing to redeploy machines due to the soft deletion of a backup gateway is fixed.
  • The issue of failing to enable incremental backup for MariaDB databases is fixed.
N/A
April 2021 True incremental-forever backup for an Oracle database Full backup and synthetic backup are supported to reduce backup costs and resource overheads. This feature is in public preview. To use this feature, join the DingTalk group whose ID is 35585947. Create a true incremental-forever backup for an Oracle database
Backup gateway V0.0.113
  • The parameter files that are used to create Oracle Windows services and Oracle standalone databases are restored.
  • A backup gateway can be configured at the frontend to disable databases before data is restored and enable databases after data is restored.
N/A
New regions DBS is newly available on Alibaba Gov Cloud and in the China (Heyuan) and China (Ulanqab) regions of the Alibaba Cloud public cloud. N/A
Fixed issue The issue of the repeated creation of incremental tasks for primary and secondary MongoDB instances is fixed. N/A
March 2021 Multi-level storage pool The multi-level storage pool feature is supported to allow data backups to be automatically replicated across storage pools. Backup policies that use multi-level storage pools are configured to manage on-premises and cloud databases and share data backups among storage pools. This enhances security and reduces backup costs. This feature is in public preview. To use this feature, join the DingTalk group whose ID is 35585947. Create a backup policy that uses multiple levels of storage pools
Source deduplication The source deduplication feature is supported to back up only data that has been modified since the last backup and ignore other data that has been backed up. This greatly reduces bandwidth and storage costs. This feature is in public preview. To use this feature, join the DingTalk group whose ID is 35585947. Source deduplication for MySQL databases
Optimization
  • The Supported regions operation is optimized to improve availability.
  • The restoration feature is optimized so that a sandbox instance can be restored to the point in time of the latest snapshot when the sandbox instance cannot be restored to a specified point in time.
  • Automatic access to data sources is disabled, which does not affect the backup set synchronization feature of the backup schedules that have been synchronized.
N/A
Fixed issue Configuration issues of the Malaysia (Kuala Lumpur) region are fixed. N/A
January 2021 DBS sandbox The public preview period of the DBS sandbox feature ends on January 28, 2021. After January 28, 2021, you are charged for the use of the sandbox feature.
  • If the sandbox feature is enabled for backup schedules after 00:00:00 on January 28, 2021 (UTC+8), you are charged based on DBS sandbox fees.
  • If the sandbox feature is enabled for backup schedules before 00:00:00 on January 28, 2021 (UTC+8), DBS extends the validity period of public preview to 00:00:00 on March 1, 2021 (UTC+8).

    If you want to continue using the sandbox feature after the public preview period ends, go to the DBS console to re-enable the sandbox feature.

Overview
Backup for MySQL based on logs MySQL databases can be backed up based on binary logs by using the physical backup method. This helps you achieve a recovery point objective (RPO) within seconds. Back up binary logs of a MySQL database

2020

Release date Feature Description References
November 2020 Batch operations on data sources Batch import, backup, and including of data sources are supported. Backup tasks can be managed in batches based on backup policies and logical groups.
Recovery drill Recovery drills are supported to verify the integrity of backup data and the reliability of the disaster recovery system. Disaster recovery drills
October 2020 Backup of MariaDB databases MariaDB 10.0 and 10.3 databases can be backed up, including ApsaraDB RDS for MariaDB TX instances and self-managed MariaDB databases. Available soon
September 2020 Backup set query Backup sets can be queried without the need of restoring databases by using built-in Data Lake Analytics (DLA). Backup set query overview
Backup of files The data of the server that hosts your databases can be backed up in a centralized manner. The data includes logs, programs, and attachments. Back up files
DBS sandbox instance Sandbox instances can be created to make data of physical backups available in a short period of time. Overview