Database types and features supported by DMS - Data Management

This topic describes the database types that are supported by Data Management (DMS) and the features that are supported by each database type.

Database types supported by DMS

Supported Alibaba Cloud databases

Relational databases

ApsaraDB RDS for MySQL
ApsaraDB RDS for SQL Server
ApsaraDB RDS for PostgreSQL
ApsaraDB for MariaDB
PolarDB for MySQL
PolarDB for PostgreSQL
PolarDB for PostgreSQL(Compatible with Oracle)
PolarDB for Xscale (formerly DRDS)
ApsaraDB for OceanBase in MySQL mode
ApsaraDB for OceanBase in Oracle mode
ApsaraDB RDS for PPAS

Data warehouses

ApsaraDB for ClickHouse
AnalyticDB for MySQL 3.0
AnalyticDB for PostgreSQL
AnalyticDB for MySQL 2.0

NoSQL databases

Tair (Redis OSS-Compatible)
ApsaraDB for MongoDB
Note
ApsaraDB for MongoDB of Serverless Edition is not supported.
ApsaraDB for Cassandra
Lindorm SQL
Lindorm Phoenix
Lindorm CQL
Lindorm TSDB
Lindorm HBase
Graph Database

Big data

MaxCompute
MaxCompute Lighting

File and log service

OSS
Log Service

Supported cloud databases from third-party providers and self-managed databases

Relational databases

MySQL
SQL Server
PostgreSQL
MariaDB
ApsaraDB for OceanBase in MySQL mode
ApsaraDB for OceanBase in Oracle mode
OceanBase ODP
Oracle
Db2
Dameng
openGauss

Data warehouse

ApsaraDB for ClickHouse

NoSQL databases

Tair (Redis OSS-Compatible)
ApsaraDB for MongoDB

Big data

BigQuery

DMS features supported by each database type

Relational databases

Feature	MySQL (excluding PolarDB-X)	PolarDB-X	SQL Server	PostgreSQL (excluding PolarDB for PostgreSQL)	PolarDB for PostgreSQL	MariaDB	ApsaraDB for OceanBase in MySQL mode	Self-managed Oracle and ApsaraDB for OceanBase in Oracle mode	PolarDB for PostgreSQL (Compatible with Oracle)	DamengDB
Query	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️
Query for logical databases or collections	✔️	❌	✔️	✔️	✔️	➖	✔️	✔️	✔️	❌
Cross-instance query	✔️	✔️	✔️	✔️	✔️	❌	❌	❌	✔️	❌
SQL result set export	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️
Table data export	✔️	✔️	✔️	✔️	✔️	✔️	✔️	❌	✔️	✔️
Data change	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️
Historical data cleanup	✔️	✔️	❌	✔️	✔️	✔️	✔️	❌	✔️	✔️
Lock-free data change	✔️	✔️	❌	✔️	✔️	✔️	✔️	❌	✔️	❌
Data import	✔️	✔️	✔️	✔️	✔️	✔️	✔️	❌	✔️	✔️
Test data generation	✔️	✔️	✔️	✔️	✔️	✔️	✔️	❌	✔️	❌
Data tracking	✔️	➖	❌	❌	❌	➖	❌	❌	➖	❌
Database cloning	✔️	✔️	❌	➖	➖	✔️	✔️	❌	➖	❌
Schema change	✔️	✔️	✔️	✔️	✔️	✔️	✔️	❌	✔️	❌
Visualized schema modification	✔️	✔️	✔️	✔️	✔️	✔️	❌	❌	✔️	❌
Schema synchronization	✔️	✔️	❌	➖	➖	✔️	✔️	❌	➖	❌
Empty database initialization	✔️	✔️	❌	➖	➖	✔️	✔️	❌	➖	❌
Programmable object	✔️	❌	✔️	✔️	✔️	✔️	❌	❌	✔️	❌
Schema export	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️
Schema design pro	✔️	✔️	❌	❌	➖	➖	✔️	❌	➖	❌
Lock-free schema change	✔️	➖	❌	❌	❌	➖	❌	❌	❌	❌
Database creation	✔️	❌	❌	➖	❌	✔️	❌	❌	❌	❌
Database user creation	✔️	❌	❌	➖	❌	✔️	❌	❌	❌	❌
SQL review	✔️	➖	❌	✔️	✔️	➖	➖	✔️	✔️	❌
SQL and instance diagnostics	✔️	❌	❌	✔️	✔️	➖	❌	❌	✔️	❌
Sensitive data management	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️
Access control system	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️
Operation logs	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️
Task orchestration	✔️	✔️	✔️	✔️	✔️	❌	✔️	✔️	✔️	✔️
Ticket system	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️
Security rules	✔️	✔️	✔️	✔️	✔️	❌	✔️	✔️	✔️	✔️
Approval process	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️	✔️

