This topic describes the database engine versions and database objects that are supported by Database Backup (DBS), and the granularity of backup and restoration in DBS. This topic also describes the features that are supported by DBS for different types of databases.
Features for all supported databases
Compression: DBS reduces storage costs by means of compression, compact backup, and incremental backup.
Encryption: DBS uses SSL and AES-256 encryption to ensure security in the transmission and storage of backup data.
Throttling: DBS throttles the number of backup threads to reduce the impact on the performance of source databases.
Lifecycle management: DBS provides complete lifecycle management of backup sets and globally controls lifecycle rules to dump, clear, copy, and distribute automatic backup data.
Symbols in the tables
This section describes the symbols that are used in the tables in this topic.
️️✔️ indicates that the feature is supported.
❌ indicates that the feature is not supported.
For information about terms such as logical backup and full backup, see Logical backup, physical backup, and snapshot.
For information about how to back up and restore various types of databases in the DBS console, see Backup and restoration overview.
Relational Databases
Alibaba Cloud database services
Backup method
Feature
ApsaraDB RDS for MySQL
ApsaraDB RDS for SQL Server
ApsaraDB RDS for PostgreSQL
ApsaraDB RDS for MariaDB
PolarDB for MySQL
PolarDB for PostgreSQL
PolarDB-X
Logical backup
Supported versions
8.0
5.7
5.6
5.5
2019
2017
2016
2012
2008 R2
16
15
14
13
12
11
10
9.4
10.3
8.0
5.7
5.6
11
The storage type is ApsaraDB RDS for MySQL. The MySQL version is 5.x.
Data source type
MySQL
SQL Server
PostgreSQL
MariaDB
MySQL
Oracle
PostgreSQL
PolarDB-X
Full data backup
✔️
✔️
✔️
✔️
✔️
✔️
✔️
Incremental log backup
✔️
❌
❌
✔️
✔️
❌
❌
Real-time backup
RPO in seconds
RPO in days
RPO in days
RPO in seconds
RPO in seconds
RPO in days
RPO in days
Instance restoration
✔️
✔️
✔️
✔️
✔️
✔️
✔️
Minimum granularity
Table
Table
Table
Table
Table
Table
Database
✔️
✔️
✔️
✔️
✔️
✔️
✔️
✔️
✔️
✔️
❌
✔️
️️✔️ (Backup set query is supported only if the data source type is PostgreSQL.)
✔️
NoteRecovery Point Objective (RPO) is the point in time to which data can be restored after a disaster. RPO is used to measure the maximum amount of acceptable data loss in a disaster.
You can back up and restore Alibaba Cloud database services across accounts in DBS. For more information, see Back up and restore data across Alibaba Cloud accounts.
Self-managed databases hosted on Elastic Compute Service (ECS) instances, on-premises databases, and cloud databases from third-party providers
Backup method
Feature
MySQL
SQL Server
Oracle
PostgreSQL
MariaDB
Logical backup
Supported versions
8.0, 5.7, 5.6, and 5.5
SQL Server 2019, 2017, 2016, 2014, 2012, 2008 R2, and 2005 on Windows
12c, 11g, 10g, and 9i
11, 10, 9.5, 9.4, and 9.3
10.3 and 10
Data source type
MySQL
SQL Server
Oracle
PostgreSQL
MariaDB
Full data backup
✔️
✔️
✔️
✔️
✔️
Incremental log backup
✔️
❌
❌
❌
✔️
Real-time backup
RPO in seconds
RPO in days
RPO in days
RPO in days
RPO in seconds
Instance restoration
✔️
✔️
✔️
✔️
✔️
Minimum granularity
Table
Table
Table
Table
Table
✔️
✔️
✔️
✔️
✔️
✔️
✔️
✔️
✔️
❌
Physical backup
Supported versions
MySQL 8.0, 5.7, 5.6, and 5.5 on Linux
2019, 2017, 2016, 2014, 2012, 2008 R2, 2005, and 2000
11g, 10g, 12c, 18c, and 19c
❌
❌
Data source type
MySQL
SQL Server
Oracle
Full data backup
✔️
✔️
✔️
Incremental log backup
✔️
Binary logs can be backed up. For more information, see Back up binary logs of a MySQL database.
️️️️️️
✔️
✔️
Differential backup
✔️
❌
❌
Instance restoration
✔️
✔️
✔️
Minimum granularity
Instance
Database
Instance
✔️
✔️
✔️
❌
❌
❌
Restoration in minutes
✔️
❌
✔️
DBS sandbox
✔️
❌
✔️
NoSQL Databases
Backup method | Feature | MongoDB | Redis |
Logical backup | Database type |
|
|
Data source type | MongoDB | Redis | |
Supported versions | 4.2, 4.0, 3.6, 3.4, and 3.2 | 4.0 (standard master-replica architecture) Note Redis 5.0 or later is not supported. Redis cluster instances are not supported. Only instances of the standard master-replica architecture are supported. | |
Full data backup | ✔️ | ✔️ | |
Incremental log backup | ️️✔️ (Only the replica set architecture is supported.) | ✔️ | |
Real-time backup | RPO in 10 minutes | RPO in 10 minutes | |
Instance restoration | ✔️ | ✔️ | |
Minimum granularity | Collection | Database | |
✔️ | ❌ | ||
❌ | ❌ |
Database objects supported by logical backup
The following table describes the database objects that can be backed up and restored in DBS.
Database engine | Database object |
| Table, index, view, trigger, constraint, primary key, foreign key, stored procedure, and function |
| Table, index, view, function, stored procedure, constraint, foreign key, sequence, rule, domain, extension, and operator |
| Table, index, view, trigger, stored procedure, role, constraint, user-defined function, and user-defined table type |
SQL Server | Table, index, view, trigger, stored procedure, user, role, constraint, user-defined function, user-defined data type, and user-defined table type |
Oracle | Table, index, view, constraint, foreign key, sequence, trigger, function, stored procedure, synonym, and package |
Redis | STRING, BINARY, LIST, SET, SORTED SET, HASH, BITARRAY, HYPERLOG, GEO, and MODULE |
MongoDB | Table, collection, index, view, function, user, and role Note The admin databases in MongoDB cannot be backed up. |
References
For more information about DBS, see What is DBS?
For information about the specifications of backup schedule types and suggestions on selecting a backup schedule type, see Select a backup schedule type.
For information about the definitions of and differences between logical backup and physical backup, see Logical backup, physical backup, and snapshot and Select a backup method.
For information about fees that may be incurred for a backup schedule, see Billing FAQ.
For information about backup and restoration scenarios, such as backup to the cloud, geo-redundancy, backup security, and quick restoration, see Common scenarios.
If you want to back up a large amount of data, we recommend that you purchase a backup instance storage plan that is provided by DBS. You can use a storage plan to offset the storage fees that are generated for the built-in DBS storage used by backup schedules. For more information about purchasing storage plans, see the "FAQ" section of the Create a backup schedule topic.