You can use Data Transmission Service (DTS) to synchronize data between data sources in real time. This feature applies to 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.

Note
  • The DTS console is upgraded. We recommend that you use the DTS console of the new version because the configuration process is optimized and multiple data synchronization scenarios are supported.
  • In some scenarios, data synchronization can achieve part of data migration features and can provide better network stability and additional features. For more information about the differences between data migration and data synchronization, see FAQ.
  • DTS can read the instances that are created in an ApsaraDB for MyBase cluster. The topics listed in the following table are also applicable to synchronization scenarios for ApsaraDB for MyBase clusters. For example, you can synchronize data from a self-managed MySQL database to an ApsaraDB RDS for MySQL instance that is created in an ApsaraDB for MyBase cluster.

Synchronization types

Synchronization type Description
Schema synchronization

DTS synchronizes the schemas of the 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 the required objects in the source database.
Full data synchronization

DTS synchronizes historical data of the 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 the data synchronization solution based on your actual scenario to view the supported database versions, synchronization types, and configuration procedure.

Note

A self-managed MySQL or Redis database can be one of the following types:

  • Self-managed database that is hosted on Elastic Compute Service (ECS)
  • Self-managed database that is connected over Express Connect, VPN Gateway, or Smart Access Gateway
  • Self-managed database that has no public IP address or port number and is connected over Database Gateway
  • Self-managed database that is connected over Cloud Enterprise Network

Synchronize data from a self-managed MySQL database or an ApsaraDB RDS for MySQL instance

Source database Destination database Synchronization type Synchronization topology Reference
  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • RDS MySQL

    All versions

  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • RDS MySQL

    All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Two-way synchronization

New version of the DTS console:
PolarDB MySQL

All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Two-way synchronization

New version of the DTS console: Synchronize data from an ApsaraDB RDS for MySQL instance to a PolarDB for MySQL cluster
PolarDB-X 1.0 and PolarDB-X
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 databases that are created based on PolarDB for MySQL clusters.
  • A database in a PolarDB-X instance must be compatible with MySQL V5.7. We recommend that you update the instance to V5.4.11 or later. For more information about how to update the version of an instance, see Update the version of an instance.

Full data synchronization

Incremental data synchronization

One-way synchronization New version of the DTS console: Synchronize data from an ApsaraDB RDS for MySQL instance to a PolarDB-X V2.0 instance
Note Data synchronization to a PolarDB-X instance is not supported in the DTS console of the new version. You can configure a data synchronization task for this scenario only in the DTS console of the previous version.

AnalyticDB for MySQL

Version 2.0 or 3.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization New version of the DTS console: Synchronize data from an ApsaraDB RDS for MySQL instance to an AnalyticDB for MySQL V3.0 cluster
Note Data synchronization to an AnalyticDB for MySQL V2.0 cluster is not supported in the DTS console of the new version. You can configure a data synchronization task for this scenario only in the DTS console of the previous version.

AnalyticDB for PostgreSQL

Version 4.3 or 6.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization New version of the DTS console: Synchronize data from an ApsaraDB RDS for MySQL instance to an AnalyticDB for PostgreSQL instance

Message Queue for Apache Kafka

Versions 0.10.1.0 to 2.x

Self-managed Kafka cluster

Versions 0.10.1.0 to 2.7.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization New version of the DTS console: Available soon

DataHub

All versions

Schema synchronization

Incremental data synchronization

One-way synchronization New version of the DTS console: Available soon

Elasticsearch

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 New version of the DTS console: Available soon

Synchronize data from a PolarDB for MySQL cluster

Source database Destination database Synchronization type Synchronization topology Reference

PolarDB MySQL

All versions

PolarDB MySQL

All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Two-way synchronization

New version of the DTS console: Synchronize data between PolarDB for MySQL clusters
  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • RDS MySQL

    All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Two-way synchronization

New version of the DTS console: Synchronize data from a PolarDB for MySQL cluster to an ApsaraDB RDS for MySQL instance
PolarDB-X 1.0 and PolarDB-X
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 databases that are created based on PolarDB for MySQL clusters.
  • A database in a PolarDB-X instance must be compatible with MySQL V5.7. We recommend that you update the instance to V5.4.11 or later. For more information about how to update the version of an instance, see Update the version of an instance.

Full data synchronization

Incremental data synchronization

One-way synchronization New version of the DTS console: Synchronize data from a PolarDB for MySQL cluster to a PolarDB-X V2.0 instance
Note Data synchronization to a PolarDB-X 1.0 instance is not supported in the DTS console of the new version. You can configure a data synchronization task for this scenario only in the DTS console of the previous version.

AnalyticDB for MySQL

Version 2.0 or 3.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization New version of the DTS console: Synchronize data from a PolarDB for MySQL cluster to an AnalyticDB for MySQL V3.0 cluster
Note Data synchronization to an AnalyticDB for MySQL V2.0 cluster is not supported in the DTS console of the new version. You can configure a data synchronization task for this scenario only in the DTS console of the previous version.