Data warehouses

Feature	AnalyticDB for MySQL 2.0	AnalyticDB for MySQL 3.0	AnalyticDB for PostgreSQL	Clickhouse
Query	✔️	✔️	✔️	✔️
Query for logical databases or collections	❌	✔️	✔️	❌
Cross-instance query	❌	✔️	✔️	❌
SQL result set export	✔️	✔️	✔️	✔️
Table data export	❌	✔️	✔️	❌
Data change	✔️	✔️	✔️	✔️
Data import	✔️	✔️	✔️	❌
Test data generation	✔️	✔️	✔️	❌
Database cloning	❌	❌	➖	❌
Schema change	❌	✔️	✔️	✔️
Visualized schema modification	❌	✔️	✔️	❌
Schema synchronization	❌	✔️	➖	❌
Empty database initialization	❌	✔️	➖	❌
Programmable object	❌	❌	✔️	❌
Schema export	✔️	✔️	✔️	❌
Schema design pro	❌	❌	➖	❌
Database creation	❌	➖	➖	❌
Database user creation	❌	➖	➖	❌
SQL review	❌	➖	➖	❌
Sensitive data management	✔️	✔️	✔️	❌
Access control system	✔️	✔️	✔️	✔️
Operation logs	✔️	✔️	✔️	✔️
Task orchestration	✔️	✔️	✔️	❌
Ticket system	✔️	✔️	✔️	✔️
Security rules	✔️	✔️	✔️	✔️
Approval process	✔️	✔️	✔️	✔️

NoSQL databases

Feature	MongoDB	Redis	Lindorm	Cassandra	GDB
Query	✔️	✔️	✔️	✔️	✔️
Cross-instance query	❌	✔️	❌	❌	❌
SQL result set export	✔️	❌	✔️	✔️	❌
Table data export	❌	❌	➖	➖	❌
Data change	✔️	✔️	✔️	✔️	✔️
Schema change	❌	❌	✔️	✔️	❌
Database creation	✔️	❌	❌	❌	❌
Database user creation	✔️	❌	❌	❌	❌
SQL review	✔️	❌	❌	❌	❌
SQL and instance diagnostics	✔️	✔️	❌	❌	❌
Sensitive data management	❌	❌	✔️	➖	❌
Access control system	✔️	✔️	✔️	✔️	✔️
Operation logs	✔️	✔️	✔️	✔️	✔️
Ticket system	✔️	✔️	✔️	✔️	✔️
Security rules	✔️	✔️	✔️	✔️	✔️
Approval process	✔️	✔️	✔️	✔️	✔️

Big data

Feature	MaxCompute	Hologres	RestAPI
Query	✔️	✔️	❌
Query for logical databases or collections	❌	❌	❌
Cross-instance query	❌	❌	❌
SQL result set export	✔️	✔️	❌
Table data export	❌	❌	❌
Data change	✔️	✔️	❌
Data import	❌	✔️	❌
Test data generation	❌	❌	❌
Database cloning	❌	❌	❌
Schema change	❌	❌	❌
Visualized schema modification	❌	❌	❌
Schema synchronization	❌	❌	❌
Empty database initialization	❌	❌	❌
Programmable object	❌	❌	❌
Schema export	❌	❌	❌
Schema design pro	❌	❌	❌
Database creation	❌	❌	❌
Database user creation	❌	❌	❌
SQL review	❌	❌	❌
Sensitive data management	✔️	✔️	❌
Access control system	✔️	✔️	✔️
Operation logs	✔️	✔️	❌
Task orchestration	✔️	✔️	✔️
Ticket system	✔️	✔️	❌
Security rules	✔️	✔️	❌
Approval process	✔️	✔️	❌

File and log service

