All Products
Search
Document Center

Data Transmission Service:Overview of data synchronization scenarios

Last Updated:Jul 27, 2023

You can use Data Transmission Service (DTS) to synchronize data between data sources in real time. Typical scenarios include active geo-redundancy, geo-disaster recovery, zone-disaster recovery, cross-border data synchronization, cloud business intelligence (BI) systems, and real-time data warehousing. This topic describes the database types, synchronization types, and synchronization topologies that are supported by DTS.

Note
  • In some scenarios, data synchronization can implement part of data migration features and can provide better network stability and additional features. For more information about the differences between the two features, see the "What are the differences between data migration and data synchronization?" section of the FAQ topic.

  • When you create a task to synchronize data to or from a database instance that is created in ApsaraDB MyBase, you can set the Access Method parameter to Alibaba Cloud Instance. This way, DTS can access the database instance. You can configure the synchronization task by referring to the topics listed in the following tables. For example, you can synchronize data from a self-managed MySQL database to an ApsaraDB MyBase for MySQL instance by referring to Synchronize data from a self-managed MySQL database to an ApsaraDB RDS for MySQL instance.

Synchronization types

Synchronization type

Description

Schema synchronization

DTS synchronizes the schemas of the required objects from the source database to the destination database. Tables, views, triggers, and stored procedures can be synchronized.

Important

Before you configure a data synchronization task, check whether schema synchronization is supported. If schema synchronization is not supported, you must create a destination database and tables based on the schemas of required objects in the source database.

Full data synchronization

DTS synchronizes the historical data of required objects from the source database to the destination database. Historical data is the basis for subsequent incremental synchronization.

To simplify data synchronization, we recommend that you select both Schema Synchronization and Full Data Synchronization when you configure a data synchronization task.

Incremental data synchronization

By default, incremental data synchronization is supported. DTS synchronizes incremental data that are generated in the source database to the destination database in real time.

Synchronization topologies

For information about synchronization topologies, see Synchronization topologies.

Data synchronization scenarios

DTS supports the following data synchronization scenarios. You can select one of the following scenarios based on your business requirements to view the supported database versions, synchronization types, and configuration procedure.

Note

Self-managed databases mentioned in the following tables, such as a self-managed MySQL or Redis database, can be one of the following types:

  • Self-managed database hosted on an Elastic Compute Service (ECS) instance

  • Self-managed database connected over Express Connect, VPN Gateway, or Smart Access Gateway

  • Self-managed database without a public IP address or port number (connected over Database Gateway)

  • Self-managed database connected over Cloud Enterprise Network (CEN)

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

Important
  • A database in a PolarDB-X 1.0 instance must be created based on one or more ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X 1.0 databases that are created based on PolarDB for MySQL clusters.

  • For a data synchronization task that has a PolarDB-X 1.0 instance configured as the destination instance, schema synchronization and initial schema synchronization are not supported. Schema synchronization and initial schema synchronization are supported for PolarDB-X 2.0 instances.

  • A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.

Source database

Destination database

Synchronization type

Synchronization topology

References

  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • ApsaraDB RDS for MySQL instance

    All versions

  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • ApsaraDB RDS for MySQL instance

    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 database (RAC or non-RAC architecture)

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

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

PolarDB-X 1.0 or PolarDB-X 2.0 instance

Full data synchronization

Incremental data synchronization

One-way synchronization

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

AnalyticDB for MySQL cluster

Version 2.0 or 3.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from an ApsaraDB RDS for MySQL instance to an AnalyticDB for MySQL V3.0 cluster

Synchronize data from an ApsaraDB RDS instance to an AnalyticDB for MySQL cluster

  • Self-managed PostgreSQL database

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

  • ApsaraDB RDS for PostgreSQL instance

    Version 9.4, 10, 11, 12, 13, 14, or 15

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

AnalyticDB for PostgreSQL instance

Version 4.3 or 6.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

Synchronize data from a self-managed MySQL database hosted on ECS to an AnalyticDB for PostgreSQL instance

Synchronize data from a self-managed MySQL database connected over Express Connect, VPN Gateway, or Smart Access Gateway to an AnalyticDB for PostgreSQL instance

Message Queue for Apache Kafka instance

