All Products
Search

This Product

    Data Transmission Service:Data synchronization scenarios

    Document Center

    Data Transmission Service:Data synchronization scenarios

    Last Updated:Jun 23, 2026

    The data synchronization feature of Data Transmission Service (DTS) synchronizes data in real time between different data sources. It captures data changes from a source database and synchronizes them to a target database in real time. Common use cases include version upgrades, data sharding or scaling, active geo-redundancy, geo-disaster recovery, cross-border data synchronization, query and report offloading, and real-time data warehousing. DTS helps you avoid the complexity, potential for errors, and performance challenges of managing data pipelines manually. This allows you to focus on your business instead of pipeline maintenance.

    Key concepts

    Synchronization type

    A DTS synchronization task includes three optional synchronization types for different business needs.

    Recommended options

    • Initial synchronization: For an initial synchronization, we recommend selecting Schema Synchronization, Full Data Synchronization, and Incremental Data Synchronization.

    • Existing baseline data: If you have already populated the target database, you can select only Incremental Data Synchronization. However, you must ensure that the checkpoints are consistent between the source and target databases. This complex operation requires careful assessment.

    Synchronization type

    Description

    Schema Synchronization

    Purpose: Automatically creates a schema in the target database that matches the source database.

    DTS synchronizes the schema definitions (such as tables, views, triggers, stored procedures, and indexes) from the source database to the target database. If the target database is empty, this option eliminates the need to create the schema manually.

    Important

    Some synchronization links do not support schema synchronization. Before you configure a synchronization task, you must manually create the required databases, tables, and views in the target database to match the source database schema.

    Full Data Synchronization

    Purpose: Migrates historical data from the source database.

    DTS copies all existing data for the selected objects from the source database to the target database. This establishes a data baseline for subsequent Incremental Data Synchronization.

    Incremental Data Synchronization

    Purpose: Continuously keeps the source and target databases in sync.

    DTS continuously captures incremental change statements (for example, from the Binlog of a MySQL database) for the objects to be synchronized in the source database. DTS then converts these statements for the target database and executes them to achieve real-time synchronization.

    Note

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

    Synchronization topology

    DTS supports two core synchronization topologies. For more information, see Data Synchronization Topology Introduction.

    Synchronization topology

    Description

    Applicable scenarios

    One-way Synchronization

    Data flows in one direction from a source database to one or more target databases.

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

    Two-way Synchronization

    Data flows in both directions between two databases. Changes made to either database are synchronized to the other.

    Multi-site active-active, remote disaster recovery, and cross-border synchronization.
    Important

    Two-way Synchronization involves both a forward and a reverse synchronization task. To prevent a data loop, DTS imposes the following strict limitations when you configure or reset a bidirectional synchronization task:

    • Initialization rule: Only the task in one direction (for example, A to B) can perform Schema Synchronization and Full Data Synchronization. The task in the other direction (B to A) can only be configured for Incremental Data Synchronization.

    • Data loop prevention: Data synchronized from A to B is not synchronized back to A.

    • Reset risk: If you need to reset and reconfigure one of the tasks (for example, the forward task), we recommend that you reset both the forward and reverse tasks simultaneously and then reconfigure them. Otherwise, when the forward task is performing 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 behave unexpectedly.

    Limitations

    Before configuring a task, ensure that your environment and use case meet the following requirements.

    General limits

    Limit

    Description

    Network configuration

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

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

    Workload

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

      Important

      By default, DTS pulls logs for the entire database, not just for the objects being synchronized. This means that even if you are synchronizing only a small table, frequent write operations on other large, unrelated tables can generate a high volume of logs and cause task delays. Therefore, consider this impact during planning.

    • Batch updates: Executing batch data updates or large-scale changes to large fields (such as CLOB, BLOB, or LONG types) may cause task latency. To avoid latency, perform these operations in smaller batches or avoid them if possible.

    • High-frequency DDL: Avoid frequent DDL operations. To prevent task latency, limit DDL operations to 10 statements per second.

    • Table without a primary key: Avoid frequent DELETE or UPDATE operations on such tables to prevent task latency.

    • Large transaction: Avoid executing a single transaction that generates more than 100 GB of logs, as this may cause the task to fail.

    Other limits

    • Cross-account synchronization: Support for cross-account synchronization tasks depends on the specific database type and connection method. For more information, see Configure a task across Alibaba Cloud accounts.

    • Cross-border data synchronization: This feature is not enabled by default. You must first apply for the cross-border data synchronization feature and await approval before using it.

      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. For bandwidth exceeding 100 Mbit/s, first use CEN to configure the cross-region network bandwidth before configuring the DTS task.

      • A cross-region or cross-border task is one you configure in the DTS console. 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?

    • Purpose

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

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

    • Features

      • The primary goal of data migration is to ensure final data consistency. The task stops upon completion.

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

    • Recommendations

    Can I add new tables to a running data synchronization task?

    Yes. You can add new databases or tables to a running data synchronization task by modifying the synchronization objects. However, this operation is not supported for data migration tasks.

    How do I merge data from multiple source databases into one destination database, or synchronize tables from one source database to existing tables with different names in the destination database?

    You can do this by configuring database, table, and column name mapping. When you configure synchronization objects, DTS lets you rename objects in the destination database. For example, you can synchronize the orders table from the source database db_A and the orders table from the 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?

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

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

    Does DTS support instances in ApsaraDB for MyBase?

    Yes. You can use a database instance created in ApsaraDB for MyBase as a DTS source or destination. To connect to it, set the Access Method parameter to Alibaba Cloud Instance. For example, to synchronize data from a self-managed MySQL database to a MySQL instance in ApsaraDB for MyBase, you can follow the steps described in Synchronize data from a self-managed MySQL database to an RDS for MySQL instance.

    What is a self-managed database?

    In DTS, a self-managed database is any database instance where the Access Method is not Alibaba Cloud Instance. Self-managed databases include database instances on a third-party cloud, on-premises databases, and databases deployed on ECS instances.

    Appendix: Support matrix for synchronization links

    This page summarizes the database synchronization solutions supported by DTS. Before you begin configuration, check if your source and destination database combination is supported. In the on this page section on the right, click the corresponding source database synchronization solution to view its supported versions, synchronization types, and configuration steps.

    Self-managed MySQL or RDS for MySQL

    Important

    • Databases in PolarDB-X 1.0 must be created based on an ApsaraDB RDS for MySQL instance. DTS does not support databases that are created based on PolarDB for MySQL.

    • If the destination is a PolarDB-X 1.0 instance, schema synchronization and schema initialization are not supported. If the destination is a PolarDB-X 2.0 instance, both are supported.

    • We recommend using PolarDB-X 2.0 version 5.4.11 or later. For more information, see View and upgrade the engine version of a PolarDB for Xscale instance.

    Source database

    Destination database

    Synchronization type

    Synchronization topology

    References

    • self-managed MySQL

      Versions 5.1, 5.5, 5.6, 5.7, 8.0, or 8.4

    • ApsaraDB RDS for MySQL

      All versions

    • self-managed MySQL

      Versions 5.1, 5.5, 5.6, 5.7, 8.0, or 8.4

    • ApsaraDB 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)

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

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize ApsaraDB RDS for MySQL to a self-managed Oracle database

    PolarDB-X 1.0

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize ApsaraDB RDS for MySQL to PolarDB-X 1.0

    PolarDB-X 2.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize ApsaraDB RDS for MySQL to PolarDB-X 2.0

    AnalyticDB for MySQL

    Versions 2.0 or 3.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    • self-managed PostgreSQL

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

    • ApsaraDB RDS for PostgreSQL

      Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, or 18

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize ApsaraDB RDS for MySQL to ApsaraDB RDS for PostgreSQL

    AnalyticDB for PostgreSQL

    Versions 4.3, 6.0, or 7.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize ApsaraDB RDS for MySQL to AnalyticDB for PostgreSQL

    • ApsaraMQ for Kafka

      Versions 0.10.1.0 to 2.x

    • self-managed Kafka

      Versions 0.10.1.0 to 2.7.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize ApsaraDB RDS for MySQL to ApsaraMQ for Kafka

    ApsaraDB for ClickHouse

    Version 20.8 or later

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from ApsaraDB RDS for MySQL to ApsaraDB for ClickHouse

    DataHub

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize ApsaraDB RDS for MySQL to DataHub

    Elasticsearch

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

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize ApsaraDB RDS for MySQL to Elasticsearch

    MaxCompute

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize ApsaraDB RDS for MySQL to MaxCompute

    Tair

    Versions 4.0, 5.0, 6.0, or 7.0

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from ApsaraDB RDS for MySQL to Tair

    Tablestore

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize ApsaraDB RDS for MySQL to Tablestore

    Function Compute

    Version 2.0

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize ApsaraDB RDS for MySQL to Function Compute

    ApsaraDB for SelectDB

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize ApsaraDB RDS for MySQL to ApsaraDB for SelectDB

    ApsaraDB for Lindorm

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize ApsaraDB RDS for MySQL to ApsaraDB for Lindorm

    Doris

    Version 1.2 or later

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from ApsaraDB RDS for MySQL to a self-managed Doris database

    ApsaraMQ for RocketMQ

    4.x and 5.x series

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize ApsaraDB RDS for MySQL to ApsaraMQ for RocketMQ

    Source: PolarDB for MySQL

    Important

    • Databases in PolarDB-X 1.0 must be created based on an ApsaraDB RDS for MySQL instance. DTS does not support databases that are created based on PolarDB for MySQL.

    • If the destination is a PolarDB-X 1.0 instance, schema synchronization and schema initialization are not supported. If the destination is a PolarDB-X 2.0 instance, both are supported.

    • We recommend using PolarDB-X 2.0 version 5.4.11 or later. For more information, see View and upgrade the engine version of a PolarDB for Xscale instance.

    Source database

    Destination database

    Type

    Topology

    Documentation

    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

      Version 5.1, 5.5, 5.6, 5.7, 8.0, or 8.4

    • ApsaraDB RDS for MySQL

      All versions

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    two-way synchronization

    Synchronize data from PolarDB for MySQL to ApsaraDB RDS for MySQL

    PolarDB-X 1.0

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from PolarDB for MySQL to PolarDB-X 1.0

    PolarDB-X 2.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from PolarDB for MySQL to PolarDB-X 2.0

    AnalyticDB for MySQL

    Version 2.0 or 3.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    AnalyticDB for PostgreSQL

    Version 4.3, 6.0, or 7.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from PolarDB for MySQL to AnalyticDB for PostgreSQL

    • Message Queue for Apache Kafka

      Versions 0.10.1.0 to 2.x

    • self-managed Kafka

      Versions 0.10.1.0 to 2.7.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from PolarDB for MySQL to Message Queue for Apache Kafka

    DataHub

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from PolarDB for MySQL to DataHub

    ApsaraDB for ClickHouse

    Version 20.8 or later

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from PolarDB for MySQL to ApsaraDB for ClickHouse

    Elasticsearch

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

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from PolarDB for MySQL to Elasticsearch

    MaxCompute

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from PolarDB for MySQL to MaxCompute

    Oracle (RAC or non-RAC)

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

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

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

    ApsaraDB for SelectDB

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from PolarDB for MySQL to ApsaraDB for SelectDB

    Doris

    Version 1.2 or later

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

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

    ApsaraDB for Lindorm

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from PolarDB for MySQL to ApsaraDB for Lindorm

    Source: PolarDB for PostgreSQL

    Source

    Destination

    Synchronization type

    Topology

    Documentation

    PolarDB for PostgreSQL

    Versions 11, 14, 15, 16, 17, and 18

    • self-managed PostgreSQL database

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

    • ApsaraDB RDS for PostgreSQL

      Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    two-way synchronization

    PolarDB for PostgreSQL

    Versions 11, 14, 15, 16, 17, and 18

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    two-way synchronization

    AnalyticDB for PostgreSQL

    Versions 4.3, 6.0, and 7.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronizing PolarDB for PostgreSQL to AnalyticDB for PostgreSQL

    Alibaba Cloud SelectDB

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronizing PolarDB for PostgreSQL to Alibaba Cloud SelectDB

    PolarDB-X as the source

    Important

    • Databases in PolarDB-X 1.0 must be created based on an ApsaraDB RDS for MySQL instance. DTS does not support databases that are created based on PolarDB for MySQL.

    • If the destination is a PolarDB-X 1.0 instance, schema synchronization and schema initialization are not supported. If the destination is a PolarDB-X 2.0 instance, both are supported.

    • We recommend using PolarDB-X 2.0 version 5.4.11 or later. For more information, see View and upgrade the engine version of a PolarDB for Xscale instance.

    Source database

    Destination database

    Synchronization type

    Synchronization topology

    References

    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

      Version 5.1, 5.5, 5.6, 5.7, 8.0, or 8.4

    • 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

    Version 3.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

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

    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

    Version 4.3, 6.0, or 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

    • Message Queue for Apache Kafka

      Versions 0.10.1.0 to 2.x

    • self-managed Kafka

      Versions 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 Message Queue for Apache Kafka

    Elasticsearch

    Version 5.5, 5.6, 6.x, 7.x, or 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

      Version 5.1, 5.5, 5.6, 5.7, 8.0, or 8.4

    • 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

    Version 3.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

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

    • Message Queue for Apache Kafka

      Versions 0.10.1.0 to 2.x

    • self-managed Kafka

      Versions 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 Message Queue for Apache Kafka

    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

    Version 4.3, 6.0, or 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

    Version 5.5, 5.6, 6.x, 7.x, or 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)

    Version 9i, 10g, 11g, 12c, 18c, or 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

    Alibaba Cloud SelectDB

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from a PolarDB-X 2.0 instance to an Alibaba Cloud SelectDB instance

    PolarDB for PostgreSQL (Compatible with Oracle) as a source

    Source database

    Destination database

    Synchronization type

    Synchronization topology

    Documentation

    PolarDB for PostgreSQL (Compatible with Oracle) cluster

    All versions

    PolarDB for PostgreSQL (Compatible with Oracle) cluster

    All versions

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    two-way synchronization

    • Message Queue for Kafka

      Versions 0.10.1.0–2.x

    • self-managed Kafka cluster

      Versions 0.10.1.0–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 Message Queue for Kafka

    AnalyticDB for MySQL cluster

    Version 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 AnalyticDB for MySQL 3.0

    Source: Oracle

    Important

    Source database

    Destination database

    Synchronization type

    Synchronization topology

    References

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

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

    AnalyticDB for PostgreSQL

    Version 4.3, 6.0, or 7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize a self-managed Oracle database to AnalyticDB for PostgreSQL

    DataHub

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize a self-managed Oracle database to DataHub

    PolarDB-X 2.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize a self-managed Oracle database to PolarDB-X 2.0

    PolarDB for MySQL

    All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize a self-managed Oracle database to PolarDB for MySQL

    MaxCompute

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize a self-managed Oracle database to MaxCompute

    PolarDB for PostgreSQL (Compatible with Oracle)

    All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

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

    ApsaraMQ for Kafka

    Versions 0.10.1.0 to 2.x

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize a self-managed Oracle database to ApsaraMQ for Kafka

    Source: self-managed PostgreSQL or RDS for PostgreSQL

    Important

    A serverless RDS for PostgreSQL instance can be used as a destination database, but not as a source database.

    Source database

    Destination database

    Synchronization type

    Synchronization topology

    References

    • self-managed PostgreSQL

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

    • RDS for PostgreSQL

      Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18

    • self-managed PostgreSQL

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

    • RDS for PostgreSQL

      Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Two-way synchronization

    PolarDB for PostgreSQL

    Versions 11, 14, 15, 16, 17, and 18

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Two-way synchronization

    AnalyticDB for PostgreSQL

    Versions 4.3, 6.0, and 7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize RDS for PostgreSQL to AnalyticDB for PostgreSQL

    • self-managed MySQL

      Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

    • RDS for MySQL

      All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize RDS for PostgreSQL to RDS for MySQL

    PolarDB for PostgreSQL (Compatible with Oracle)

    All versions

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize self-managed PostgreSQL to PolarDB for PostgreSQL (Compatible with Oracle)

    SelectDB

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize RDS for PostgreSQL to SelectDB

    Source: Self-managed or ApsaraDB RDS for SQL Server

    Important

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

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

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

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

    • The following are not supported as source databases: self-managed SQL Server version 2005 and ApsaraDB RDS for SQL Server versions 2008 or 2008 R2.

    • In hybrid log parsing mode, where the 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 following source databases are supported:

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

      • Standard edition: 2016, 2019, 2022, or 2025.

    • If the source database is the Web edition of SQL Server, the SQL Server Incremental Synchronization Mode can only be set to Incremental Synchronization Based on Logs of Source Database (Heap tables are not supported).

    Source

    Destination

    Sync type

    Topology

    Guide

    • Self-managed SQL Server

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

    • ApsaraDB RDS for SQL Server

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

    • Self-managed SQL Server

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

    • ApsaraDB RDS for SQL Server

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

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data between ApsaraDB RDS for SQL Server instances

    • Self-managed MySQL

      Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

    • ApsaraDB RDS for MySQL

      All versions

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from ApsaraDB RDS for SQL Server to ApsaraDB RDS for MySQL

    PolarDB for MySQL

    All versions

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from a self-managed SQL Server to PolarDB for MySQL

    AnalyticDB for MySQL

    Version 3.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from ApsaraDB RDS for SQL Server to AnalyticDB for MySQL 3.0

    AnalyticDB for PostgreSQL

    Versions 4.3, 6.0, and 7.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    ApsaraDB RDS for PostgreSQL

    Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from a self-managed SQL Server to ApsaraDB RDS for PostgreSQL

    DataHub

    schema synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from ApsaraDB RDS for SQL Server to DataHub

    Source: MariaDB

    Source

    Destination

    Sync type

    Topology

    Documentation

    • ApsaraDB RDS for MariaDB

      • 10.x

    • A self-managed MariaDB database

      • 10.x, 11.0 to 11.4

    • ApsaraDB RDS for MariaDB

    • A self-managed MariaDB database

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    ApsaraDB RDS for MySQL

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from ApsaraDB RDS for MariaDB to ApsaraDB RDS for MySQL

    ApsaraDB RDS for PostgreSQL

    Versions 9.4, 10, 11, 12, 13, 14, 15, and 16

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from ApsaraDB RDS for MariaDB to ApsaraDB RDS for PostgreSQL

    Source: Self-managed or Alibaba Cloud MongoDB

    Source

    Destination

    Sync type

    Topology

    Guide

    Replica set architecture

    • self-managed MongoDB

      Versions 3.0 to 8.0

    • Alibaba Cloud MongoDB

      Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

    Replica set or sharded cluster architecture

    • self-managed MongoDB

      Versions 3.0 to 8.0

    • Alibaba Cloud MongoDB

      Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize a replica set to a replica set or sharded cluster

    Sharded cluster architecture

    • self-managed MongoDB

      Versions 3.0 to 8.0

    • Alibaba Cloud MongoDB

      Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

    Replica set or sharded cluster architecture

    • self-managed MongoDB

      Versions 3.0 to 8.0

    • Alibaba Cloud MongoDB

      Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize a sharded cluster to a replica set or sharded cluster

    Alibaba Cloud MongoDB (sharded cluster architecture)

    Versions 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

    Alibaba Cloud MongoDB (sharded cluster architecture)

    Versions 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    two-way synchronization

    Two-way synchronization between Alibaba Cloud MongoDB sharded clusters

    Alibaba Cloud MongoDB (replica set architecture)

    Versions 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

    Alibaba Cloud MongoDB (replica set architecture)

    Versions 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    two-way synchronization

    Two-way synchronization between Alibaba Cloud MongoDB replica sets

    Replica set or sharded cluster architecture

    • self-managed MongoDB

      Versions 3.0 to 8.0

    • Alibaba Cloud MongoDB

      Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

    Function Compute

    Version 2.0

    incremental data synchronization

    one-way synchronization

    Lindorm

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize MongoDB to Lindorm

    AnalyticDB for PostgreSQL

    Versions 4.3, 6.0, and 7.0

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize MongoDB to AnalyticDB for PostgreSQL

    AnalyticDB for MySQL 3.0

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize MongoDB to AnalyticDB for MySQL 3.0

    • self-managed MySQL

      Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

    • Alibaba Cloud RDS for MySQL

      All versions

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize MongoDB to Alibaba Cloud RDS for MySQL

    PolarDB for MySQL

    All versions

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize MongoDB to PolarDB for MySQL

    • ApsaraMQ for Kafka

      Versions 0.10.1.0 to 2.x

    • self-managed Kafka

      Versions 0.10.1.0 to 2.7.0

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize MongoDB to Message Queue for Apache Kafka

    Source: Self-managed Redis or Tair (Redis OSS-Compatible)

    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 database is a self-managed Redis or a Tair (Redis OSS-Compatible) instance, full data synchronization and incremental data synchronization are supported and collectively displayed as Incremental Data Synchronization.

    • It supports RDB versions up to 11, corresponding to Redis 7.2.

    Source database

    Destination database

    Type

    Topology

    References

    • Self-managed Redis (standalone or cluster architecture)

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

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

      Versions 4.0, 5.0, 6.0, and 7.0

    • Self-managed Redis (standalone or cluster architecture)

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

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

      Versions 4.0, 5.0, 6.0, and 7.0

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

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

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

    Full data synchronization

    Incremental data synchronization

    Two-way synchronization

    Source: TiDB

    Source database

    Destination database

    Synchronization type

    Synchronization topology

    Documentation

    TiDB

    AnalyticDB for MySQL cluster

    Version 3.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize a self-managed TiDB database to an AnalyticDB for MySQL V3.0 cluster

    PolarDB-X 2.0 instance

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Coming soon

    Source: Db2 for LUW

    Important

    • Db2 for LUW is displayed as DB2 for LUW in the console.

    • The destination PolarDB-X 2.0 instance should be version 5.4.11 or later. For upgrade instructions, see View and upgrade instance version.

    Source database

    Destination database

    Synchronization type

    Synchronization topology

    Configuration document

    Db2 for LUW

    Versions 9.5, 9.7, 10.1, 10.5, 11.1, and 11.5

    • Self-managed MySQL

      Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

    • RDS for MySQL

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from Db2 for LUW 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 Db2 for LUW to a PolarDB for MySQL cluster

    PolarDB-X 2.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize data from Db2 for LUW to a PolarDB-X 2.0 instance

    AnalyticDB for PostgreSQL

    Versions 4.3, 6.0, and 7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

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

    • Message Queue for Apache Kafka

      Versions 0.10.1.0 to 2.x

    • Self-managed Kafka

      Versions 0.10.1.0 to 2.7.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

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

    Source: Db2 for i (AS/400)

    Important

    The console displays Db2 for i as DB2 for iSeries (AS/400).

    Source database

    Destination database

    Synchronization type

    Synchronization topology

    Documentation

    Db2 for i

    Versions 7.3 and 7.4

    • self-managed MySQL

      Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

    • ApsaraDB RDS for MySQL

      All versions

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Available soon

    PolarDB for MySQL

    All versions

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Available soon

    Source: AnalyticDB for MySQL 3.0

    Important

    The source AnalyticDB for MySQL 3.0 cluster must run kernel version 3.2.1.0 or later.

    Source database

    Destination database

    Synchronization type

    Synchronization topology

    Configuration guide

    AnalyticDB for MySQL

    Version 3.0

    AnalyticDB for MySQL

    Version 3.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Synchronize data from AnalyticDB for MySQL 3.0 to AnalyticDB for MySQL 3.0

    Source: AnalyticDB for PostgreSQL

    Important

    The source AnalyticDB for PostgreSQL instance requires kernel version 7.2.1.4 or later.

    Source

    Destination

    Type

    Topology

    Document

    AnalyticDB for PostgreSQL

    Version 7.0

    AnalyticDB for PostgreSQL

    Version 7.0

    schema synchronization

    full data synchronization

    incremental data synchronization

    one-way synchronization

    Data Synchronization Between AnalyticDB for PostgreSQL Instances

    AnalyticDB for PostgreSQL

    Version 7.0

    Message Queue for Apache Kafka

    Versions 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 a Message Queue for Apache Kafka Instance

    DMS logical database as a source

    Important

    A DMS logical database must be created from shards of multiple PolarDB for MySQL clusters.

    Source database

    Destination database

    Synchronization type

    Synchronization topology

    Configuration document

    DMS logical database

    AnalyticDB for MySQL

    Version 3.0

    Schema synchronization

    Full data synchronization

    Incremental data synchronization

    One-way synchronization

    Synchronize a DMS logical database to AnalyticDB for MySQL 3.0

    Source: AWS database

    Source database

    Destination database

    Synchronization type

    Synchronization topology

    Configuration document

    AWS database

    See the console for the latest information.

    Use DTS to synchronize data between ApsaraDB RDS and Amazon EC2 over a VPN gateway