All Products
Search

This Product

    Data Transmission Service:Overview of data synchronization solutions

    Document Center

    Data Transmission Service:Overview of data synchronization solutions

    Last Updated:Dec 13, 2025

    The data synchronization feature of Data Transmission Service (DTS) provides real-time data synchronization between different data sources. This feature captures data changes from a source database and synchronizes them to a destination database in real time. It is widely used for scenarios such as version upgrades, data sharding or scaling, active geo-redundancy, geo-disaster recovery, cross-border data synchronization, query and report offloading, and building real-time data warehouses. DTS eliminates the complexity, errors, and performance challenges of manually managing data streams. This lets you focus on your business instead of maintaining data pipelines.

    Core concepts

    Synchronization types

    A DTS sync task can include three optional synchronization types to meet different business needs.

    Recommendations

    • First-time synchronization: For an initial synchronization, select Schema Synchronization, Full Data Synchronization, and Incremental Data Synchronization to perform a complete data synchronization from the beginning.

    • Existing baseline data: If you have already populated the destination database using other methods, select only Incremental Data Synchronization. Ensure that the data is consistent between the source and destination databases. This is a complex operation that requires careful evaluation.

    Synchronization type

    Description

    Schema Synchronization

    Purpose: Automatically create a schema in the destination database that matches the source database.

    DTS synchronizes the schema definitions of the objects to be synchronized from the source database to the destination database. These objects can include tables, views, triggers, stored procedures, and indexes. If the destination database is empty, selecting this option saves you from creating the schema manually.

    Important

    Some synchronization links do not support schema synchronization. Before you configure a data synchronization task, you must create the corresponding databases, tables, and views in the destination database based on the schema definitions of the objects in the source database.

    Full Data Synchronization

    Purpose: Migrate historical data from the source database.

    DTS copies all historical data of the objects to be synchronized from the source database to the destination database. This process establishes a data baseline for the subsequent Incremental Data Synchronization.

    Incremental Data Synchronization

    Purpose: Continuously keep the source and destination databases synchronized.

    DTS continuously captures incremental change statements for the objects to be synchronized from the source database, such as from the binary log of a MySQL database. DTS then converts these statements as needed for the destination database and executes them to synchronize incremental data in real time.

    Note

    Incremental Data Synchronization runs continuously and does not end automatically. To stop it, you must manually end the DTS instance or release the DTS instance.

    Synchronization topology

    DTS supports two core data synchronization topologies. For more information, see Introduction to data synchronization topologies.

    Synchronization topology

    Description

    Scenarios

    One-way Synchronization

    Data flows one-way from a source database to one or more destination databases.

    Data sharding or scaling, query and report offloading, and building real-time data warehouses.

    Two-way Synchronization

    Data flows bidirectionally between two databases. Changes in either database are synchronized to the other.

    Active geo-redundancy, geo-disaster recovery, and cross-border synchronization.

    Important

    Two-way Synchronization consists of a forward sync task and a reverse sync task. When you configure or reset a two-way sync task, DTS imposes strict limits to prevent data loops:

    • Initialization rules: A unidirectional task (for example, from A to B) can perform Schema Synchronization and Full Data Synchronization. The task in the reverse direction (from B to A) can only be configured for Incremental Data Synchronization.

    • Avoid data loops: Data that is synchronized from A to B is not synchronized back to A.

    • Reset risks: When you need to reset and reconfigure a single task, such as the forward task, we recommend that you reset and reconfigure both the forward and reverse tasks. Otherwise, when the forward task performs Schema Synchronization and Full Data Synchronization, the system automatically removes the synchronized objects configured in the reverse task. This can cause the Two-way Synchronization task to produce unexpected results.

    Limits

    Before you begin, make sure that your environment and business scenario meet the following requirements.

    General limits

    Limit

    Description

    Network configuration

    • Source database network bandwidth: Must be 100 Mb/s or higher.

    • Network latency (RTT): To ensure synchronization performance, the network round-trip time (RTT) between the source database and the DTS service should be less than 2 ms. For cross-region or cross-border deployments, the physical distance can cause the RTT to exceed this limit, leading to synchronization latency. For example, this can happen if a database in the Singapore region connects to DTS through a VPN in the Hong Kong (China) region.

    Workload

    • Log volume: DTS performs incremental synchronization by pulling database logs. To ensure stability, we recommend that the peak log volume of the source instance is less than 1 TB per day, the average hourly log volume is less than 50 GB, and the peak traffic is less than 15 MB/s.

      Important

      DTS pulls logs for the entire database by default, not just for the synchronized objects. This means that even if you synchronize only one small table, frequent writes to other large, unrelated tables in the database (which generate a large volume of logs) can still cause latency in the sync task. Therefore, fully consider this impact during planning.

    • Batch updates: Performing batch data updates or large-scale changes to large objects (such as CLOB, BLOB, and LONG types) can cause task latency. We recommend performing such operations in batches or avoiding them if possible.

    • High-frequency DDL: Avoid frequent Data Definition Language (DDL) operations. We recommend no more than 10 DDL statements per second. Otherwise, task latency may occur.

    • Tables without primary keys: Avoid frequent DELETE or UPDATE operations on tables without primary keys. Otherwise, task latency may occur.

    • Large transactions: Avoid executing large transactions that generate more than 100 GB of logs in a single transaction. Otherwise, the task may fail.

    Other limits

    • Cross-account synchronization: Whether you can create cross-account sync tasks depends on the database type and connection type. For more information, see Configure a cross-account task.

    • Cross-border data synchronization: This feature is not enabled by default. You must first request permission for cross-border data synchronization and receive approval before you can use this feature.

      Note

      • If your synchronization or migration task involves cross-border and cross-region operations, ensure that your task bandwidth does not exceed 100 Mbit/s. If your bandwidth exceeds 100 Mbit/s, you must use CEN to configure cross-region network bandwidth before you configure the DTS task.

      • A cross-region or cross-border task is a task in which the source and destination databases are in different regions. For example, the source database is an RDS instance in the Singapore region and the destination database is an RDS instance in the China (Hangzhou) region.

    FAQ

    What is the difference between data migration and data synchronization?

    • Different purposes

      • Data migration is a one-time process of moving data from a source database to a destination database. After the migration, the source database is typically decommissioned.

      • Data synchronization is used to establish long-term, continuous data replication between two data sources to keep them dynamically consistent.

    • Different features

      • The core goal of data migration is to ensure that all data is consistent after the migration is complete. The task stops after the process is finished.

      • Data synchronization is a long-running task that provides more complex features, such as two-way synchronization and conflict resolution.

    • Recommendations

    Can I add new tables to a running sync task?

    Yes, you can. For data synchronization tasks, you can modify the synchronized objects to add new databases or tables while the task is running. However, this operation is not supported for data migration tasks.

    How can I merge data from multiple source databases into a single destination database, or synchronize a table from a source database to an existing table with a different name in the destination database?

    You can achieve this by configuring schema, table, and column name mapping. When you configure objects for synchronization, DTS lets you rename them in the destination database. For example, you can synchronize the orders table from source database db_A and the orders table from source database db_B to the destination database db_Z, and map them to orders_from_A and orders_from_B respectively.

    Does DTS support RDS Serverless instances?

    • Serverless ApsaraDB RDS for MySQL and Serverless PolarDB for MySQL: Supported as both source and destination databases.

    • Serverless ApsaraDB RDS for PostgreSQL: Currently supported only as a destination database, not as a source database.

    Does DTS support instances in ApsaraDB for MyBase dedicated clusters?

    Yes. Database instances created in an ApsaraDB for MyBase dedicated cluster can be used as a DTS source or destination by setting the Access Method to Alibaba Cloud Instance. For example, to configure data synchronization from a self-managed MySQL database to a MySQL instance in an ApsaraDB for MyBase dedicated cluster, you can follow the instructions in Synchronize data from a self-managed MySQL database to an RDS for MySQL instance.

    What is a self-managed database?

    When you configure a DTS task, a database instance is considered self-managed if its Access Method is not set to Alibaba Cloud Instance. These include databases from third-party cloud providers, on-premises databases, and databases deployed on ECS instances.

    Appendix: Synchronization link support matrix

    The following tables summarize the database synchronization links that DTS supports. Before you start, you can check whether your source and destination database combination is supported. In the On This Page section on the right, you can click the synchronization solution for your source database to navigate to the corresponding section and view the supported versions, synchronization types, and configuration steps.

    Source is a self-managed MySQL or RDS for MySQL database

    Important

    • The database in PolarDB-X 1.0 must be created using RDS for MySQL. DTS does not support databases created using PolarDB for MySQL.

    • When PolarDB-X 1.0 is the destination, schema synchronization and initial schema synchronization are not supported. When PolarDB-X 2.0 is the destination, both are supported.

    • We recommend that you use PolarDB-X 2.0 instances that are version 5.4.11 or later. For information about how to upgrade an instance, see View and upgrade the instance version.

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

    • Self-managed MySQL

      5.1, 5.5, 5.6, 5.7, 8.0

    • RDS for MySQL

      All versions

    • Self-managed MySQL

      5.1, 5.5, 5.6, 5.7, 8.0

    • RDS for MySQL

      All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Two-way synchronization

    PolarDB for MySQL

    All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Two-way synchronization

    Oracle (RAC or non-RAC architecture)

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

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MySQL instance to a self-managed Oracle database

    PolarDB-X 1.0

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MySQL instance to a PolarDB-X 1.0 instance

    PolarDB-X 2.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MySQL instance to a PolarDB-X 2.0 instance

    AnalyticDB for MySQL

    2.0, 3.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    • Self-managed PostgreSQL

      9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x

    • RDS for PostgreSQL

      9.4, 10, 11, 12, 13, 14, 15, 16, 17

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MySQL instance to an RDS for PostgreSQL instance

    AnalyticDB for PostgreSQL

    4.3, 6.0, 7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MySQL instance to an AnalyticDB for PostgreSQL instance

    • ApsaraMQ for Kafka

      0.10.1.0 to 2.x

    • Self-managed Kafka

      0.10.1.0 to 2.7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MySQL instance to an ApsaraMQ for Kafka instance

    ApsaraDB for ClickHouse cluster

    20.8 and later

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MySQL instance to a ClickHouse cluster

    DataHub

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MySQL instance to a DataHub project

    Elasticsearch

    5.5, 5.6, 6.x, 7.x, 8.x

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MySQL instance to an Elasticsearch cluster

    MaxCompute

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MySQL instance to a MaxCompute project

    ApsaraDB for Tair (Redis Compatible) instance (cluster, standard, or read/write splitting architecture)

    4.0, 5.0, 6.0, 7.0

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MySQL instance to a Tair or Redis instance

    Tablestore

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MySQL instance to a Tablestore instance

    Function Compute (FC)

    2.0

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MySQL instance to Function Compute

    ApsaraDB for SelectDB

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MySQL instance to an ApsaraDB for SelectDB instance

    Lindorm

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MySQL instance to a Lindorm instance

    Doris

    1.2 and later

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MySQL instance to a self-managed Doris cluster

    ApsaraMQ for RocketMQ

    4.x and 5.x series

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MySQL instance to an ApsaraMQ for RocketMQ instance

    Source is a PolarDB for MySQL cluster

    Important

    • The database in PolarDB-X 1.0 must be created using RDS for MySQL. DTS does not support databases created using PolarDB for MySQL.

    • When PolarDB-X 1.0 is the destination, schema synchronization and initial schema synchronization are not supported. When PolarDB-X 2.0 is the destination, both are supported.

    • We recommend that you use PolarDB-X 2.0 instances that are version 5.4.11 or later. For information about how to upgrade an instance, see View and upgrade the instance version.

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

    PolarDB for MySQL

    All versions

    PolarDB for MySQL

    All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Two-way synchronization

    • Self-managed MySQL

      5.1, 5.5, 5.6, 5.7, 8.0

    • RDS for MySQL

      All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Two-way synchronization

    Synchronize data from a PolarDB for MySQL cluster to an RDS for MySQL instance

    PolarDB-X 1.0

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB for MySQL cluster to a PolarDB-X 1.0 instance

    PolarDB-X 2.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB for MySQL cluster to a PolarDB-X 2.0 instance

    AnalyticDB for MySQL

    2.0, 3.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    AnalyticDB for PostgreSQL

    4.3, 6.0, 7.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

    • ApsaraMQ for Kafka

      0.10.1.0 to 2.x

    • Self-managed Kafka

      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 an ApsaraMQ for Kafka instance

    DataHub

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB for MySQL cluster to a DataHub project

    ApsaraDB for ClickHouse cluster

    20.8 and later

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB for MySQL cluster to a ClickHouse cluster

    Elasticsearch

    5.5, 5.6, 6.x, 7.x, 8.x

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB for MySQL cluster to an Elasticsearch cluster

    MaxCompute

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB for MySQL cluster to a MaxCompute project

    Oracle (RAC or non-RAC architecture)

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

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB for MySQL cluster to a self-managed Oracle database

    ApsaraDB for SelectDB

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB for MySQL cluster to an ApsaraDB for SelectDB instance

    Doris

    1.2 and later

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB for MySQL cluster to a self-managed Doris cluster

    Lindorm

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB for MySQL cluster to a Lindorm instance

    Source is a PolarDB for PostgreSQL cluster

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

    PolarDB for PostgreSQL

    11, 14, 15, 16, 17

    • Self-managed PostgreSQL

      9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x

    • RDS for PostgreSQL

      9.4, 10, 11, 12, 13, 14, 15, 16, 17

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Two-way synchronization

    PolarDB for PostgreSQL

    11, 14, 15, 16, 17

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Two-way synchronization

    AnalyticDB for PostgreSQL

    4.3, 6.0, 7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB for PostgreSQL cluster to an AnalyticDB for PostgreSQL instance

    ApsaraDB for SelectDB

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB for PostgreSQL cluster to an ApsaraDB for SelectDB instance

    Source is a PolarDB-X instance

    Important

    • The database in PolarDB-X 1.0 must be created using RDS for MySQL. DTS does not support databases created using PolarDB for MySQL.

    • When PolarDB-X 1.0 is the destination, schema synchronization and initial schema synchronization are not supported. When PolarDB-X 2.0 is the destination, both are supported.

    • We recommend that you use PolarDB-X 2.0 instances that are version 5.4.11 or later. For information about how to upgrade an instance, see View and upgrade the instance version.

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

    PolarDB-X 1.0

    PolarDB-X 1.0

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data between PolarDB-X 1.0 instances

    • Self-managed MySQL

      5.1, 5.5, 5.6, 5.7, 8.0

    • RDS for MySQL

      All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB-X 1.0 instance to an RDS for MySQL instance

    PolarDB for MySQL

    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

    3.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB-X 1.0 instance to an AnalyticDB for MySQL 3.0 cluster

    DataHub

    Schema synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB-X 1.0 instance to a DataHub project

    AnalyticDB for PostgreSQL

    4.3, 6.0, 7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB-X 1.0 instance to an AnalyticDB for PostgreSQL instance

    • ApsaraMQ for Kafka

      0.10.1.0 to 2.x

    • Self-managed Kafka

      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 1.0 instance to an ApsaraMQ for Kafka instance

    Elasticsearch

    5.5, 5.6, 6.x, 7.x, 8.x

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB-X 1.0 instance to an Elasticsearch cluster

    PolarDB-X 2.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB-X 1.0 instance to a PolarDB-X 2.0 instance

    PolarDB-X 2.0

    PolarDB-X 2.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Two-way synchronization

    • Self-managed MySQL

      5.1, 5.5, 5.6, 5.7, 8.0

    • RDS for MySQL

      All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB-X 2.0 instance to an RDS for MySQL instance

    PolarDB for MySQL

    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

    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 3.0 cluster

    • ApsaraMQ for Kafka

      0.10.1.0 to 2.x

    • Self-managed Kafka

      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 an ApsaraMQ for Kafka instance

    DataHub

    Schema synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB-X 2.0 instance to a DataHub project

    MaxCompute

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB-X 2.0 instance to a MaxCompute project

    AnalyticDB for PostgreSQL

    4.3, 6.0, 7.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 PostgreSQL instance

    Elasticsearch

    5.5, 5.6, 6.x, 7.x, 8.x

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB-X 2.0 instance to an Elasticsearch cluster

    Oracle (RAC or non-RAC architecture)

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

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB-X 2.0 instance to a self-managed Oracle database

    Tablestore

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB-X 2.0 instance to a Tablestore instance

    PolarDB-X 1.0

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB-X 2.0 instance to a PolarDB-X 1.0 instance

    ApsaraDB for SelectDB

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB-X 2.0 instance to an ApsaraDB for SelectDB instance

    Source is a PolarDB for PostgreSQL (Compatible with Oracle) cluster

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

    PolarDB for PostgreSQL (Compatible with Oracle)

    All versions

    PolarDB for PostgreSQL (Compatible with Oracle)

    All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Two-way synchronization

    • ApsaraMQ for Kafka

      0.10.1.0 to 2.x

    • Self-managed Kafka

      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 PostgreSQL (Compatible with Oracle) cluster to an ApsaraMQ for Kafka instance

    AnalyticDB for MySQL

    3.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a PolarDB for PostgreSQL (Compatible with Oracle) cluster to an AnalyticDB for MySQL 3.0 cluster

    Source is an Oracle database

    Important

    • Configuration is supported only in the new console.

    • We recommend that you use PolarDB-X 2.0 instances that are version 5.4.11 or later. For information about how to upgrade an instance, see View and upgrade the instance version.

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

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

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

    AnalyticDB for PostgreSQL

    4.3, 6.0, 7.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

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a self-managed Oracle database to a DataHub project

    PolarDB-X 2.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a self-managed Oracle database to a PolarDB-X 2.0 instance

    PolarDB for MySQL

    All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a self-managed Oracle database to a PolarDB for MySQL cluster

    MaxCompute

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a self-managed Oracle database to a MaxCompute project

    PolarDB for PostgreSQL (Compatible with Oracle)

    All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a self-managed Oracle database to a PolarDB for PostgreSQL (Compatible with Oracle) cluster

    ApsaraMQ for Kafka

    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 an ApsaraMQ for Kafka instance

    Source is a self-managed PostgreSQL or RDS for PostgreSQL database

    Important

    Serverless ApsaraDB RDS for PostgreSQL instances are not supported as the source database, but are supported as the destination database.

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

    • Self-managed PostgreSQL

      9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x

    • RDS for PostgreSQL

      9.4, 10, 11, 12, 13, 14, 15, 16, 17

    • Self-managed PostgreSQL

      9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x

    • RDS for PostgreSQL

      9.4, 10, 11, 12, 13, 14, 15, 16, 17

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Two-way synchronization

    PolarDB for PostgreSQL

    11, 14, 15, 16, 17

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Two-way synchronization

    AnalyticDB for PostgreSQL

    4.3, 6.0, 7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for PostgreSQL instance to an AnalyticDB for PostgreSQL instance

    • Self-managed MySQL

      5.1, 5.5, 5.6, 5.7, 8.0

    • RDS for MySQL

      All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for PostgreSQL instance to an RDS for MySQL instance

    PolarDB for PostgreSQL (Compatible with Oracle)

    All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a self-managed PostgreSQL database to a PolarDB for PostgreSQL (Compatible with Oracle) cluster

    ApsaraDB for SelectDB

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for PostgreSQL instance to an ApsaraDB for SelectDB instance

    Source is a self-managed SQL Server or RDS for SQL Server database

    Important

    • Supported self-managed SQL Server source databases must be one of the following editions: Enterprise, Developer, Enterprise Evaluation, Standard, or Web.

    • Supported self-managed SQL Server destination databases must be one of the following editions: Enterprise, Developer, Enterprise Evaluation, Standard, or Web.

    • SQL Server Cluster and SQL Server Always On availability groups are supported.

    • When Azure SQL Database is the source database, you must set SQL Server Incremental Synchronization Mode to Polling and querying CDC instances for incremental synchronization.

    • Self-managed SQL Server 2005 and RDS for SQL Server 2008 or 2008 R2 are not supported as source databases.

    • In hybrid log parsing mode (when SQL Server Incremental Synchronization Mode is set to Log-based Parsing for Non-heap Tables and CDC-based Incremental Synchronization for Heap Tables (Hybrid Log-based Parsing)), the supported source databases, such as RDS for SQL Server and self-managed SQL Server, are:

      • Enterprise or Enterprise Evaluation edition: 2012, 2014, 2016, 2019, or 2022.

      • Standard edition: 2016, 2019, or 2022.

    • When a Web edition of SQL Server is the source database, the only supported option for SQL Server Incremental Synchronization Mode is Incremental Synchronization Based on Logs of Source Database (Heap tables are not supported).

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

    • Self-managed SQL Server

      2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022

    • RDS for SQL Server

      2012, 2014, 2016, 2017, 2019, or 2022

    • Self-managed SQL Server

      2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022

    • RDS for SQL Server

      2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data between RDS for SQL Server instances

    • Self-managed MySQL

      5.1, 5.5, 5.6, 5.7, 8.0

    • RDS for MySQL

      All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for SQL Server instance to an RDS for MySQL instance

    PolarDB for 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

    AnalyticDB for MySQL

    3.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for SQL Server instance to an AnalyticDB for MySQL 3.0 cluster

    AnalyticDB for PostgreSQL

    4.3, 6.0, 7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    RDS for PostgreSQL

    9.4, 10, 11, 12, 13, 14, 15, 16, 17

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a self-managed SQL Server database to an RDS for PostgreSQL instance

    DataHub

    Schema synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for SQL Server instance to a DataHub project

    Source is a MariaDB database

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

    • RDS for MariaDB

    • Self-managed MariaDB

    • RDS for MariaDB

    • Self-managed MariaDB

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    RDS for MySQL

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MariaDB instance to an RDS for MySQL instance

    RDS for PostgreSQL

    9.4, 10, 11, 12, 13, 14, 15, 16, 17

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an RDS for MariaDB instance to an RDS for PostgreSQL instance

    Source is a self-managed MongoDB or ApsaraDB for MongoDB database

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

    Replica set architecture

    • Self-managed MongoDB

      3.0 to 7.0

    • ApsaraDB for MongoDB

      3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0

    Replica set or sharded cluster architecture

    • Self-managed MongoDB

      3.0 to 7.0

    • ApsaraDB for MongoDB

      3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an ApsaraDB for MongoDB replica set instance to an ApsaraDB for MongoDB replica set or sharded cluster instance

    Sharded cluster architecture

    • Self-managed MongoDB

      3.0 to 7.0

    • ApsaraDB for MongoDB

      3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0

    Replica set or sharded cluster architecture

    • Self-managed MongoDB

      3.0 to 7.0

    • ApsaraDB for MongoDB

      3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an ApsaraDB for MongoDB sharded cluster instance to an ApsaraDB for MongoDB replica set or sharded cluster instance

    ApsaraDB for MongoDB (sharded cluster architecture)

    4.0, 4.2, 4.4, 5.0, 6.0, 7.0

    ApsaraDB for MongoDB (sharded cluster architecture)

    4.0, 4.2, 4.4, 5.0, 6.0, 7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    Two-way synchronization

    Two-way synchronization between ApsaraDB for MongoDB sharded cluster instances

    ApsaraDB for MongoDB (replica set architecture)

    4.0, 4.2, 4.4, 5.0, 6.0, 7.0

    ApsaraDB for MongoDB (replica set architecture)

    4.0, 4.2, 4.4, 5.0, 6.0, 7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    Two-way synchronization

    Two-way synchronization between ApsaraDB for MongoDB replica set instances

    Replica set or sharded cluster architecture

    • Self-managed MongoDB

      3.0 to 7.0

    • ApsaraDB for MongoDB

      3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0

    Function Compute (FC)

    2.0

    Incremental data synchronization

    One-way synchronization

    Lindorm

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an ApsaraDB for MongoDB instance to a Lindorm instance

    AnalyticDB for PostgreSQL

    4.3, 6.0, 7.0

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an ApsaraDB for MongoDB instance to an AnalyticDB for PostgreSQL instance

    AnalyticDB for MySQL 3.0

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an ApsaraDB for MongoDB instance to an AnalyticDB for MySQL 3.0 cluster

    • Self-managed MySQL

      5.1, 5.5, 5.6, 5.7, 8.0

    • RDS for MySQL

      All versions

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an ApsaraDB for MongoDB instance to an RDS for MySQL instance

    PolarDB for MySQL

    All versions

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an ApsaraDB for MongoDB instance to a PolarDB for MySQL cluster

    • ApsaraMQ for Kafka

      0.10.1.0 to 2.x

    • Self-managed Kafka

      0.10.1.0 to 2.7.0

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an ApsaraDB for MongoDB instance to an ApsaraMQ for Kafka instance

    Source is a self-managed Redis or ApsaraDB for Tair (Redis Compatible) instance

    Important

    • Redis is a NoSQL database and does not require schema synchronization.

    • Only two-way synchronization between Tair (Enterprise Edition) instances is supported.

    • When the source is a self-managed Redis or ApsaraDB for Tair (Redis Compatible) instance, the Incremental Data Synchronization option supports both full data synchronization and incremental data synchronization.

    • RDB version 11 (corresponding to Redis 7.2) is the highest supported version.

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

    • Self-managed Redis (standalone or cluster architecture)

      2.8, 3.0, 3.2, 4.0, 5.0, 6.0, 7.0, 7.2

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

      4.0, 5.0, 6.0, 7.0

    • Self-managed Redis (standalone or cluster architecture)

      2.8, 3.0, 3.2, 4.0, 5.0, 6.0, 7.0, 7.2

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

      4.0, 5.0, 6.0, 7.0

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    ApsaraDB for Tair (Redis Compatible) Enterprise Edition/Tair instance (cluster, standard, or read/write splitting architecture)

    ApsaraDB for Tair (Redis Compatible) Enterprise Edition/Tair instance (cluster, standard, or read/write splitting architecture)

    Full data synchronization

    Incremental data synchronization

    Two-way synchronization

    Source is a TiDB database

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

    TiDB

    AnalyticDB for MySQL

    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 3.0 cluster

    PolarDB-X 2.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Document in preparation

    Source is a Db2 for LUW database

    Important

    • Db2 for LUW appears as DB2 for LUW in the console.

    • We recommend that you use PolarDB-X 2.0 instances that are version 5.4.11 or later. For information about how to upgrade an instance, see View and upgrade the instance version.

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

    Db2 for LUW

    9.5, 9.7, 10.1, 10.5, 11.1, 11.5

    • Self-managed MySQL

      5.1, 5.5, 5.6, 5.7, 8.0

    • RDS for MySQL

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a Db2 for LUW database to an RDS for MySQL instance

    PolarDB for MySQL

    All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a Db2 for LUW database to a PolarDB for MySQL cluster

    PolarDB-X 2.0

    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

    4.3, 6.0, 7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a Db2 for LUW database to an AnalyticDB for PostgreSQL instance

    • ApsaraMQ for Kafka

      0.10.1.0 to 2.x

    • Self-managed Kafka

      0.10.1.0 to 2.7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from a Db2 for LUW database to a self-managed Kafka cluster

    Source is a Db2 for i (AS/400) database

    Important

    Db2 for i appears as DB2 for iSeries (AS/400) in the console.

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

    Db2 for i

    7.3, 7.4

    • Self-managed MySQL

      5.1, 5.5, 5.6, 5.7, 8.0

    • RDS for MySQL

      All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Document in preparation

    PolarDB for MySQL

    All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Document in preparation

    Source is an AnalyticDB for MySQL 3.0 cluster

    Important

    The source AnalyticDB for MySQL 3.0 cluster must have a kernel version of 3.2.1.0 or later.

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

    AnalyticDB for MySQL

    3.0

    AnalyticDB for MySQL

    3.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data between AnalyticDB for MySQL 3.0 clusters

    Source is an AnalyticDB for PostgreSQL instance

    Important

    The source AnalyticDB for PostgreSQL instance must have a kernel version of 7.2.1.4 or later.

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

    AnalyticDB for PostgreSQL

    7.0

    AnalyticDB for PostgreSQL

    7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data between AnalyticDB for PostgreSQL instances

    AnalyticDB for PostgreSQL

    7.0

    ApsaraMQ for Kafka

    0.10.1.0 to 2.x

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from an AnalyticDB for PostgreSQL instance to an ApsaraMQ for Kafka instance

    Source is a Data Management (DMS) logical database

    Important

    The DMS logical database must be created using multiple sharded PolarDB for MySQL instances.

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

    Data Management (DMS) logical database

    AnalyticDB for MySQL

    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 3.0 cluster

    Source is an AWS database

    Source database

    Destination database

    Synchronization types

    Synchronization topology

    Configuration document

    AWS database

    Subject to the console

    Use DTS and a VPN Gateway to synchronize data between an Alibaba Cloud RDS instance and an AWS EC2 instance