Feature	SLS	OSS
Query	✔️	✔️
Query for logical databases or collections	❌	❌
Cross-instance query	❌	❌
SQL result set export	✔️	❌
Table data export	❌	❌
Data change	❌	❌
Data import	❌	❌
Test data generation	❌	❌
Database cloning	❌	❌
Schema change	❌	❌
Visualized schema modification	❌	❌
Schema synchronization	❌	❌
Empty database initialization	❌	❌
Programmable object	✔️	❌
Schema export	❌	❌
Schema design pro	❌	❌
Database creation	❌	❌
Database user creation	❌	❌
SQL review	❌	❌
Sensitive data management	❌	❌
Access control system	✔️	✔️
Operation logs	✔️	❌
Task orchestration	❌	✔️
Ticket system	❌	❌
Security rules	❌	❌
Approval process	❌	❌

This section describes the symbols that are used in the tables of this topic:

️️️✔️ indicates that the feature is supported.
➖ indicates that the feature will be supported soon.
❌ indicates that the feature is not supported.

Database types supported by Data Disaster Recovery (formerly DBS)

Important

If the data source contains Chinese table names or field names, data recovery fails. In this case, join the DingTalk group (ID: 35585947) to provide feedback or submit a ticket.

Data Disaster Recovery (formerly DBS)

Relational databases
- Alibaba Cloud databases
- Self-managed databases hosted on Elastic Compute Service (ECS) instances, on-premises databases, and cloud databases from third-party providers
NoSQL databases
- MongoDB
- Redis
Databases supported by logical backup
- MySQL
- MariaDB
- PolarDB: PolarDB for PostgreSQL, PolarDB for MySQL, PolarDB for PostgreSQL (Compatible with Oracle), and PolarDB-X
- SQL Server
- Oracle
- Redis
- MongoDB

Disaster Recovery Data Source

Note

You can create a backup by using the disaster recovery data source module.

Alibaba Cloud databases: ApsaraDB RDS for MySQL, ApsaraDB RDS for PostgreSQL, ApsaraDB RDS for SQL Server, and PolarDB for MySQL
Self-managed databases hosted on Elastic Compute Service (ECS) instances: MySQL
On-premises databases, and cloud databases from third-party providers: MySQL

Data Disaster Recovery (formerly DBS) features supported by each database type

Relational databases

Alibaba Cloud databases

Backup method	Operation	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 2014 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	Tables	Tables	Tables	Tables	Tables	Tables	Database
	Backup set download	✔️	✔️	✔️	✔️	✔️	✔️	✔️
	Backup set query	✔️	✔️	✔️	❌	✔️	✔️️️️️ (Backup set query is supported only if the data source type is PostgreSQL.)	✔️

Note

Recovery 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 databases across accounts in Data Disaster Recovery. For more information, see Back up and restore data across Alibaba Cloud accounts.

Self-managed databases hosted on ECS instances, on-premises databases, and cloud databases from third-party providers

Backup method	Operation	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	Tables	Tables	Tables	Tables	Tables
	Backup set download	✔️	✔️	✔️	✔️	✔️
	Backup set query	✔️	✔️	✔️	✔️	❌
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
	Backup set download	✔️	✔️	✔️
	Backup set query	❌	❌	❌
	Restoration in minutes	✔️	❌	✔️
	Data Disaster Recovery sandbox	✔️	❌	✔️

NoSQL databases

Backup method	Operation	MongoDB	Redis
Logical backup	Database types	Alibaba Cloud databases Self-managed databases hosted on ECS instances On-premises databases Cloud databases from third-party providers	Alibaba Cloud databases Self-managed databases hosted on ECS instances On-premises databases Cloud databases from third-party providers
	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
	Backup set download	✔️	❌
	Backup set query	❌	❌

Database objects supported by logical backup in Data Disaster Recovery

Important

If the data source contains Chinese table names or field names, data recovery fails. In this case, join the DingTalk group (ID: 35585947) to provide feedback or submit a ticket.

Database engine	Database object
MySQL MariaDB	Table, index, view, trigger, constraint, primary key, foreign key, stored procedure, and function
PostgreSQL PolarDB for PostgreSQL	Table, index, view, function, stored procedure, constraint, foreign key, sequence, rule, domain, extension, and operator
PolarDB for MySQL PolarDB for PostgreSQL (Compatible with Oracle) PolarDB-X	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.