Version 0.10.1.0 to 2.x

Self-managed Kafka cluster

Version 0.10.1.0 to 2.7.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

DataHub project

Schema synchronization

Incremental data synchronization

One-way synchronization

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

Elasticsearch cluster

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

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from a self-managed MySQL database hosted on ECS to an Elasticsearch cluster

MaxCompute project

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

Tablestore instance

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

Synchronize data from a PolarDB for MySQL cluster

Important
  • A database in a PolarDB-X 1.0 instance must be created based on one or more ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X 1.0 databases that are created based on PolarDB for MySQL clusters.

  • For a data synchronization task that has a PolarDB-X 1.0 instance configured as the destination instance, schema synchronization and initial schema synchronization are not supported. Schema synchronization and initial schema synchronization are supported for PolarDB-X 2.0 instances.

  • A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.

Source database

Destination database

Synchronization type

Synchronization topology

References

PolarDB for MySQL

All versions

PolarDB for MySQL

All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Two-way synchronization

Synchronize data between PolarDB for MySQL clusters

  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • ApsaraDB RDS for MySQL instance

    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 ApsaraDB RDS for MySQL instance

PolarDB-X 1.0 or PolarDB-X 2.0 instance

Full data synchronization

Incremental data synchronization

One-way synchronization

Two-way synchronization

AnalyticDB for MySQL cluster

Version 2.0 or 3.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

AnalyticDB for PostgreSQL instance

Version 4.3 or 6.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

Message Queue for Apache Kafka instance

Version 0.10.1.0 to 2.x

Self-managed Kafka cluster

Version 0.10.1.0 to 2.7.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

DataHub project

Schema synchronization

Incremental data synchronization

One-way synchronization

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

Elasticsearch cluster

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

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

Oracle database (RAC or non-RAC architecture)

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

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

Synchronize data from a PolarDB for PostgreSQL cluster

Source database

Destination database

Synchronization type

Synchronization topology

References

PolarDB for PostgreSQL

Version 11

  • Self-managed PostgreSQL database

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

  • ApsaraDB RDS for PostgreSQL instance

    Version 9.4, 10, 11, 12, 13, 14, or 15

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Two-way synchronization

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

PolarDB for PostgreSQL

Version 11

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Two-way synchronization

Synchronize data between PolarDB for PostgreSQL clusters

AnalyticDB for PostgreSQL instance

Version 4.3 or 6.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

Synchronize data from a PolarDB-X instance

Important
  • A database in a PolarDB-X 1.0 instance must be created based on one or more ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X 1.0 databases that are created based on PolarDB for MySQL clusters.

  • For a data synchronization task that has a PolarDB-X 1.0 instance configured as the destination instance, schema synchronization and initial schema synchronization are not supported. Schema synchronization and initial schema synchronization are supported for PolarDB-X 2.0 instances.

  • A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.

Source database

Destination database

Synchronization type

Synchronization topology

References

PolarDB-X 1.0 instance

PolarDB-X 1.0 instance

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data between PolarDB-X 1.0 instances

  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • ApsaraDB RDS for MySQL instance

    All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

PolarDB for MySQL

All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

AnalyticDB for MySQL cluster

Version 3.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from a PolarDB-X 1.0 instance to an AnalyticDB for MySQL V3.0 cluster

DataHub project

Schema synchronization

Incremental data synchronization

One-way synchronization

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

AnalyticDB for PostgreSQL instance

Version 4.3 or 6.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Available soon

  • Message Queue for Apache Kafka instance

    Version 0.10.1.0 to 2.x

  • Self-managed Kafka cluster

    Version 0.10.1.0 to 2.7.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from a PolarDB-X 1.0 instance to an ApsaraMQ for Kafka instance

Elasticsearch cluster

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

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Available soon

PolarDB-X 2.0 instance

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Available soon

PolarDB-X 2.0 instance

PolarDB-X 2.0 instance

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Two-way synchronization

  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • ApsaraDB RDS for MySQL instance

    All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

PolarDB for MySQL

All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

AnalyticDB for MySQL cluster

Version 3.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from a PolarDB-X 2.0 instance to an AnalyticDB for MySQL V3.0 cluster

Message Queue for Apache Kafka instance

Version 0.10.1.0 to 2.x

