Data Transmission Service (DTS) allows you 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 the data synchronization feature of DTS.
In some scenarios, data synchronization can be used instead of data migration and provide better network stability and additional features. For more information about the differences between data migration and data synchronization, see the What are the differences between data migration and data synchronization? section of the "FAQ" topic.
Cross-region data synchronization is not supported if the destination database is a Function Compute function.
Whether cross-account data synchronization is supported depends on the type and access method of a database. If cross-account data synchronization is supported, the Replicate Data Across Alibaba Cloud Accounts parameter is displayed when you configure the source and destination databases. If you want to synchronize data across Alibaba Cloud accounts, set this parameter to Yes. For more information, see the Supported databases section of the "Configure a DTS task across Alibaba Cloud accounts" topic.
The source or destination database can be a serverless ApsaraDB RDS for MySQL instance. The destination database can be a serverless ApsaraDB RDS for PostgreSQL instance. The source or destination database cannot be a serverless ApsaraMQ for Kafka instance.
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. DTS can access the database instance as expected. You can configure the data synchronization task by following the instructions described in the corresponding topic. You can find the link to the topic in one of the following tables. For example, the Synchronize data from a self-managed MySQL database to an ApsaraDB RDS for MySQL instance topic describes how to synchronize data from a self-managed MySQL database to an ApsaraDB MyBase for MySQL instance.
Synchronization types
Synchronization type | Description |
Schema synchronization | DTS synchronizes the schemas of the selected objects, such as tables, views, triggers, and stored procedures, from the source database to the destination database. 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 the selected objects in the source database. |
Full data synchronization | DTS synchronizes the historical data of the selected objects from the source database to the destination database. The historical data is the basis for subsequent incremental data 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 is generated in the source database to the destination database in real time. |
Synchronization topologies
For more information, 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 procedures.
Synchronize data from a self-managed MySQL database or an ApsaraDB RDS for MySQL instance
Synchronize data from a PolarDB for PostgreSQL (Compatible with Oracle) cluster
Synchronize data from a self-managed PostgreSQL database or an ApsaraDB RDS for PostgreSQL instance
Synchronize data from a self-managed SQL Server database or an ApsaraDB RDS for SQL Server instance
Synchronize data from a self-managed MongoDB database or an ApsaraDB for MongoDB instance
Self-managed databases described 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)
DTS tasks that involve this type of database may be unstable due to factors such as poor quality of Internet connections. We recommend that you use Express Connect or Smart Access Gateway to connect the local data center to a virtual private cloud (VPC). This way, DTS can access the self-managed database over Express Connect, VPN Gateway, or Smart Access Gateway. For more information, see Connect a data center to a VPC.
Self-managed database connected over Cloud Enterprise Network (CEN)
Synchronize data from a self-managed MySQL database or an ApsaraDB RDS for MySQL instance
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 synchronizes data to a PolarDB-X 1.0 instance, schema synchronization or initial schema synchronization is not supported. Schema synchronization and initial schema synchronization are supported for a data synchronization task that synchronizes data to a PolarDB-X 2.0 instance.
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 |
|
| Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization Two-way synchronization | |
PolarDB for MySQL cluster All versions | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization Two-way synchronization | ||
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 instance | Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB RDS for MySQL instance to a PolarDB-X 1.0 instance | |
PolarDB-X 2.0 instance | Schema synchronization 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 | |
| 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, 6.0, or 7.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 | |
ApsaraMQ for Kafka instance Versions 0.10.1.0 to 2.x Self-managed Kafka cluster Versions 0.10.1.0 to 2.7.0 | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | ||
ApsaraDB for ClickHouse cluster Version 20.8 or later | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB RDS for MySQL instance to an ApsaraDB for ClickHouse cluster | |
DataHub project | Schema synchronization Full data 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 | |
| Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB RDS for MySQL instance to a Tair or ApsaraDB for Redis instance | |
Tablestore (OTS) 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 | |
Function Compute function | Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB RDS for MySQL instance to a Function Compute function |
Synchronize data from a PolarDB for MySQL cluster
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 synchronizes data to a PolarDB-X 1.0 instance, schema synchronization or initial schema synchronization is not supported. Schema synchronization and initial schema synchronization are supported for a data synchronization task that synchronizes data to a PolarDB-X 2.0 instance.
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 cluster All versions | PolarDB for MySQL cluster All versions | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization Two-way synchronization | |
| 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, 6.0, or 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 instance Versions 0.10.1.0 to 2.x Self-managed Kafka cluster Versions 0.10.1.0 to 2.7.0 | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a PolarDB for MySQL cluster to a self-managed Kafka cluster | |
DataHub project | 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 Version 20.8 or later | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a PolarDB for MySQL cluster to an ApsaraDB for ClickHouse cluster | |
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 cluster Version 11 or 14 |
| 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 cluster Version 11 or 14 | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization Two-way synchronization | ||
AnalyticDB for PostgreSQL instance Version 4.3, 6.0, or 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 |
Synchronize data from a PolarDB-X instance
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 synchronizes data to a PolarDB-X 1.0 instance, schema synchronization or initial schema synchronization is not supported. Schema synchronization and initial schema synchronization are supported for a data synchronization task that synchronizes data to a PolarDB-X 2.0 instance.
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 | |
| Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a PolarDB-X 1.0 instance to an ApsaraDB RDS for MySQL instance | |
PolarDB for MySQL cluster All versions | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a PolarDB-X 1.0 instance to a PolarDB for MySQL cluster | |
AnalyticDB for MySQL cluster Version 3.0 | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | 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, 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 | |
| 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 | Synchronize data from a PolarDB-X 1.0 instance to an Elasticsearch cluster | |
PolarDB-X 2.0 instance | 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 instance | PolarDB-X 2.0 instance | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization Two-way synchronization | |
| Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a PolarDB-X 2.0 instance to an ApsaraDB RDS for MySQL instance | |
PolarDB for MySQL cluster All versions | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a PolarDB-X 2.0 instance to a PolarDB for MySQL cluster | |
AnalyticDB for MySQL cluster Version 3.0 | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a PolarDB-X 2.0 instance to an AnalyticDB for MySQL V3.0 cluster | |
ApsaraMQ for Kafka instance Versions 0.10.1.0 to 2.x Self-managed Kafka cluster Versions 0.10.1.0 to 2.7.0 | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a PolarDB-X 2.0 instance to an ApsaraMQ for 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, 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 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 | |
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-X 2.0 instance to a self-managed Oracle database | |
OTS instance | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a PolarDB-X 2.0 instance to a Tablestore instance |
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) 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 | |
ApsaraMQ for Kafka instance Versions 0.10.1.0 to 2.x Self-managed Kafka cluster Versions 0.10.1.0 to 2.7.0 | Incremental data synchronization | One-way synchronization | 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 an Oracle database
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, 6.0, or 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 project | 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 instance | 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 cluster | 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 project | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Available soon | |
PolarDB for PostgreSQL (Compatible with Oracle) cluster | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Available soon | |
ApsaraMQ for Kafka instance Versions 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 |
Synchronize data from a self-managed PostgreSQL database or an ApsaraDB RDS for PostgreSQL instance
A serverless ApsaraDB RDS for PostgreSQL instance can serve as the destination database but not as the source database.
Source database | Destination database | Synchronization type | Synchronization topology | References |
|
| Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization Two-way synchronization | |
PolarDB for PostgreSQL cluster Version 11 or 14 | 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, 6.0, or 7.0 | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | ||
| Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB RDS for PostgreSQL instance to an ApsaraDB RDS for MySQL instance | |
PolarDB for PostgreSQL (Compatible with Oracle) cluster | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization |
Synchronize data from a self-managed SQL Server database or an ApsaraDB RDS for SQL Server instance
The source self-managed SQL Server database must be one of the following editions: Enterprise, Developer, and Enterprise Evaluation.
The destination self-managed SQL Server database must be one of the following editions: Enterprise, Developer, Enterprise Evaluation, and Standard.
DTS does not support SQL Server clusters or SQL Server Always On availability groups (AOAGs).
The source database cannot be a self-managed SQL Server database of version 2015 or an ApsaraDB RDS for SQL Server database of version 2008 or 2008R2.
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 |
|
| Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data between ApsaraDB RDS for SQL Server instances |
| Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB RDS for SQL Server instance to an ApsaraDB RDS for MySQL instance | |
PolarDB for MySQL cluster All versions | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a self-managed SQL Server database to a PolarDB for MySQL cluster | |
AnalyticDB for MySQL cluster Version 3.0 | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | ||
AnalyticDB for PostgreSQL instance Version 4.3, 6.0, or 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 SQL Server instance to a DataHub project |
Synchronize data from a MariaDB database
Source database | Destination database | Synchronization type | Synchronization topology | References |
|
| Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | |
ApsaraDB RDS for MySQL instance | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB RDS for MariaDB TX instance to an ApsaraDB RDS for MySQL instance | |
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 a self-managed MongoDB database or an ApsaraDB for MongoDB instance
Source database | Destination database | Synchronization type | Synchronization topology | References |
Replica set architecture
| Replica set or sharded cluster architecture
| Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | |
Sharded cluster architecture
| Replica set or sharded cluster architecture
| Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | |
Replica set or sharded cluster architecture
| Function Compute function | Incremental data synchronization | One-way synchronization | |
Replica set or sharded cluster architecture
| Lindorm instance | Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB for MongoDB instance to a Lindorm instance |
ApsaraDB for MongoDB sharded cluster instance Version 4.0, 4.2, 4.4, 5.0, or 6.0 | ApsaraDB for MongoDB sharded cluster instance Version 4.0, 4.2, 4.4, 5.0, or 6.0 | Schema synchronization Full data synchronization Incremental data synchronization | Two-way synchronization | Configure two-way data synchronization between ApsaraDB for MongoDB sharded cluster instances |
ApsaraDB for MongoDB replica set instance Version 4.0, 4.2, 4.4, 5.0, or 6.0 | ApsaraDB for MongoDB replica set instance Version 4.0, 4.2, 4.4, 5.0, or 6.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
A Redis database is a NoSQL database and does not require schema synchronization.
Two-way data synchronization supports only 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 collectively displayed as Incremental Data Synchronization.
Source database | Destination database | Synchronization type | Synchronization topology | References |
|
| Full data synchronization Incremental data synchronization | One-way synchronization Two-way synchronization |
Synchronize data from a TiDB database
Source database | Destination database | Synchronization type | Synchronization topology | References |
TiDB database | AnalyticDB for MySQL cluster Version 2.0 or 3.0 | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a self-managed TiDB database to an AnalyticDB for MySQL cluster |
PolarDB for MySQL cluster All versions | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Available soon |
Synchronize data from a Db2 for LUW database
The Db2 for LUW database is displayed as DB2 for 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 |
| 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 cluster | 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, 6.0, or 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 instance Versions 0.10.1.0 to 2.x Self-managed Kafka cluster Versions 0.10.1.0 to 2.7.0 | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a Db2 for LUW database to a self-managed Kafka cluster |
Synchronize data from an iSeries DB2 (AS/400) database
The iSeries DB2 (AS/400) 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 |
| Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Available soon |
PolarDB for MySQL cluster | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Available soon |
Synchronize data from a DMS logical database
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 |