Message Queue for Apache Kafka

Versions 0.10.1.0 to 2.x

Self-managed Kafka cluster

Versions 0.10.1.0 to 2.7.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization New version of the DTS console: Available soon

DataHub

All versions

Schema synchronization

Incremental data synchronization

One-way synchronization New version of the DTS console: Available soon

Synchronize data from a PolarDB-X instance

  • Perform the following data synchronization tasks in the DTS console of the new version.
    Source database Destination database Synchronization type Synchronization topology Reference
    PolarDB-X 1.0
    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 databases that are created based on PolarDB for MySQL clusters.
    PolarDB-X 1.0
    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 databases that are created based on PolarDB for MySQL clusters.

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization Available soon
    • Self-managed MySQL database

      Version 5.1, 5.5, 5.6, 5.7, or 8.0

    • RDS MySQL

      All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization Synchronize data from a DRDS instance to an ApsaraDB RDS for MySQL instance

    PolarDB MySQL

    All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization Available soon

    AnalyticDB for MySQL

    Version 3.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization Available soon

    DataHub

    All versions

    Schema synchronization

    Incremental data synchronization

    One-way synchronization Available soon
    PolarDB-X 2.0
    Note A database in a PolarDB-X instance must be compatible with MySQL V5.7. We recommend that you update the instance to V5.4.11 or later. For more information about how to update the version of an instance, see Update the version of an instance.
    PolarDB-X 2.0
    Note A database in a PolarDB-X instance must be compatible with MySQL V5.7. We recommend that you update the instance to V5.4.11 or later. For more information about how to update the version of an instance, see Update the version of an instance.

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization Available soon
    • Self-managed MySQL database

      Version 5.1, 5.5, 5.6, 5.7, or 8.0

    • RDS MySQL

      All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization Available soon

    PolarDB MySQL

    All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization Available soon

    AnalyticDB for MySQL

    Version 3.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization Available soon

    Message Queue for Apache Kafka

    Versions 0.10.1.0 to 2.x

    Self-managed Kafka cluster

    Versions 0.10.1.0 to 2.7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization Available soon

    DataHub

    All versions

    Schema synchronization

    Incremental data synchronization

    One-way synchronization Available soon

    Elasticsearch

    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 Available soon

Synchronize data from a PolarDB for Oracle cluster

Source database Destination database Synchronization type Synchronization topology Reference

PolarDB for Oracle

All versions

PolarDB for Oracle

All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization New version of the DTS console: Available soon

Message Queue for Apache Kafka

Versions 0.10.1.0 to 2.x

Self-managed Kafka cluster

Versions 0.10.1.0 to 2.7.0

Incremental data synchronization

One-way synchronization New version of the DTS console: Available soon

Synchronize data from an Oracle database

Note You can configure a data synchronization task for this scenario only in the DTS console of the new version.
Source database Destination database Synchronization type Synchronization topology Reference

Self-managed Oracle database (RAC or non-RAC architecture)

Version 9i, 10g, 11g, 12c, 18c, or 19c

AnalyticDB for PostgreSQL

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

All versions

Schema synchronization

Incremental data synchronization

One-way synchronization Available soon
PolarDB-X 2.0
Note A database in a PolarDB-X instance must be compatible with MySQL V5.7. We recommend that you update the instance to V5.4.11 or later. For more information about how to update the version of an instance, see Update the version of an instance.

Full data synchronization

Incremental data synchronization

One-way synchronization Available soon
Note You can configure a data synchronization task for this scenario only in the DTS console of the new version.

Synchronize data from a self-managed PostgreSQL database or an ApsaraDB RDS for PostgreSQL instance

Source database Destination database Synchronization type Synchronization topology Reference
  • Self-managed PostgreSQL database

    Version 9.5.x, 9.6.x, 10.x, 11.x, 12.x, or 13.x

  • RDS PostgreSQL

    Version 9.4, 10, 11, 12, or 13

  • Self-managed PostgreSQL database

    Version 9.5.x, 9.6.x, 10.x, 11.x, 12.x, or 13.x

  • RDS PostgreSQL

    Version 9.4, 10, 11, 12, or 13

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Two-way synchronization

Note You can configure a two-way data synchronization task for this scenario only in the DTS console of the new version.

PolarDB PostgreSQL

Version 11

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization Available soon
Note You can configure a data synchronization task for this scenario only in the DTS console of the new version.

AnalyticDB for PostgreSQL