Self-managed Kafka cluster

Version 0.10.1.0 to 2.7.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from a PolarDB-X 2.0 instance to a Message Queue for Apache Kafka instance

DataHub project

Schema synchronization

Incremental data synchronization

One-way synchronization

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

MaxCompute project

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 instance

Version 4.3 or 6.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Available soon

Elasticsearch cluster

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

Synchronize data from a PolarDB for PostgreSQL(Compatible with Oracle) cluster

Source database

Destination database

Synchronization type

Synchronization topology

References

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

Configure one-way data synchronization between PolarDB for Oracle clusters

Message Queue for Apache Kafka instance

Version 0.10.1.0 to 2.x

Self-managed Kafka cluster

Version 0.10.1.0 to 2.7.0

Incremental data synchronization

One-way synchronization

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

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 an AnalyticDB for MySQL V3.0 cluster

Synchronize data from an Oracle database

Important
  • You can configure a data synchronization task for this scenario only in the DTS console of the new version.

  • A destination database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.

Source database

Destination database

Synchronization type

Synchronization topology

References

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

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

AnalyticDB for PostgreSQL instance

Version 4.3 or 6.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from a self-managed Oracle database to an AnalyticDB for PostgreSQL instance

DataHub project

Schema synchronization

Incremental data synchronization

One-way synchronization

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

PolarDB-X 2.0 instance

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from a self-managed Oracle database to a PolarDB-X V2.0 instance

MaxCompute project

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Available soon

PolarDB for PostgreSQL(Compatible with Oracle)

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Available soon

Message Queue for Apache Kafka instance

Version 0.10.1.0 to 2.x

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from a self-managed Oracle database to a Message Queue for Apache Kafka instance

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

Important

The source ApsaraDB RDS for PostgreSQL instance cannot be of Serverless Edition.

Source database

Destination database

Synchronization type

Synchronization topology

References

  • Self-managed PostgreSQL database

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

  • ApsaraDB RDS for PostgreSQL instance

    Version 9.4, 10, 11, 12, 13, 14, or 15

  • Self-managed PostgreSQL database

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

  • ApsaraDB RDS for PostgreSQL instance

    Version 9.4, 10, 11, 12, 13, 14, or 15

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Two-way synchronization

PolarDB for PostgreSQL

Version 11

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Two-way synchronization

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

AnalyticDB for PostgreSQL instance

Version 4.3 or 6.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • ApsaraDB RDS for MySQL instance

    All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

PolarDB for PostgreSQL(Compatible with Oracle)

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

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

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

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

  • If the SQL Server Incremental Synchronization Mode parameter is set to Log-based Parsing for Non-heap Tables and CDC-based Incremental Synchronization for Heap Tables, data is synchronized in the hybrid log-based parsing mode and the following versions of source databases are supported:

    • Self-managed SQL Server or ApsaraDB RDS for SQL Server database of the Enterprise or Enterprise Evaluation edition: version 2012, 2014, 2016, or 2019.

    • Self-managed SQL Server or ApsaraDB RDS for SQL Server database of the Standard edition: version 2016 or 2019.

Source database

Destination database

Synchronization type

Synchronization topology

References

  • Self-managed SQL Server database

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

  • ApsaraDB RDS for SQL Server instance

    Version 2012, 2014, 2016, 2017, or 2019

  • Self-managed SQL Server database

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

  • ApsaraDB RDS for SQL Server instance

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

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data between ApsaraDB RDS for SQL Server instances

  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • ApsaraDB RDS for MySQL instance

    All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

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 cluster

Version 3.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from an ApsaraDB RDS for SQL Server instance to an AnalyticDB for MySQL V3.0 cluster

AnalyticDB for PostgreSQL instance

Version 4.3 or 6.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

DataHub project

Schema synchronization

Incremental data synchronization

One-way synchronization

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

Synchronize data from an ApsaraDB RDS for MariaDB instance

Source database

Destination database

Synchronization type

Synchronization topology

References

ApsaraDB RDS for MariaDB instance

ApsaraDB RDS for MariaDB instance

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Available soon

ApsaraDB RDS for MySQL instance

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Available soon

ApsaraDB RDS for PostgreSQL instance

