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.
Background
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 retrieves the incremental data change statements of an object to be synchronized from the source database, such as retrieving the incremental data statements from the binary log of a MySQL database, converts the statements based on the type of the destination database, and executes the statements in the destination database. In this way, the incremental data from the source database is synchronized to the destination database. Note During incremental data synchronization, data is synchronized between the source and destination databases in real time. The synchronization task does not automatically stop. You must manually stop the migration task. For more information, see End a DTS instance and Release a DTS instance. |
Synchronization topologies
DTS supports one-way synchronization and two-way synchronization. For more information, see Synchronization topologies.
A two-way data synchronization instance contains a forward synchronization task and a reverse synchronization task. If an object is to be synchronized in both the forward and reverse synchronization tasks when you configure or reset the instance, the following rules apply:
Only one of the tasks can synchronize the schema, full data, and incremental data of objects. The other task synchronizes only the incremental data of the objects.
If you need to reset and reconfigure the forward synchronization task, we recommend that you reset both the forward and reverse tasks, and then reconfigure the tasks. Otherwise, DTS automatically removes the synchronization objects that are configured for the reverse task during the full data and schema synchronization of the forward task. In this case, the result of the two-way synchronization instance does not meet expectations.
The source data of the current task can be synchronized only to the destination database in the task. The synchronized data is not used as the source data of the other task.
Differences between data synchronization and data migration
In some scenarios, data synchronization can be used instead of data migration and provide better network stability and additional features. For more information, see the What are the differences between data migration and data synchronization? section of the topic "FAQ".
Cross-account data synchronization
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 Configure tasks across Alibaba Cloud accounts.
Limits on databases
The limits on the network bandwidth and business requirements of the source database are shown in the following table. For more information, see the specific documents.
Item | Description |
Network bandwidth |
|
Business requirements |
|
FAQ
Does DTS support Serverless ApsaraDB RDS for MySQL instances?
Yes.
Does DTS support the serverless feature of PolarDB for MySQL clusters?
Yes.
Does DTS support serverless ApsaraDB RDS for PostgreSQL instances?
A serverless ApsaraDB RDS for PostgreSQL instance can serve only as the destination database instead of the source database.
Does DTS support instances in ApsaraDB for MyBase?
Yes. When you create a task to synchronize data to or from a database instance that is created in ApsaraDB for MyBase, you can set the Access Method parameter to Alibaba Cloud Instance. Then, 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.
NoteFor 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.
What is a self-managed database?
A self-managed database is a database where the Access Method is not set to Alibaba Cloud Instance when you configure a DTS task. The self-managed database includes databases that are hosted on a third-party cloud, on-premises databases, and databases that are hosted on ECS instances.
Data synchronization scenarios
Based on your business requirements, you can click a data synchronization instance from a source database from the guide section on the right side of the page to quickly 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
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 | ||
| 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 | |
| Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB RDS for MySQL instance to an ApsaraMQ for Kafka instance | |
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, 7.x, or 8.x | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB RDS for MySQL instance 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 | |
Tair (Redis OSS-Compatible) instance (cluster, standard, or read/write splitting architecture) Version 4.0, 5.0, 6.0, or 7.0 | Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB RDS for MySQL instance to a Tair (Redis OSS-Compatible) 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 | |
ApsaraDB for SelectDB instance | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB RDS for MySQL instance to an ApsaraDB for SelectDB instance | |
ApsaraDB for Lindorm instance | Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB RDS for MySQL instance to a Lindorm instance | |
Doris cluster Version 1.2 or later | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB RDS for MySQL instance to a self-managed Doris database | |
ApsaraMQ for RocketMQ instance 4.x and 5.x series | Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB RDS for MySQL instance to an ApsaraMQ for RocketMQ instance |
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 instance | Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a PolarDB for MySQL cluster to a PolarDB-X 1.0 instance | |
PolarDB-X 2.0 instance | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a PolarDB for MySQL cluster to a PolarDB-X 2.0 instance | |
AnalyticDB for MySQL 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 | |
| Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a PolarDB for MySQL cluster to a Message Queue for Apache Kafka instance | |
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, 7.x, or 8.x | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a PolarDB for MySQL cluster to an Elasticsearch cluster | |
MaxCompute 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 | |
ApsaraDB for SelectDB instance | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a PolarDB for MySQL cluster to an ApsaraDB for SelectDB instance | |
Doris cluster Version 1.2 or later | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a PolarDB for MySQL cluster to a self-managed Doris database | |
ApsaraDB for Lindorm instance | Full Synchronization Incremental Synchronization | One-way synchronization | Synchronize data from a PolarDB for MySQL cluster to a Lindorm instance |
Synchronize data from a PolarDB for PostgreSQL cluster
Source database | Destination database | Synchronization type | Synchronization topology | References |
PolarDB for PostgreSQL cluster Version 11, 14, 15, or 16 |
| Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization Two-way synchronization | |
PolarDB for PostgreSQL cluster Version 11, 14, 15, or 16 | 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 | |
ApsaraDB for SelectDB instance | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a PolarDB for PostgreSQL cluster to an ApsaraDB for SelectDB instance |
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 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, 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 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 | 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 | |
| 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, 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, 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 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 | |
Tablestore (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 | |
| Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | ||
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 All versions | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a self-managed Oracle database to a PolarDB for MySQL cluster | |
MaxCompute project | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a self-managed Oracle database to a MaxCompute project | |
PolarDB for PostgreSQL (Compatible with Oracle) cluster All versions | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | ||
ApsaraMQ for Kafka instance Versions 0.10.1.0 to 2.x Note If the number of brokers is greater than 3, you can set Access Method to Express Connect, VPN Gateway, or Smart Access Gateway for the instance | 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, 14, 15, or 16 | 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 | ||
| 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 All versions | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | ||
SelectDB | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB RDS for PostgreSQL instance to an ApsaraDB for SelectDB instance |
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, Enterprise Evaluation, Standard, and Web.
The destination self-managed SQL Server database must be one of the following editions: Enterprise, Developer, Enterprise Evaluation, Standard, and Web.
DTS supports SQL Server clusters or SQL Server AlwaysOn High Availability groups.
if the source database is an Azure SQL Database, you must set the SQL Server Incremental Synchronization Mode parameter to Polling and querying CDC instances for incremental synchronization.
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.
If the source database is a SQL Server Web, you can only select Incremental Synchronization Based on Logs of Source Database (Heap tables are not supported) for the SQL Server Incremental Synchronization Mode parameter.
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 | ||
ApsaraDB RDS for PostgreSQL instance Version 9.4, 10, 11, 12, 13, 14, 15, or 16 | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a self-managed SQL Server database to an ApsaraDB RDS 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 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, 15, or 16 | 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 instances
| Replica set or sharded cluster instance
| Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a replica set instance to another replica set or sharded cluster instance |
Sharded cluster instances
| ReplicaSet or sharded cluster architecture
| Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | |
ApsaraDB for MongoDB sharded cluster instance Versions 4.0, 4.2, 4.4, 5.0, 6.0, or 7.0 | ApsaraDB for MongoDB sharded cluster instance Version 4.0, 4.2, 4.4, 5.0, 6.0, or 7.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, 6.0, or 7.0 | ApsaraDB for MongoDB replica set instance Version 4.0, 4.2, 4.4, 5.0, 6.0, or 7.0 | Schema synchronization Full data synchronization Incremental data synchronization | Two-way synchronization | Configure two-way data synchronization between ApsaraDB for MongoDB replica set instances |
Replica set or sharded cluster architecture
| Function Compute function | Incremental data synchronization | One-way synchronization | |
Lindorm instance | Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB for MongoDB instance to a Lindorm instance | |
AnalyticDB for PostgreSQL instance Version 4.3, 6.0, or 7.0 | Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB for MongoDB instance to an AnalyticDB for PostgreSQL instance | |
AnalyticDB for MySQL V3.0 cluster | Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB for MongoDB instance to an AnalyticDB for MySQL 3.0 cluster | |
| Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB for MongoDB instance to an ApsaraDB RDS for MySQL instance | |
PolarDB for MySQL cluster All versions | Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB for MongoDB instance to a PolarDB for MySQL cluster | |
| Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from an ApsaraDB for MongoDB instance to an ApsaraMQ for Kafka instance |
Synchronize data from a self-managed Redis database, a Tair instance, or an Tair (Redis OSS-Compatible) instance
A Redis database 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 ApsaraDB for Tair (Redis-compatible) 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 Synchronization Incremental Synchronization | One-way synchronization | |
Tair (Redis OSS-Compatible) Enterprise Edition/Tair instance (cluster, standard, or read/write splitting architecture) | Tair (Redis OSS-Compatible) Enterprise Edition/Tair instance (cluster, standard, or read/write splitting architecture) | Full data synchronization Incremental data 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 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 V3.0 cluster |
PolarDB-X 2.0 instance | 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 |
PolarDB for MySQL cluster All versions | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Synchronize data from a Db2 for LUW database to a PolarDB for MySQL cluster | |
PolarDB-X 2.0 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 | |
| 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 All versions | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization | Available soon |
Synchronize data from an AnalyticDB for MySQL V3.0 cluster
Source database | Destination database | Synchronization type | Synchronization topology | References |
AnalyticDB for MySQL V3.0 cluster | AnalyticDB for MySQL V3.0 cluster | Schema synchronization Full data synchronization Incremental data synchronization | One-way synchronization |
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 V3.0 cluster | 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 |
Synchronize data from an AWS database
Source database | Destination database | Synchronization type | Synchronization topology | References |
Amazon Web Services (AWS) database | The information in the console shall prevail. | Use DTS to synchronize data between ApsaraDB RDS and Amazon EC2 over a VPN gateway |