You can use Data Transmission Service (DTS) to synchronize data between data sources in real time. This feature is suitable for the following scenarios: active geo-redundancy, geo-disaster recovery, zone-disaster recovery, cross-border data synchronization, cloud BI systems, and real-time data warehousing. This topic describes the database types, synchronization types, and synchronization topologies that are supported by DTS.
- The DTS console is upgraded. We recommend that you use the new DTS console because the configuration process is optimized and more data synchronization scenarios are supported.
- In some scenarios, data synchronization can implement part of data migration features and can provide better network stability and additional features. For more information about the differences between the two features, see the "What are the differences between incremental data migration and data synchronization?" section of the FAQ topic.
- DTS can read the instances that are created in an ApsaraDB MyBase dedicated cluster. The topics listed in the following table are also suitable for synchronization scenarios of ApsaraDB MyBase dedicated clusters. For example, you can synchronize data from a self-managed MySQL database to an ApsaraDB MyBase for MySQL instance.
Synchronization types
Synchronization type | Description |
---|---|
Schema synchronization |
DTS synchronizes the schemas of required objects from the source database to the destination database. Tables, views, triggers, and stored procedures can be synchronized. Note Before you configure a data synchronization task, check whether schema synchronization
is supported. If schema synchronization is not supported, you must create a destination
database and tables based on the schemas of required objects in the source database.
|
Full data synchronization |
DTS synchronizes the historical data of required objects from the source database to the destination database. Historical data is the basis for subsequent incremental synchronization. To simplify data synchronization, we recommend that you select both Schema Synchronization and Full Data Synchronization when you configure a data synchronization task. |
Incremental data synchronization | Incremental data synchronization is supported by default. DTS synchronizes incremental data generated in the source database to the destination database in real time. |
Synchronization topologies
For more information, see Synchronization topologies.
Overview of data synchronization scenarios
DTS supports the following data synchronization scenarios. Select a data synchronization solution based on your actual scenario to view the supported database versions, synchronization types, and configuration procedure.
- Synchronize data from a self-managed MySQL database or an ApsaraDB RDS for MySQL instance
- Synchronize data from a PolarDB for MySQL cluster
- Synchronize data from a PolarDB for Oracle cluster
- Migrate data from a PolarDB for PostgreSQL cluster
- Synchronize data from a PolarDB-X instance
- Synchronize data from an Oracle database
- Synchronize data from a self-managed PostgreSQL database or an ApsaraDB RDS for PostgreSQL instance
- Synchronize data from a self-managed SQL Server database or an ApsaraDB RDS for SQL Server instance
- Synchronize data from a self-managed MongoDB database or an ApsaraDB for MongoDB instance
- Synchronize data from a self-managed Redis database or an ApsaraDB for Redis instance
- Synchronize data from a TiDB database
- Synchronize data from a Db2 for LUW database
- Synchronize data from a Db2 for i database
- Synchronize data from a DMS logical database
Databases in this topic, such as a self-managed MySQL or Redis database, can be one of the following types:
- Self-managed database hosted on Elastic Compute Service (ECS)
- Self-managed database connected over Express Connect, VPN Gateway, or Smart Access Gateway
- Self-managed database without a public IP address or port number (connected over Database Gateway)
- Self-managed database connected over Cloud Enterprise Network (CEN)
Synchronize data from a self-managed MySQL database or an ApsaraDB RDS for MySQL instance
Source database | Destination database | Synchronization type | Synchronization topology | References |
---|---|---|---|---|
|
|
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization
Two-way synchronization |
|
PolarDB for MySQL cluster
All versions |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization
Two-way synchronization |
Synchronize data from an ApsaraDB RDS for MySQL instance to a PolarDB for MySQL cluster | |
Oracle database (RAC or non-RAC architecture)
Version 9i, 10g, 11g, 12c, 18c, or 19c |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Available soon | |
PolarDB-X 1.0 or PolarDB-X 2.0 instance |
Full data synchronization Incremental data synchronization Note For a data synchronization task that has a PolarDB-X 2.0 instance configured as the
destination instance, schema synchronization and schema initialization are supported.
However, they are not supported for PolarDB-X 1.0 instances.
|
One-way synchronization | Synchronize data from an ApsaraDB RDS for MySQL instance to a PolarDB-X 2.0 instance | |
AnalyticDB for MySQL cluster Version 2.0 or 3.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from an ApsaraDB RDS for MySQL instance to an AnalyticDB for MySQL
V3.0 cluster Synchronize data from an ApsaraDB RDS for MySQL instance to an AnalyticDB for MySQL cluster |
|
|
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Available soon | |
AnalyticDB for PostgreSQL instance Version 4.3 or 6.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from an ApsaraDB RDS for MySQL instance to an AnalyticDB for PostgreSQL instance | |
Message Queue for Apache Kafka instance Version 0.10.1.0 to 2.x Self-managed Kafka cluster Version 0.10.1.0 to 2.7.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization |
|
|
DataHub project |
Schema synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from an ApsaraDB RDS for MySQL instance to a DataHub instance | |
Elasticsearch cluster Version 5.5, 5.6, 6.3, 6.7, 7.4, or 7.10 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from a self-managed MySQL database hosted on ECS to an Elasticsearch cluster | |
MaxCompute project |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from an ApsaraDB RDS for MySQL instance to a MaxCompute project | |
ApsaraDB for ClickHouse cluster |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization |
N/A |
|
Tablestore instance |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from an ApsaraDB RDS for MySQL instance to a Tablestore instance |
Synchronize data from a PolarDB for MySQL cluster
Source database | Destination database | Synchronization type | Synchronization topology | References |
---|---|---|---|---|
PolarDB for MySQL cluster All versions |
PolarDB for MySQL cluster All versions |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization
Two-way synchronization |
Synchronize data between PolarDB for MySQL clusters |
|
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization
Two-way synchronization |
Synchronize data from a PolarDB for MySQL cluster to an ApsaraDB RDS for MySQL instance | |
PolarDB-X 1.0 or PolarDB-X 2.0 instance
Note
|
Full data synchronization Incremental data synchronization Note For a data synchronization task that has a PolarDB-X 2.0 instance configured as the
destination instance, schema synchronization and schema initialization are supported.
However, they are not supported for PolarDB-X 1.0 instances.
|
One-way synchronization | ||
AnalyticDB for MySQL cluster Version 2.0 or 3.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | ||
AnalyticDB for PostgreSQL instance Version 4.3 or 6.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from a PolarDB for MySQL cluster to an AnalyticDB for PostgreSQL instance | |
Message Queue for Apache Kafka instance Version 0.10.1.0 to 2.x Self-managed Kafka cluster Version 0.10.1.0 to 2.7.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from a PolarDB for MySQL cluster to a self-managed Kafka cluster | |
DataHub project |
Schema synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from an Apsara PolarDB for MySQL cluster to a DataHub instance | |
Elasticsearch cluster Version 5.5, 6.3, 6.7, 7.4, or 7.10 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from a PolarDB for MySQL cluster to an Elasticsearch cluster | |
MaxCompute project |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Available soon | |
Oracle database (RAC or non-RAC architecture)
Version 9i, 10g, 11g, 12c, 18c, or 19c |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Available soon |
Migrate data from a PolarDB for PostgreSQL cluster
Source database | Destination database | Synchronization type | Synchronization topology | References |
---|---|---|---|---|
PolarDB for PostgreSQL cluster Version 11 |
|
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Available soon |
Synchronize data from a PolarDB-X instance
Source database | Destination database | Synchronization type | Synchronization topology | References |
---|---|---|---|---|
PolarDB-X 1.0 instance
Note A database in a PolarDB-X 1.0 instance must be created based on one or more ApsaraDB
RDS for MySQL instances. DTS does not support PolarDB-X 1.0 databases that are created
based on PolarDB for MySQL clusters.
|
PolarDB-X 1.0 instance
Note
|
Full data synchronization Incremental data synchronization Note For a data synchronization task that has a PolarDB-X 1.0 instance configured as the
destination instance, schema synchronization and schema initialization are not supported.
|
One-way synchronization | Synchronize data between PolarDB-X 1.0 instances |
|
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from a PolarDB-X 1.0 instance to an ApsaraDB RDS for MySQL instance | |
PolarDB for MySQL cluster All versions |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from a PolarDB-X 1.0 instance to a PolarDB for MySQL cluster | |
AnalyticDB for MySQL cluster Version 3.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Available soon | |
DataHub project |
Schema synchronization Incremental data synchronization |
One-way synchronization | Available soon | |
PolarDB-X 2.0 instance
Note A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend
that you update the instance to version 5.4.11 or later. For more information about
how to update the version of an instance, see View and update the version of an instance..
|
PolarDB-X 2.0 instance
Note A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend
that you update the instance to version 5.4.11 or later. For more information about
how to update the version of an instance, see View and update the version of an instance..
|
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data between PolarDB-X 2.0 instances |
|
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from a PolarDB-X 2.0 instance to an ApsaraDB RDS for MySQL instance | |
PolarDB for MySQL cluster All versions |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from a PolarDB-X 2.0 instance to a PolarDB for MySQL cluster | |
AnalyticDB for MySQL cluster Version 3.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from a PolarDB-X 2.0 instance to an AnalyticDB for MySQL V3.0 cluster | |
Message Queue for Apache Kafka instance Version 0.10.1.0 to 2.x Self-managed Kafka cluster Version 0.10.1.0 to 2.7.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from a PolarDB-X 2.0 instance to a Message Queue for Apache Kafka instance | |
DataHub project |
Schema synchronization Incremental data synchronization |
One-way synchronization | Available soon | |
MaxCompute project |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Available soon | |
Elasticsearch cluster Version 5.5, 5.6, 6.3, 6.7, 7.4, or 7.10 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from a PolarDB-X 2.0 instance to an Elasticsearch cluster |
Synchronize data from a PolarDB for Oracle cluster
Source database | Destination database | Synchronization type | Synchronization topology | References |
---|---|---|---|---|
PolarDB for Oracle cluster All versions |
PolarDB for Oracle cluster All versions |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Configure one-way data synchronization between PolarDB for Oracle clusters |
Message Queue for Apache Kafka instance Version 0.10.1.0 to 2.x Self-managed Kafka cluster Version 0.10.1.0 to 2.7.0 |
Incremental data synchronization |
One-way synchronization | Synchronize data from a PolarDB for Oracle cluster to a self-managed Kafka cluster |
Synchronize data from an Oracle database
Source database | Destination database | Synchronization type | Synchronization topology | References |
---|---|---|---|---|
Self-managed Oracle database (RAC or non-RAC architecture) Version 9i, 10g, 11g, 12c, 18c, or 19c |
AnalyticDB for PostgreSQL instance Version 4.3 or 6.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from a self-managed Oracle database to an AnalyticDB for PostgreSQL instance |
DataHub project |
Schema synchronization Incremental data synchronization |
One-way synchronization | Available soon | |
PolarDB-X 2.0 instance
Note A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend
that you update the instance to version 5.4.11 or later. For more information about
how to update the version of an instance, see View and update the version of an instance..
|
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Available soon | |
Message Queue for Apache Kafka instance Version 0.10.1.0 to 2.x |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from a self-managed Oracle database to a Message Queue for Apache Kafka instance |
Synchronize data from a self-managed PostgreSQL database or an ApsaraDB RDS for PostgreSQL instance
Source database | Destination database | Synchronization type | Synchronization topology | References |
---|---|---|---|---|
|
|
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization
Two-way synchronization |
|
PolarDB for PostgreSQL cluster Version 11 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Available soon | |
AnalyticDB for PostgreSQL instance Version 4.3 or 6.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | ||
|
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from an ApsaraDB RDS for PostgreSQL instance to an ApsaraDB RDS for MySQL instance |
Synchronize data from a self-managed SQL Server database or an ApsaraDB RDS for SQL Server instance
Source database | Destination database | Synchronization type | Synchronization topology | References |
---|---|---|---|---|
|
|
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data between ApsaraDB RDS for SQL Server instances |
|
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from an ApsaraDB RDS for SQL Server instance to an ApsaraDB RDS for MySQL instance | |
PolarDB for MySQL cluster All versions |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from a self-managed SQL Server database to a PolarDB for MySQL cluster | |
AnalyticDB for MySQL cluster
Version 3.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from an ApsaraDB RDS for SQL Server instance to an AnalyticDB for MySQL V3.0 cluster | |
AnalyticDB for PostgreSQL instance Version 4.3 or 6.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from a self-managed SQL Server database to an AnalyticDB for PostgreSQL instance | |
DataHub project |
Schema synchronization Incremental data synchronization |
One-way synchronization | Available soon |
Synchronize data from a self-managed MongoDB database or an ApsaraDB for MongoDB instance
Source database | Destination database | Synchronization type | Synchronization topology | References |
---|---|---|---|---|
|
|
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from an ApsaraDB for MongoDB instance (replica set architecture) to another ApsaraDB for MongoDB instance (replica set architecture or sharded cluster architecture) |
ApsaraDB for MongoDB instance (sharded cluster architecture)
Version 3.4, 4.0, 4.2, or 4.4 |
ApsaraDB for MongoDB instance (sharded cluster architecture)
Version 3.4, 4.0, 4.2, or 4.4 |
Schema synchronization Full data synchronization Incremental data synchronization |
Two-way synchronization |
Configure two-way data synchronization between ApsaraDB for MongoDB instances (sharded cluster architecture) |
Synchronize data from a self-managed Redis database or an ApsaraDB for Redis instance
- Redis is a NoSQL database that does not require schema synchronization.
- When the source and destination instances are ApsaraDB for Redis instances, DTS supports instances that use a master-replica architecture and cloud disks but not instances that use a cluster architecture and cloud disks.
- In this scenario, a two-way data synchronization task supports only ApsaraDB for Redis Enhanced Edition (Tair 5.0) instances.
- If the source database is a self-managed Redis instance or an ApsaraDB for Redis Community Edition instance, full data synchronization and incremental data synchronization are supported and displayed as incremental data synchronization.
Source database | Destination database | Synchronization type | Synchronization topology | References |
---|---|---|---|---|
|
|
Full data synchronization Incremental data synchronization |
One-way synchronization Two-way synchronization |
|
Synchronize data from a TiDB database
Source database | Destination database | Synchronization type | Synchronization topology | References |
---|---|---|---|---|
TiDB database | AnalyticDB for MySQL cluster
Version 2.0 or 3.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization |
Synchronize data from a self-managed TiDB database to an AnalyticDB for MySQL cluster |
Synchronize data from a Db2 for LUW database
Source database | Destination database | Synchronization type | Synchronization topology | References |
---|---|---|---|---|
Db2 for LUW database
Version 9.5, 9.7, 10.1, 10.5, 11.1, or 11.5 |
|
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization |
Available soon |
AnalyticDB for MySQL cluster Version 3.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization |
Available soon | |
PolarDB for MySQL cluster All versions |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization |
Available soon | |
PolarDB-X 2.0 instance
Note A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend
that you update the instance to version 5.4.11 or later. For more information about
how to update the version of an instance, see View and update the version of an instance..
|
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization |
Synchronize data from a Db2 for LUW database to a PolarDB-X 2.0 instance | |
AnalyticDB for PostgreSQL instance Version 4.3 or 6.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization |
Available soon | |
Message Queue for Apache Kafka instance Version 0.10.1.0 to 2.x Self-managed Kafka cluster Version 0.10.1.0 to 2.7.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization |
Available soon |
Synchronize data from a Db2 for i database
Source database | Destination database | Synchronization type | Synchronization topology | References |
---|---|---|---|---|
Db2 for i database
Version 7.3 or 7.4 |
|
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization |
Available soon |
Synchronize data from a DMS logical database
Source database | Destination database | Synchronization type | Synchronization topology | References |
---|---|---|---|---|
DMS logical database
Note A logical database in Data Management (DMS) must be created based on the database
shards of multiple PolarDB for MySQL clusters.
|
AnalyticDB for MySQL cluster Version 3.0 |
Schema synchronization Full data synchronization Incremental data synchronization |
One-way synchronization | Synchronize data from a DMS logical database to an AnalyticDB for MySQL V3.0 cluster |