Version 4.3 or 6.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization New version of the DTS console: Available soon
  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • RDS MySQL

    All versions

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
Note You can configure a data synchronization task for this scenario only in the DTS console of the new version.

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 Reference
  • Self-managed SQL Server database
    2008 Version 2008R2, 2012, 2014, 2016, or 2017
    Note

    The self-managed SQL Server database must be of the Enterprise, Developer, or Enterprise Evaluation edition.

  • RDS SQL Server

    Version 2012, 2014, 2016, or 2017

  • Self-managed SQL Server database

    2008 Version 2008R2, 2012, 2014, 2016, or 2017

    The self-managed SQL Server database must be of the Enterprise, Developer, or Enterprise Evaluation edition.

    Note

    The self-managed SQL Server database must be of the Enterprise, Developer, or Enterprise Evaluation edition.

  • RDS SQL Server

    2008 Version 2008R2, 2012, 2014, 2016, or 2017

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization Synchronize data between ApsaraDB RDS for SQL Server instances
Note You can configure a data synchronization task for this scenario only in the DTS console of the new version.
  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • RDS MySQL

    All versions

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
Note You can configure a data synchronization task for this scenario only in the DTS console of the new version.

PolarDB MySQL

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
Note You can configure a data synchronization task for this scenario only in the DTS console of the new version.
AnalyticDB for MySQL

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 cluster V3.0
Note You can configure a data synchronization task for this scenario only in the DTS console of the new version.

AnalyticDB for PostgreSQL

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

Synchronize data from a self-managed MongoDB database or an ApsaraDB for MongoDB instance

Note You can configure a data synchronization task for this scenario only in the DTS console of the new version.
Source database Destination database Synchronization type Synchronization topology Reference
  • Self-managed MongoDB database (replica set architecture)

    Versions 2.8 to 4.4

  • ApsaraDB for MongoDB (replica set architecture)

    Version 3.4, 4.0, 4.2, or 4.4

  • Self-managed MongoDB database (replica set or sharded cluster architecture)

    Versions 2.8 to 4.4

  • ApsaraDB for MongoDB (replica set or sharded cluster architecture)

    Version 3.4, 4.0, 4.2, or 4.4

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 (sharded cluster architecture)

Version 3.4, 4.0, 4.2, or 4.4

ApsaraDB for MongoDB (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

Note
  • Redis is a NoSQL database that does not require schema synchronization.
  • When the source database and the destination database belong to an ApsaraDB for Redis instance, DTS supports databases of replica set architecture on a cloud disk but not databases of cluster architecture on a cloud disk.
  • In this scenario, a two-way data synchronization task supports only ApsaraDB for Redis Enhanced Edition (Tair 5.0) instances.
  • Full data synchronization is supported only when the source database and the destination database belong to an ApsaraDB for Redis Enhanced Edition (Tair 5.0) instance.
Source database Destination database Synchronization type Synchronization topology Reference
  • Self-managed Redis database (standalone or cluster architecture)

    Version 2.8, 3.0, 3.2, 4.0, 5.0, or 6.0

  • ApsaraDB for Redis Community Edition instance (cluster, standard, or read/write splitting architecture)

    Version 4.0, 5.0, or 6.0

  • ApsaraDB for Redis Enhanced Edition instance (cluster, standard, or read/write splitting architecture)

    Version 5.0

  • Self-managed Redis database (standalone or cluster architecture)

    Version 2.8, 3.0, 3.2, 4.0, 5.0, or 6.0

  • ApsaraDB for Redis Community Edition instance (cluster, standard, or read/write splitting architecture)

    Version 4.0, 5.0, or 6.0

  • ApsaraDB for Redis Enhanced Edition instance (cluster, standard, or read/write splitting architecture)

    Version 5.0

Full data synchronization

Incremental data synchronization

One-way synchronization

Two-way synchronization

New version of the DTS console: Configure one-way data synchronization between ApsaraDB for Redis instances across Alibaba Cloud accounts

Synchronize data from a DB2 for LUW database

Source database Destination database Synchronization type Synchronization topology Reference
DB2 for LUW

Version 9.5, 9.7, 10.1, 10.5, 11.1, or 11.5

  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • RDS MySQL

    All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Available soon
PolarDB-X 2.0
Note A database in a PolarDB-X instance must be compatible with MySQL V5.7. We recommend that you update the instance to V5.4.11 or later. For more information about how to update the version of an instance, see Update the version of an instance.

Full data synchronization

Incremental data synchronization

One-way synchronization

Available soon

AnalyticDB for PostgreSQL

Version 4.3 or 6.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Available soon

Message Queue for Apache Kafka

Versions 0.10.1.0 to 2.x

Self-managed Kafka cluster

Versions 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 Reference
DB2 for i

Version 7.3 or 7.4

  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • RDS MySQL

    All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Available soon

Synchronize data from a DMS logical database

Note You can configure a data synchronization task for this scenario only in the DTS console of the new version in the China (Shanghai) and Singapore (Singapore) regions.
Source database Destination database Synchronization type Synchronization topology Reference
DMS logical database
Note A logical database in DMS must be created based on the database shards of multiple PolarDB for MySQL instances.

AnalyticDB for MySQL

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