Version 9.4, 10, 11, 12, 13, 14, or 15

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Available soon

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

Source database

Destination database

Synchronization type

Synchronization topology

References

  • Self-managed MongoDB database (replica set architecture)

    Versions 2.8 to 5.0

  • ApsaraDB for MongoDB instance (replica set architecture)

    Version 3.4, 4.0, 4.2, 4.4, or 5.0

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

    Versions 2.8 to 5.0

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

    Version 3.4, 4.0, 4.2, 4.4, or 5.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from an ApsaraDB for MongoDB instance (replica set architecture) to another ApsaraDB for MongoDB instance (replica set architecture or sharded cluster architecture)

ApsaraDB for MongoDB instance (sharded cluster architecture)

Version 3.4, 4.0, 4.2, 4.4, or 5.0

ApsaraDB for MongoDB instance (sharded cluster architecture)

Version 3.4, 4.0, 4.2, 4.4, or 5.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Two-way synchronization

ApsaraDB for MongoDB instance (replica set architecture)

Version 3.4, 4.0, 4.2, 4.4, or 5.0

ApsaraDB for MongoDB instance (replica set architecture)

Version 3.4, 4.0, 4.2, 4.4, or 5.0

Schema synchronization

Full data synchronization

Incremental data synchronization

Two-way synchronization

Configure two-way data synchronization between ApsaraDB for MongoDB replica set instances

Synchronize data from a self-managed Redis database, a Tair instance, or an ApsaraDB for Redis instance

Important
  • A Redis database is a NoSQL database that does not require schema synchronization.

  • A Tair enhanced SSD (ESSD)-based instance cannot be configured as the source database.

  • A two-way data synchronization task supports only ApsaraDB for Redis Enhanced Edition (Tair) instances that use local disks, Tair dynamic random access memory (DRAM)-based instances that use cloud disks, and Tair persistent memory-optimized instances that use cloud disks.

  • If the source database is a self-managed Redis database or an ApsaraDB for Redis Community Edition instance, full data synchronization and incremental data synchronization are supported and displayed as incremental data synchronization.

Source database

Destination database

Synchronization type

Synchronization topology

References

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

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

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

    Version 4.0, 5.0, or 6.0

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

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

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

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

    Version 4.0, 5.0, or 6.0

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

Full data synchronization

Incremental data synchronization

One-way synchronization

Two-way synchronization

Synchronize data from a TiDB database

Source database

Destination database

Synchronization type

Synchronization topology

References

TiDB database

AnalyticDB for MySQL cluster

Version 2.0 or 3.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from a self-managed TiDB database to an AnalyticDB for MySQL cluster

Synchronize data from a Db2 for LUW database

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

  • A destination database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.

Source database

Destination database

Synchronization type

Synchronization topology

References

Db2 for LUW database

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

  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • ApsaraDB RDS for MySQL instance

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

AnalyticDB for MySQL cluster

Version 3.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from a Db2 for LUW database to an AnalyticDB for MySQL V3.0 cluster

PolarDB for MySQL

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 instance

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

AnalyticDB for PostgreSQL instance

Version 4.3 or 6.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

Message Queue for Apache Kafka instance

Version 0.10.1.0 to 2.x

Self-managed Kafka cluster

Version 0.10.1.0 to 2.7.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

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

  • Self-managed PostgreSQL database

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

  • ApsaraDB RDS for PostgreSQL instance

    Version 9.4, 10, 11, 12, 13, 14, or 15

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Available soon

PolarDB for PostgreSQL

Version 11

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Available soon

Synchronize data from a Db2 for i database

Important

The Db2 for i database is displayed as DB2 iSeries(AS/400) in the console.

Source database

Destination database

Synchronization type

Synchronization topology

References

Db2 for i database

Version 7.3 or 7.4

  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • ApsaraDB RDS for MySQL instance

    All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Available soon

PolarDB for MySQL

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Available soon

Synchronize data from a DMS logical database

Important

A logical database in Data Management (DMS) must be created based on the database shards of multiple PolarDB for MySQL clusters.

Source database

Destination database

Synchronization type

Synchronization topology

References

DMS logical database

AnalyticDB for MySQL cluster

Version 3.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from a DMS logical database to an AnalyticDB for MySQL V3.0 cluster