This topic describes the release notes for Database Backup (DBS) and provides links to the relevant references.
DBS provides the backup and restoration features for ApsaraDB RDS, PolarDB, ApsaraDB for MongoDB, ApsaraDB for Redis, Tair, and AnalyticDB for PostgreSQL. The following tables describe the release notes of the features for these databases.
2024
Release date | Feature | Description | References |
September 2024 | Database and table restoration feature for ApsaraDB RDS for MySQL Cluster Edition instances | The database and table restoration feature is supported for ApsaraDB RDS for MySQL Cluster Edition instances. You can start a database and table restoration task for an instance based on the instance ID on the Backup and Restoration page in the ApsaraDB RDS console. | |
June 2024 | Logical backup feature for ApsaraDB RDS for PostgreSQL instances | DBS allows you to enable SSL encryption when you back up an ApsaraDB RDS for PostgreSQL instance by using logical backup. SSL encryption encrypts data at the transport layer during the backup process. This increases data security and ensures data integrity. | |
March 2024 | Database and table restoration feature for ApsaraDB RDS for PostgreSQL instances | The database and table restoration feature for ApsaraDB RDS for PostgreSQL instances allows you to restore databases and tables to the original instance from a backup set or to a specific point in time without the need to restore the full data of an instance. This feature can be used in scenarios such as data restoration after accidental operations, and historical data analysis. | |
January 2024 | Backup retention feature for PolarDB for PostgreSQL clusters | The retention period of a backup set in a PolarDB for PostgreSQL cluster of Standard Edition is increased from 14 days to 7,300 days. | |
Backup retention feature for PolarDB for MySQL clusters | The retention period of a backup set in a PolarDB for MySQL cluster of Standard Edition is increased from 14 days to 7,300 days. | ||
Cross-region backup feature for PolarDB-X instances | The cross-region backup feature is supported for PolarDB-X 2.0 instances. The system automatically migrates full backup data and incremental backup logs from one region to another after you configure a backup policy. You can also restore the data to a database instance in the destination region. This feature meets the requirements for high availability of databases and complies with the requirements of Multi-Level Protection Scheme (MLPS). | ||
PITR feature for ApsaraDB RDS for MySQL instances | The point-in-time restoration (PITR) feature for ApsaraDB RDS for MySQL instances is developed based on the log backup feature. After you turn on Restoration to Specific Point in Time and configure the Time Range of Specific Points in Time for Restoration parameter on the Backup Strategy tab, the system implements PITR based on the specified point in time and time range. The PITR feature resolves the issue that the restorable time range of your ApsaraDB RDS for MySQL instance is significantly shortened when the first full backup set of the instance is deleted due to expiration. |
2023
Release date | Feature | Description | References |
December 2023 | Backup download feature for ApsaraDB RDS for PostgreSQL instances | The backup download feature is supported for ApsaraDB RDS for PostgreSQL instances that use PL2 Enterprise SSDs (ESSD) and PL3 ESSDs. | |
Long-term backup retention feature for ApsaraDB RDS for MySQL instances | The long-term backup retention feature is supported for serverless and cloud disk-based ApsaraDB RDS for MySQL instances. You can configure a retention policy for the backup files of an ApsaraDB RDS for MySQL instance. This way, the backup files are retained for a long period of time even if the ApsaraDB RDS for MySQL instance is released. | ||
November 2023 | Backup download feature for PolarDB for MySQL clusters | The backup download feature for PolarDB for MySQL clusters allows you to download data in files of the following formats: CSV, SQL, and Parquet. This feature is applicable to data application scenarios such as on-premises development, test environment restoration, compliance auditing, and query analysis. | |
October 2023 | High-frequency backup feature for ApsaraDB for MongoDB instances | The high-frequency backup feature is supported for ApsaraDB for MongoDB sharded cluster instances. A backup can be completed within minutes or hours. This feature allows you to increase the full backup frequency to reduce the size of logs that are required for restoration at a point in time and reduce the recovery time objective (RTO). | |
Database and table restoration feature for PolarDB for MySQL clusters | The database and table restoration feature for PolarDB for MySQL clusters supports the restoration of millions of tables, which is far more than the original limited 50,000 tables. This feature also allows you to restore data that is accidentally deleted and meets the requirements of SaaS for a large amount of databases and tables. | ||
Fast database and table restoration feature for ApsaraDB RDS for PostgreSQL instances | The fast database and table restoration feature for ApsaraDB RDS for PostgreSQL instances is supported in all regions. | ||
September 2023 | Database and table restoration feature for PolarDB for MySQL clusters | The database and table restoration feature for PolarDB for MySQL clusters supports the restoration of millions of tables, which is far more than the original limited 50,000 tables. This feature also allows you to restore data that is accidentally deleted and meets the requirements of SaaS for a large amount of databases and tables. | Method 1 for database and table restoration: Restore data from a backup set |
August 2023 | Cross-region backup feature for ApsaraDB RDS for SQL Server instances | The cross-region backup and restoration feature is supported for ApsaraDB RDS for SQL Server instances for which Transparent Data Encryption (TDE) is enabled. This improves the backup and restoration capabilities of DBS. | |
Backup and restoration features for ApsaraDB RDS for PostgreSQL, ApsaraDB RDS for SQL Server, and ApsaraDB RDS for MariaDB TX instances | The tabs on the Backup and Restoration page for ApsaraDB RDS for PostgreSQL, ApsaraDB RDS for SQL Server, and ApsaraDB RDS for MariaDB TX instances are adjusted. The Data Backup and Log Backup tabs are merged into the Base Backups tab. The original Backup Settings tab is renamed Backup Strategy. The features on the tab remain unchanged. The adjustments further simplify and optimize the backup and restoration management page and improve user experience. | ||
Backup and restoration features for AnalyticDB for PostgreSQL instances | The backup and restoration features are supported for AnalyticDB for PostgreSQL V7.0 instances. | ||
July 2023 | Database and table restoration feature for ApsaraDB RDS for MySQL and ApsaraDB RDS for PostgreSQL instances | The database and table restoration feature is supported for cost-effective ApsaraDB RDS for MySQL and YiTian ApsaraDB RDS for PostgreSQL instances that use the Advanced RISC Machine (ARM) architecture. | |
Data restoration feature for ApsaraDB for MongoDB instances | The data restoration efficiency for ApsaraDB for MongoDB instances is improved by nearly 20 times. The data restoration, download, and playback are accelerated by using storage gateways. | ||
Database and table restoration feature for PolarDB for MySQL clusters | The database and table restoration feature is supported for PolarDB for MySQL clusters that contain millions of tables. | Method 1 for database and table restoration: Restore data from a backup set | |
Secondary database backup feature for ApsaraDB RDS for SQL Server instances | The secondary database preferred mode is supported for RDS instances that run RDS Cluster Edition. You can configure the system to perform physical backups on secondary RDS instances. This reduces the I/O loads on primary RDS instances and improves instance performance and stability. | ||
June 2023 | Backup download feature for ApsaraDB RDS for MySQL, ApsaraDB RDS for PostgreSQL, and ApsaraDB RDS for SQL Server instances |
| |
May 2023 | Backup and restoration features for PolarDB for PostgreSQL clusters | The backup and restoration feature based on PolarStore and Elastic Compute Service (ECS) is supported for PolarDB for PostgreSQL clusters. | |
Cross-region backup feature for ApsaraDB RDS for MySQL, ApsaraDB RDS for SQL Server, and ApsaraDB RDS for PostgreSQL instances, and PolarDB for MySQL clusters | The unit price for network traffic that is generated during cross-region backups is reduced for ApsaraDB RDS for MySQL, ApsaraDB RDS for SQL Server, and ApsaraDB RDS for PostgreSQL instances, and PolarDB for MySQL clusters. | ||
April 2023 | Database and table restoration feature for ApsaraDB RDS for MySQL instances and PolarDB for PostgreSQL clusters | The database and table restoration feature is optimized for ApsaraDB RDS for MySQL instances that use standard SSDs or ESSDs and PolarDB for PostgreSQL clusters. | |
Fast restoration feature for individual databases and tables in ApsaraDB RDS for PostgreSQL instances | The fast restoration feature is supported for individual databases and tables in ApsaraDB RDS for PostgreSQL instances that use standard SSDs or ESSDs. You can restore databases and tables to the original instance from a backup set or to a specific point in time without the need to restore the full data of an instance. This feature can be used in scenarios such as data restoration after accidental operations, and historical data analysis. | ||
March 2023 | High-frequency physical backup feature for ApsaraDB RDS for MySQL V8.0 High-availability Edition instances that use local SSDs | The high-frequency physical backup feature is supported for ApsaraDB RDS for MySQL V8.0 High-availability Edition instances that use local SSDs. You can enable this feature for your instance to increase the backup frequency. | |
February 2023 | Fast restoration feature for individual databases and tables in ApsaraDB RDS for MySQL instances that use standard SSDs or ESSDs | The fast restoration feature is supported for individual databases and tables in ApsaraDB RDS for MySQL instances that use standard SSDs or ESSDs. You can restore databases and tables to the original instance from a backup set or to a specific point in time. This feature can be used in scenarios such as data restoration after accidental operations, and historical data analysis. | |
January 2023 | Logical backup feature for PolarDB for MySQL clusters | Logical backup by using DBS is supported for PolarDB for MySQL clusters. |
2022
Release date | Feature | Description | References |
December 2022 | Optimized cross-region backup feature for ApsaraDB RDS for SQL Server instances | The cross-region backup feature is optimized. If your ApsaraDB RDS instance runs SQL Server 2017 EE on RDS Cluster Edition and the snapshot backup feature is enabled for the instance, you can use the cross-region backup feature to back up data from one region to another in the ApsaraDB RDS console for regulatory compliance or disaster recovery. | Use the cross-region backup feature for an ApsaraDB RDS for SQL Server instance |
Cross-region backup feature for ApsaraDB RDS for MySQL instances that use standard SSDs or ESSDs | The cross-region backup feature is supported for ApsaraDB RDS for MySQL instances that use standard SSDs or ESSDs. You can use the cross-region backup feature to back up data from one region to another for regulatory compliance or disaster recovery. | Use the cross-region backup feature for an ApsaraDB RDS for MySQL instance | |
October 2022 | Optimized automatic backup feature for ApsaraDB RDS for SQL Server instances | The automatic backup feature is optimized. When you configure a physical backup policy for an ApsaraDB RDS for SQL Server instance, you can enable or disable the incremental backup feature. By default, this feature is enabled. After the incremental backup feature is enabled, automatic backups are performed based on the backup cycle that you specify. The backup cycle consists of three phases: a full backup, an incremental backup, and another incremental backup. | |
Optimized manual backup feature for ApsaraDB RDS for SQL Server instances | The manual physical backup feature for ApsaraDB RDS for SQL Server instances is optimized based on improved scheduling algorithms and concurrency control. For example, if you manually create multiple single-database backup tasks for an ApsaraDB RDS for SQL Server instance, the efficiency of the manual backup tasks is significantly improved. | ||
Advanced download feature for ApsaraDB RDS for PostgreSQL instances | The advanced download feature is supported for ApsaraDB RDS for PostgreSQL instances. You can use this feature to create advanced download tasks by point in time or backup set. You can set the Download Destination parameter to URL or directly upload the downloaded data to your Object Storage Service (OSS) bucket to facilitate data analysis and offline archiving. | ||
September 2022 | New regions in which the advanced download feature is supported for ApsaraDB RDS for MySQL instances | The advanced download feature is supported for ApsaraDB RDS for MySQL instances in the following regions: Singapore, US (Silicon Valley), and US (Virginia). | |
August 2022 | Advanced download feature for ApsaraDB RDS for MySQL instances | The advanced download feature is supported for ApsaraDB RDS for MySQL instances. You can use this feature to create advanced download tasks by point in time or backup set. You can set the Download Destination parameter to URL or directly upload the downloaded data to your OSS bucket to facilitate data analysis and offline archiving. | |
High-frequency backup feature for ApsaraDB for MongoDB replica set instances that use ESSDs | The high-frequency backup feature is supported for ApsaraDB for MongoDB replica set instances that use ESSDs. You can specify a backup frequency that ranges from 15 minutes to 12 hours for your ApsaraDB for MongoDB instance to increase the backup frequency. | ||
July 2022 | High-frequency physical backup feature for ApsaraDB RDS for MySQL instances | The high-frequency physical backup feature is supported for ApsaraDB RDS for MySQL instances. You can enable the high-frequency physical backup feature for your ApsaraDB RDS for MySQL instance to increase the backup frequency. | Use the high-frequency physical backup feature for an ApsaraDB RDS for MySQL instance |
High-frequency snapshot backup feature for ApsaraDB RDS for PostgreSQL instances | The high-frequency snapshot backup feature is supported for ApsaraDB RDS for PostgreSQL instances. You can specify a backup frequency that ranges from 15 minutes to 12 hours for your ApsaraDB RDS for PostgreSQL instance to increase the backup frequency. | Use the high-frequency snapshot backup feature for an ApsaraDB RDS for PostgreSQL instance | |
June 2022 | Cross-region backup feature for PolarDB for MySQL clusters | The cross-region backup feature is supported for PolarDB for MySQL clusters. You can use the cross-region backup feature to back up data from one region to another for regulatory compliance or disaster recovery. You can enable the cross-region backup feature by configuring a backup policy. | |
Multi-level storage pool | The multi-level storage pool feature of DBS is gradually available after its public preview period ended on June 20, 2022. This feature is to be included in the infrastructure of DBS to provide services in scenarios such as cross-region backup and backup file download. Important The feature is available only for users who have joined the public preview. | Notice on the end of the public preview of the multi-level storage pool feature | |
May 2022 | Optimized configurations for backing up ApsaraDB RDS for PostgreSQL instances | The retention period of data backups can be changed for ApsaraDB RDS instances that run PostgreSQL 10 on RDS Basic Edition.
| |
Fixed issues |
| N/A | |
April 2022 | Data restoration from a backup set to a new instance for ApsaraDB for Redis instances that use standard SSDs or ESSDs | Data can be restored from a backup set to a new instance for ApsaraDB for Redis instances that use standard SSDs or ESSDs. The data in the new instance is the same as that in the backup set. This feature is suitable for scenarios such as data restoration, quick workload deployment, and data verification. | |
Optimized feature | Whitelists can be managed in a fine-grained manner. | N/A | |
Fixed issues |
| N/A | |
March 2022 | High-frequency snapshot backup feature for ApsaraDB RDS for MySQL instances | The high-frequency snapshot backup feature is supported for ApsaraDB RDS for MySQL instances that use standard SSDs or ESSDs. You can specify a backup frequency that ranges from 15 minutes to 12 hours for your ApsaraDB RDS for MySQL instance to increase the backup frequency. | |
Features of advanced download and data restoration from a downloaded backup set for ApsaraDB RDS for MySQL instances that use standard SSDs or ESSDs | The features of advanced download and data restoration from a downloaded backup set are supported for ApsaraDB RDS for MySQL instances that use standard SSDs or ESSDs. You can convert backup files to CSV files, download the backup files, and then restore the downloaded backup files to your on-premises MySQL databases. | ||
Fast restoration feature for individual databases and tables in ApsaraDB RDS for MySQL instances that use local SSDs | The fast restoration feature for individual databases and tables is supported for ApsaraDB RDS for MySQL instances that use local SSDs. Compared with the standard restoration feature for individual databases and tables, the fast restoration feature for individual databases and tables accelerates data restoration by 2 to 10 times for ApsaraDB RDS for MySQL instances that use local SSDs. | ||
Optimized feature | A solution is added for the issue that data backups are performed at a time beyond the specified time windows in the China (Hohhot) region and central sites. | N/A | |
Fixed issues |
| N/A | |
February 2022 | Fixed issue | The issue that backup sets fail to be downloaded and restored is fixed. | N/A |
January 2022 | Fixed issues |
| N/A |
2021
Release date | Feature | Description | References |
December 2021 | Optimized feature | Physical backup gateways are upgraded to improve the security of physical backup data. | |
November 2021 | Backup set download fees | You are charged for the downloads of backup sets over the Internet. | |
August 2021 | Creation of privileged accounts | The disaster recovery feature is further enhanced to allow you to create a privileged account in a sandbox instance. | Use the emergency recovery feature for an ApsaraDB RDS for MySQL instance |
July 2021 | Deletion of backup sets | Backup sets can be deleted. | |
June 2021 | Disaster recovery in an emergency | The disaster recovery feature is enhanced. | Use the emergency recovery feature for a self-managed MySQL database |
Optimized feature | For emergency instances, the 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 |
| N/A | |
May 2021 | Network-attached storage (NAS) storage pool | Self-managed OSS buckets and NAS file systems are supported in addition to the built-in storage space of DBS. This facilitates backup management. | |
Fixed issues |
| 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. | Create a true incremental-forever backup for an Oracle database |
Backup gateway V0.0.113 |
| N/A | |
New regions | DBS is available on Alibaba Gov Cloud and in the China (Heyuan) and China (Ulanqab) regions of the Alibaba Cloud public cloud. | N/A | |
Fixed issues | The issue of the repeated creation of incremental tasks for ApsaraDB for MongoDB instances that support primary/secondary switchover 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. You can configure backup policies that use multi-level storage pools to manage on-premises storage pools and storage pools in the cloud, and share data backups among storage pools. This enhances security and reduces backup costs. Note The public preview period of the multi-level storage pool feature of DBS ended on June 20, 2022. The feature is available only for users who have joined the public preview. | Notice on the end of the public preview of the multi-level storage pool feature |
Optimized feature |
| N/A | |
Fixed issue | Configuration issues are fixed in the Malaysia (Kuala Lumpur) region. | N/A | |
January 2021 | DBS sandbox | The public preview period of the DBS sandbox feature ended on January 28, 2021. After January 28, 2021, you are charged for the use of the sandbox feature.
| |
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. |
2020
Release date | Feature | Description | References |
November 2020 | Batch operations on data sources | Batch operations can be performed on data sources. For example, add multiple data sources at a time, back up databases from multiple data sources, and manage multiple data sources at a time. Multiple backup tasks can be managed at a time 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. | ||
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. | |
September 2020 | Backup set query | Backup sets can be queried by using built-in Data Lake Analytics (DLA), without the need to restore databases. | |
File backup | The data of the server that hosts your databases can be backed up in a centralized manner. The data includes logs, programs, and attachments. | ||
DBS sandbox instance | Sandbox instances can be created to make data of physical backups available in a short period of time. |