Data Transmission Service (DTS) keeps databases in sync by continuously capturing changes from a source database and applying them to a destination database in real time. Use DTS synchronization for ongoing replication scenarios: version upgrades, active geo-redundancy, geo-disaster recovery, cross-border data synchronization, data sharding or scaling, query and report offloading, and building real-time data warehouses.
Key concepts
Synchronization types
DTS breaks synchronization into three phases that run in sequence. Understanding this sequence explains why you typically enable all three together:
Schema synchronization copies database object definitions—tables, views, triggers, stored procedures, and indexes—from the source to the destination. This creates the structure the data will occupy.
Full data synchronization copies all existing data from the source to the destination. While this runs, DTS captures any new changes that arrive so they are not lost.
Incremental data synchronization applies those captured changes, then continuously replicates new changes from the source (for example, from a MySQL binary log) to keep the two databases in sync. This phase runs indefinitely—to stop it, manually end the DTS instance or release the DTS instance.
Which types to enable:
| Starting point | Types to enable | Notes |
|---|---|---|
| New synchronization (destination is empty) | Schema Synchronization + Full Data Synchronization + Incremental Data Synchronization | Recommended for most cases |
| Destination already has baseline data | Incremental Data Synchronization only | Verify data consistency between source and destination before starting. This is a complex operation that requires careful evaluation. |
Important
Some synchronization links do not support schema synchronization. For these links, create the required databases, tables, and views in the destination database manually before configuring the task.
Synchronization topologies
DTS supports two topologies. For details, see Introduction to data synchronization topologies.
| Topology | Description | Use cases |
|---|---|---|
| One-way synchronization | Data flows in one direction from a source database to one or more destination databases. | Data sharding or scaling, query and report offloading, building real-time data warehouses |
| Two-way synchronization | Data flows in both directions between two databases. Changes in either database are replicated to the other. | Active geo-redundancy, geo-disaster recovery, cross-border synchronization |
Two-way synchronization rules
Two-way synchronization consists of a forward task and a reverse task. To prevent data loops, DTS enforces the following rules:
Initialization: Only one direction (for example, A to B) can run Schema Synchronization and Full Data Synchronization. The reverse direction (B to A) can only run Incremental Data Synchronization.
Loop prevention: Data synchronized from A to B is not synchronized back to A.
Resetting: To reset either task, reset both the forward and reverse tasks before reconfiguring either one. If you reset only the forward task and it runs Schema Synchronization and Full Data Synchronization, the system automatically removes the synchronization objects configured in the reverse task, which can produce unexpected results.
Limitations
Review the following requirements before configuring a synchronization task.
Network and workload limits
| Limit | Requirement |
|---|---|
| Source database network bandwidth | 100 Mb/s or greater |
| Network round-trip time (RT) | Less than 2 ms between the source database and the DTS service. Cross-region or cross-border deployments increase RT due to physical distance, which can cause synchronization latency. |
| Peak log volume | Less than 1 TB per day |
| Average hourly log volume | Less than 50 GB |
| Peak traffic | Less than 15 MB/s |
| DDL operations | No more than 10 DDL operations per second. Avoid frequent DDL operations to prevent task latency. |
| Tables without primary keys | Avoid frequent DELETE or UPDATE operations on tables without primary keys. These operations can cause task latency. |
| Large transactions | Avoid transactions that generate more than 100 GB of logs in a single transaction. These can cause task failure. |
| Batch updates | Performing batch data updates or large-scale changes to large object types (CLOB, BLOB, LONG) can cause task latency. Perform these operations in batches or avoid them if possible. |
Important
DTS pulls logs from the entire source database, not only the objects being synchronized. If unrelated tables in the database have high write volumes, the resulting log traffic can cause latency in your synchronization task—even if the synchronized objects themselves have low write activity. Account for this when planning your synchronization setup.
Other limits
Cross-account synchronization: Whether cross-account tasks are supported depends on the database type and connection type. For details, see Configure a task across Alibaba Cloud accounts.
Cross-border data synchronization: This feature is disabled by default. Request permission for cross-border data synchronization before configuring a cross-border task. You can use the feature only after your request is approved.
Note
For cross-border or cross-region tasks, the required bandwidth must not exceed 100 Mbit/s. If your bandwidth requirement exceeds this limit, configure cross-region network bandwidth using Cloud Enterprise Network (CEN) before configuring the DTS task. A cross-region or cross-border task is one where the source and destination databases are in different regions—for example, synchronizing from an RDS instance in the Singapore region to an RDS instance in the China (Hangzhou) region.
FAQ
Does DTS support instances in an ApsaraDB for MyBase dedicated cluster?
Yes. Use database instances from an ApsaraDB for MyBase dedicated cluster as a DTS source or destination by setting Access Method to Alibaba Cloud Instance.
What counts as a self-managed database?
Any database instance for which Access Method is not set to Alibaba Cloud Instance. This includes databases from third-party cloud providers, on-premises databases, and databases deployed on ECS instances.
Appendix: Synchronization link support matrix
The following tables summarize the synchronization links that DTS supports. Use this matrix to verify whether your source and destination database combination is supported before you begin configuration.
Source: Self-managed MySQL or RDS for MySQL
Important
Databases in PolarDB-X 1.0 must be created based on RDS for MySQL. DTS does not support databases created based on PolarDB for MySQL.
When PolarDB-X 1.0 is the destination, schema synchronization and initial schema synchronization are not supported. Both are supported when PolarDB-X 2.0 is the destination.
PolarDB-X 2.0 instances must be version 5.4.11 or later. For upgrade instructions, see View and upgrade the instance version.
| Source database | Destination database | Synchronization type | Topology | Configuration guide |
|---|---|---|---|---|
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | Schema synchronization, full data synchronization, incremental data synchronization | One-way, two-way | Synchronize data from a self-managed MySQL database to an RDS for MySQL instance / One-way synchronization between RDS for MySQL instances / Two-way synchronization between MySQL databases / Synchronize RDS for MySQL instances across Alibaba Cloud accounts |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | PolarDB for MySQL (all versions) | Schema synchronization, full data synchronization, incremental data synchronization | One-way, two-way | Synchronize data from RDS for MySQL to PolarDB for MySQL / Two-way synchronization between a MySQL database and a PolarDB for MySQL instance |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to a self-managed Oracle database |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | PolarDB-X 1.0 | Full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to PolarDB-X 1.0 |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | PolarDB-X 2.0 | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to PolarDB-X 2.0 |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | AnalyticDB for MySQL (2.0, 3.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to AnalyticDB for MySQL 3.0 / Synchronize data from RDS to AnalyticDB for MySQL |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to RDS for PostgreSQL |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | AnalyticDB for PostgreSQL (4.3, 6.0, 7.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to AnalyticDB for PostgreSQL |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x) / Self-managed Kafka (0.10.1.0–2.7.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to Alibaba Cloud Message Queue for Kafka |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | ApsaraDB for ClickHouse cluster (version 20.8 and later) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to an ApsaraDB for ClickHouse cluster |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | DataHub | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to DataHub |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | Elasticsearch (5.5, 5.6, 6.x, 7.x, 8.x) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to Elasticsearch |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | MaxCompute | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to MaxCompute |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | ApsaraDB for Tair (compatible with Redis) cluster/standard/read-write splitting (4.0, 5.0, 6.0, 7.0) | Full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to Tair/Redis |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | Tablestore | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to Tablestore |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | Function Compute (FC) version 2.0 | Full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to Function Compute (FC) |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | ApsaraDB for SelectDB | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to ApsaraDB for SelectDB |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | Lindorm | Full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to Lindorm |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | Doris (version 1.2 and later) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to a self-managed Doris cluster |
| Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | ApsaraMQ for RocketMQ (4.x and 5.x) | Full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MySQL to ApsaraMQ for RocketMQ |
Source: PolarDB for MySQL
Important
Databases in PolarDB-X 1.0 must be created based on RDS for MySQL. DTS does not support databases created based on PolarDB for MySQL.
When PolarDB-X 1.0 is the destination, schema synchronization and initial schema synchronization are not supported. Both are supported when PolarDB-X 2.0 is the destination.
PolarDB-X 2.0 instances must be version 5.4.11 or later. For upgrade instructions, see View and upgrade the instance version.
| Source database | Destination database | Synchronization type | Topology | Configuration guide |
|---|---|---|---|---|
| PolarDB for MySQL (all versions) | PolarDB for MySQL (all versions) | Schema synchronization, full data synchronization, incremental data synchronization | One-way, two-way | One-way synchronization between PolarDB for MySQL instances / Two-way synchronization between PolarDB for MySQL instances |
| PolarDB for MySQL (all versions) | Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | Schema synchronization, full data synchronization, incremental data synchronization | One-way, two-way | Synchronize data from PolarDB for MySQL to RDS for MySQL |
| PolarDB for MySQL (all versions) | PolarDB-X 1.0 | Full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB for MySQL to PolarDB-X 1.0 |
| PolarDB for MySQL (all versions) | PolarDB-X 2.0 | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB for MySQL to PolarDB-X 2.0 |
| PolarDB for MySQL (all versions) | AnalyticDB for MySQL (2.0, 3.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB for MySQL to AnalyticDB for MySQL 3.0 / Synchronize data from PolarDB for MySQL to AnalyticDB for MySQL |
| PolarDB for MySQL (all versions) | AnalyticDB for PostgreSQL (4.3, 6.0, 7.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB for MySQL to AnalyticDB for PostgreSQL |
| PolarDB for MySQL (all versions) | Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x) / Self-managed Kafka (0.10.1.0–2.7.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB for MySQL to Alibaba Cloud Message Queue for Kafka |
| PolarDB for MySQL (all versions) | DataHub | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB for MySQL to DataHub |
| PolarDB for MySQL (all versions) | ApsaraDB for ClickHouse cluster (version 20.8 and later) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB for MySQL to an ApsaraDB for ClickHouse cluster |
| PolarDB for MySQL (all versions) | Elasticsearch (5.5, 5.6, 6.x, 7.x, 8.x) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB for MySQL to Elasticsearch |
| PolarDB for MySQL (all versions) | MaxCompute | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB for MySQL to MaxCompute |
| PolarDB for MySQL (all versions) | Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB for MySQL to a self-managed Oracle database |
| PolarDB for MySQL (all versions) | ApsaraDB for SelectDB | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB for MySQL to ApsaraDB for SelectDB |
| PolarDB for MySQL (all versions) | Doris (version 1.2 and later) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB for MySQL to a self-managed Doris cluster |
| PolarDB for MySQL (all versions) | Lindorm | Full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB for MySQL to Lindorm |
Source: PolarDB for PostgreSQL
| Source database | Destination database | Synchronization type | Topology | Configuration guide |
|---|---|---|---|---|
| PolarDB for PostgreSQL (versions 11, 14, 15, 16, 17) | Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17) | Schema synchronization, full data synchronization, incremental data synchronization | One-way, two-way | Synchronize data from PolarDB for PostgreSQL to RDS for PostgreSQL / Two-way synchronization between PolarDB for PostgreSQL and RDS for PostgreSQL |
| PolarDB for PostgreSQL (versions 11, 14, 15, 16, 17) | PolarDB for PostgreSQL (versions 11, 14, 15, 16, 17) | Schema synchronization, full data synchronization, incremental data synchronization | One-way, two-way | One-way synchronization between PolarDB for PostgreSQL instances / Two-way synchronization between PolarDB for PostgreSQL instances |
| PolarDB for PostgreSQL (versions 11, 14, 15, 16, 17) | AnalyticDB for PostgreSQL (4.3, 6.0, 7.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB for PostgreSQL to AnalyticDB for PostgreSQL |
| PolarDB for PostgreSQL (versions 11, 14, 15, 16, 17) | ApsaraDB for SelectDB | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB for PostgreSQL to ApsaraDB for SelectDB |
Source: PolarDB-X
Important
Databases in PolarDB-X 1.0 must be created based on RDS for MySQL. DTS does not support databases created based on PolarDB for MySQL.
When PolarDB-X 1.0 is the destination, schema synchronization and initial schema synchronization are not supported. Both are supported when PolarDB-X 2.0 is the destination.
PolarDB-X 2.0 instances must be version 5.4.11 or later. For upgrade instructions, see View and upgrade the instance version.
| Source database | Destination database | Synchronization type | Topology | Configuration guide |
|---|---|---|---|---|
| PolarDB-X 1.0 | PolarDB-X 1.0 | Full data synchronization, incremental data synchronization | One-way | Synchronize data between PolarDB-X 1.0 instances |
| PolarDB-X 1.0 | Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 1.0 to RDS for MySQL |
| PolarDB-X 1.0 | PolarDB for MySQL (all versions) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 1.0 to PolarDB for MySQL |
| PolarDB-X 1.0 | AnalyticDB for MySQL (version 3.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 1.0 to AnalyticDB for MySQL 3.0 |
| PolarDB-X 1.0 | DataHub | Schema synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 1.0 to DataHub |
| PolarDB-X 1.0 | AnalyticDB for PostgreSQL (4.3, 6.0, 7.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 1.0 to AnalyticDB for PostgreSQL |
| PolarDB-X 1.0 | Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x) / Self-managed Kafka (0.10.1.0–2.7.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 1.0 to Alibaba Cloud Message Queue for Kafka |
| PolarDB-X 1.0 | Elasticsearch (5.5, 5.6, 6.x, 7.x, 8.x) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 1.0 to Elasticsearch |
| PolarDB-X 1.0 | PolarDB-X 2.0 | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 1.0 to PolarDB-X 2.0 |
| PolarDB-X 2.0 | PolarDB-X 2.0 | Schema synchronization, full data synchronization, incremental data synchronization | One-way, two-way | One-way synchronization between PolarDB-X 2.0 instances / Two-way synchronization between PolarDB-X 2.0 instances |
| PolarDB-X 2.0 | Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 2.0 to RDS for MySQL |
| PolarDB-X 2.0 | PolarDB for MySQL (all versions) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 2.0 to PolarDB for MySQL |
| PolarDB-X 2.0 | AnalyticDB for MySQL (version 3.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 2.0 to AnalyticDB for MySQL 3.0 |
| PolarDB-X 2.0 | Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x) / Self-managed Kafka (0.10.1.0–2.7.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 2.0 to Alibaba Cloud Message Queue for Kafka |
| PolarDB-X 2.0 | DataHub | Schema synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 2.0 to DataHub |
| PolarDB-X 2.0 | MaxCompute | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 2.0 to MaxCompute |
| PolarDB-X 2.0 | AnalyticDB for PostgreSQL (4.3, 6.0, 7.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 2.0 to AnalyticDB for PostgreSQL |
| PolarDB-X 2.0 | Elasticsearch (5.5, 5.6, 6.x, 7.x, 8.x) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 2.0 to Elasticsearch |
| PolarDB-X 2.0 | Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 2.0 to a self-managed Oracle database |
| PolarDB-X 2.0 | Tablestore | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 2.0 to Tablestore |
| PolarDB-X 2.0 | PolarDB-X 1.0 | Full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 2.0 to PolarDB-X 1.0 |
| PolarDB-X 2.0 | ApsaraDB for SelectDB | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from PolarDB-X 2.0 to ApsaraDB for SelectDB |
Source: PolarDB for PostgreSQL (Compatible with Oracle)
| Source database | Destination database | Synchronization type | Topology | Configuration guide |
|---|---|---|---|---|
| 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, two-way | One-way synchronization between PolarDB for PostgreSQL (Compatible with Oracle) clusters / Two-way synchronization between PolarDB for PostgreSQL (Compatible with Oracle) clusters |
| PolarDB for PostgreSQL (Compatible with Oracle) (all versions) | Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x) / Self-managed Kafka (0.10.1.0–2.7.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from a PolarDB for PostgreSQL (Compatible with Oracle) cluster to Alibaba Cloud Message Queue for Kafka |
| PolarDB for PostgreSQL (Compatible with Oracle) (all versions) | AnalyticDB for MySQL (version 3.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from a PolarDB for PostgreSQL (Compatible with Oracle) cluster to AnalyticDB for MySQL 3.0 |
Source: Oracle
Important
This source type can only be configured in the new DTS console.
The destination PolarDB-X 2.0 instance must be version 5.4.11 or later. For upgrade instructions, see View and upgrade the instance version.
| Source database | Destination database | Synchronization type | Topology | Configuration guide |
|---|---|---|---|---|
| Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c) | AnalyticDB for PostgreSQL (4.3, 6.0, 7.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from a self-managed Oracle database to AnalyticDB for PostgreSQL |
| Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c) | DataHub | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from a self-managed Oracle database to DataHub |
| Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c) | PolarDB-X 2.0 | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from a self-managed Oracle database to PolarDB-X 2.0 |
| Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c) | PolarDB for MySQL (all versions) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from a self-managed Oracle database to PolarDB for MySQL |
| Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c) | MaxCompute | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from a self-managed Oracle database to MaxCompute |
| Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c) | PolarDB for PostgreSQL (Compatible with Oracle) (all versions) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from a self-managed Oracle database to PolarDB for PostgreSQL (Compatible with Oracle) |
| Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c) | Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from a self-managed Oracle database to Alibaba Cloud Message Queue for Kafka |
Source: Self-managed PostgreSQL or RDS for PostgreSQL
Important
RDS for PostgreSQL Serverless instances are not supported as a source database but are supported as a destination database.
| Source database | Destination database | Synchronization type | Topology | Configuration guide |
|---|---|---|---|---|
| Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17) | Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17) | Schema synchronization, full data synchronization, incremental data synchronization | One-way, two-way | Two-way synchronization between PostgreSQL databases / One-way synchronization between RDS for PostgreSQL instances / Synchronize data from a self-managed PostgreSQL database to an RDS for PostgreSQL instance |
| Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17) | PolarDB for PostgreSQL (versions 11, 14, 15, 16, 17) | Schema synchronization, full data synchronization, incremental data synchronization | One-way, two-way | Synchronize data from RDS for PostgreSQL to PolarDB for PostgreSQL / Two-way synchronization between RDS for PostgreSQL and PolarDB for PostgreSQL |
| Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17) | AnalyticDB for PostgreSQL (4.3, 6.0, 7.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for PostgreSQL to AnalyticDB for PostgreSQL |
| Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17) | Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for PostgreSQL to RDS for MySQL |
| Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17) | PolarDB for PostgreSQL (Compatible with Oracle) (all versions) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from a self-managed PostgreSQL database to PolarDB for PostgreSQL (Compatible with Oracle) |
| Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17) | ApsaraDB for SelectDB | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for PostgreSQL to ApsaraDB for SelectDB |
Source: Self-managed SQL Server or RDS for SQL Server
Important
Supported editions for self-managed SQL Server (both source and destination): Enterprise, Developer, Enterprise Evaluation, Standard, and Web.
SQL Server clusters and SQL Server Always On availability groups are supported.
If the source database is Azure SQL Database, set SQL Server Incremental Synchronization Mode to Polling and querying CDC instances for incremental synchronization.
Self-managed SQL Server 2005 and RDS for SQL Server 2008 and 2008 R2 are not supported as a source.
Hybrid log parsing mode (Log-based Parsing for Non-heap Tables and CDC-based Incremental Synchronization for Heap Tables (Hybrid Log-based Parsing)) supports:
Enterprise or Enterprise Evaluation Edition: versions 2012, 2014, 2016, 2019, or 2022.
Standard Edition: versions 2016, 2019, or 2022.
Web Edition sources support only Incremental Synchronization Based on Logs of Source Database (Heap tables are not supported).
| Source database | Destination database | Synchronization type | Topology | Configuration guide |
|---|---|---|---|---|
| Self-managed SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022) / RDS for SQL Server (2012, 2014, 2016, 2017, 2019, 2022) | Self-managed SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022) / RDS for SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data between RDS for SQL Server instances |
| Self-managed SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022) / RDS for SQL Server (2012, 2014, 2016, 2017, 2019, 2022) | Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for SQL Server to RDS for MySQL |
| Self-managed SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022) / RDS for SQL Server (2012, 2014, 2016, 2017, 2019, 2022) | PolarDB for MySQL (all versions) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from a self-managed SQL Server database to PolarDB for MySQL |
| Self-managed SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022) / RDS for SQL Server (2012, 2014, 2016, 2017, 2019, 2022) | AnalyticDB for MySQL (version 3.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for SQL Server to AnalyticDB for MySQL 3.0 |
| Self-managed SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022) / RDS for SQL Server (2012, 2014, 2016, 2017, 2019, 2022) | AnalyticDB for PostgreSQL (4.3, 6.0, 7.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from a self-managed SQL Server database to AnalyticDB for PostgreSQL / Synchronize data from RDS for SQL Server to AnalyticDB for PostgreSQL |
| Self-managed SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022) / RDS for SQL Server (2012, 2014, 2016, 2017, 2019, 2022) | RDS for PostgreSQL (9.4, 10–17) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from a self-managed SQL Server database to RDS for PostgreSQL |
| Self-managed SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022) / RDS for SQL Server (2012, 2014, 2016, 2017, 2019, 2022) | DataHub | Schema synchronization, incremental data synchronization | One-way | Synchronize data from RDS for SQL Server to DataHub |
Source: MariaDB
| Source database | Destination database | Synchronization type | Topology | Configuration guide |
|---|---|---|---|---|
| RDS for MariaDB (10.x) / Self-managed MariaDB (10.x, 11.0–11.4) | RDS for MariaDB / Self-managed MariaDB | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data between RDS for MariaDB instances / Synchronize data from a self-managed MariaDB database to an RDS for MariaDB instance |
| RDS for MariaDB (10.x) / Self-managed MariaDB (10.x, 11.0–11.4) | RDS for MySQL | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MariaDB to RDS for MySQL |
| RDS for MariaDB (10.x) / Self-managed MariaDB (10.x, 11.0–11.4) | RDS for PostgreSQL (9.4, 10–17) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from RDS for MariaDB to RDS for PostgreSQL |
Source: Self-managed MongoDB or ApsaraDB for MongoDB
| Source database | Destination database | Synchronization type | Topology | Configuration guide |
|---|---|---|---|---|
| Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0) — replica set architecture | Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0) — replica set or sharded cluster architecture | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from an ApsaraDB for MongoDB replica set instance to an ApsaraDB for MongoDB replica set or sharded cluster instance |
| Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0) — sharded cluster architecture | Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0) — replica set or sharded cluster architecture | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from an ApsaraDB for MongoDB sharded cluster instance to an ApsaraDB for MongoDB replica set or sharded cluster instance |
| ApsaraDB for MongoDB sharded cluster (4.0, 4.2, 4.4, 5.0, 6.0, 7.0) | ApsaraDB for MongoDB sharded cluster (4.0, 4.2, 4.4, 5.0, 6.0, 7.0) | Schema synchronization, full data synchronization, incremental data synchronization | Two-way | Two-way synchronization between ApsaraDB for MongoDB sharded cluster instances |
| ApsaraDB for MongoDB replica set (4.0, 4.2, 4.4, 5.0, 6.0, 7.0) | ApsaraDB for MongoDB replica set (4.0, 4.2, 4.4, 5.0, 6.0, 7.0) | Schema synchronization, full data synchronization, incremental data synchronization | Two-way | Two-way synchronization between ApsaraDB for MongoDB replica set instances |
| Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0) — replica set or sharded cluster | Function Compute (FC) version 2.0 | Incremental data synchronization | One-way | Synchronize data from an ApsaraDB for MongoDB replica set instance to Function Compute (FC) / Synchronize data from an ApsaraDB for MongoDB sharded cluster instance to Function Compute (FC) |
| Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0) | Lindorm | Full data synchronization, incremental data synchronization | One-way | Synchronize data from ApsaraDB for MongoDB to Lindorm |
| Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0) | AnalyticDB for PostgreSQL (4.3, 6.0, 7.0) | Full data synchronization, incremental data synchronization | One-way | Synchronize data from ApsaraDB for MongoDB to AnalyticDB for PostgreSQL |
| Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0) | AnalyticDB for MySQL 3.0 | Full data synchronization, incremental data synchronization | One-way | Synchronize data from ApsaraDB for MongoDB to AnalyticDB for MySQL 3.0 |
| Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0) | Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | Full data synchronization, incremental data synchronization | One-way | Synchronize data from ApsaraDB for MongoDB to RDS for MySQL |
| Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0) | PolarDB for MySQL (all versions) | Full data synchronization, incremental data synchronization | One-way | Synchronize data from ApsaraDB for MongoDB to PolarDB for MySQL |
| Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0) | Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x) / Self-managed Kafka (0.10.1.0–2.7.0) | Full data synchronization, incremental data synchronization | One-way | Synchronize data from ApsaraDB for MongoDB to Alibaba Cloud Message Queue for Kafka |
Source: Self-managed Redis or ApsaraDB for Tair (compatible with Redis)
Important
Redis is a NoSQL database and does not require schema synchronization.
Only two-way synchronization between Tair (Enterprise Edition) instances is supported.
When the source is a self-managed Redis instance or an ApsaraDB for Tair (compatible with Redis) instance, full and incremental data synchronization are combined into a single step called Incremental Data Synchronization.
The highest supported RDB version is 11, which corresponds to Redis 7.2.
| Source database | Destination database | Synchronization type | Topology | Configuration guide |
|---|---|---|---|---|
| Self-managed Redis standalone or cluster (2.8, 3.0, 3.2, 4.0, 5.0, 6.0, 7.0, 7.2) / ApsaraDB for Tair (compatible with Redis) cluster/standard/read-write splitting (4.0, 5.0, 6.0, 7.0) | Self-managed Redis standalone or cluster (2.8, 3.0, 3.2, 4.0, 5.0, 6.0, 7.0, 7.2) / ApsaraDB for Tair (compatible with Redis) cluster/standard/read-write splitting (4.0, 5.0, 6.0, 7.0) | Full data synchronization, incremental data synchronization | One-way | One-way synchronization between ApsaraDB for Tair (compatible with Redis) instances / Cross-account one-way synchronization / Synchronize data from a self-managed Redis instance on an ECS instance to an ApsaraDB for Tair (compatible with Redis) instance |
| ApsaraDB for Tair (compatible with Redis) Enterprise Edition/Tair cluster/standard/read-write splitting | ApsaraDB for Tair (compatible with Redis) Enterprise Edition/Tair cluster/standard/read-write splitting | Full data synchronization, incremental data synchronization | Two-way | Two-way synchronization between Tair (Enterprise Edition) instances / Use an OpenAPI to configure one-way or two-way data synchronization between Tair (Enterprise Edition) instances |
Source: TiDB
| Source database | Destination database | Synchronization type | Topology | Configuration guide |
|---|---|---|---|---|
| TiDB | AnalyticDB for MySQL (version 3.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from a self-managed TiDB database to AnalyticDB for MySQL 3.0 |
| TiDB | PolarDB-X 2.0 | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Document in preparation |
Source: Db2 for LUW
Important
Db2 for LUW is displayed as DB2 for LUW in the console.
The destination PolarDB-X 2.0 instance must be version 5.4.11 or later. For upgrade instructions, see View and upgrade the instance version.
| Source database | Destination database | Synchronization type | Topology | Configuration guide |
|---|---|---|---|---|
| Db2 for LUW (9.5, 9.7, 10.1, 10.5, 11.1, 11.5) | Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from Db2 for LUW to RDS for MySQL |
| Db2 for LUW (9.5, 9.7, 10.1, 10.5, 11.1, 11.5) | PolarDB for MySQL (all versions) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from Db2 for LUW to PolarDB for MySQL |
| Db2 for LUW (9.5, 9.7, 10.1, 10.5, 11.1, 11.5) | PolarDB-X 2.0 | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from Db2 for LUW to PolarDB-X 2.0 |
| Db2 for LUW (9.5, 9.7, 10.1, 10.5, 11.1, 11.5) | AnalyticDB for PostgreSQL (4.3, 6.0, 7.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from Db2 for LUW to AnalyticDB for PostgreSQL |
| Db2 for LUW (9.5, 9.7, 10.1, 10.5, 11.1, 11.5) | Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x) / Self-managed Kafka (0.10.1.0–2.7.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from Db2 for LUW to a self-managed Kafka cluster |
Source: Db2 for i (AS/400)
Important
Db2 for i is displayed as DB2 for iSeries (AS/400) in the console.
| Source database | Destination database | Synchronization type | Topology | Configuration guide |
|---|---|---|---|---|
| Db2 for i (versions 7.3, 7.4) | Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Document in preparation |
| Db2 for i (versions 7.3, 7.4) | PolarDB for MySQL (all versions) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Document in preparation |
Source: AnalyticDB for MySQL 3.0
Important
The kernel version of the source AnalyticDB for MySQL 3.0 cluster must be 3.2.1.0 or later.
| Source database | Destination database | Synchronization type | Topology | Configuration guide |
|---|---|---|---|---|
| AnalyticDB for MySQL (version 3.0) | AnalyticDB for MySQL (version 3.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data between AnalyticDB for MySQL 3.0 instances |
Source: AnalyticDB for PostgreSQL
Important
The kernel version of the source AnalyticDB for PostgreSQL instance must be 7.2.1.4 or later.
| Source database | Destination database | Synchronization type | Topology | Configuration guide |
|---|---|---|---|---|
| AnalyticDB for PostgreSQL (version 7.0) | AnalyticDB for PostgreSQL (version 7.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data between AnalyticDB for PostgreSQL instances |
| AnalyticDB for PostgreSQL (version 7.0) | Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x) | Full data synchronization, incremental data synchronization | One-way | Synchronize data from AnalyticDB for PostgreSQL to Alibaba Cloud Message Queue for Kafka |
Source: Data Management (DMS) logical database
Important
The DMS logical database must be created from multiple sharded PolarDB for MySQL instances.
| Source database | Destination database | Synchronization type | Topology | Configuration guide |
|---|---|---|---|---|
| Data Management (DMS) logical database | AnalyticDB for MySQL (version 3.0) | Schema synchronization, full data synchronization, incremental data synchronization | One-way | Synchronize data from a Data Management (DMS) logical database to AnalyticDB for MySQL 3.0 |
Source: AWS platform database
| Source database | Destination database | Configuration guide |
|---|---|---|
| AWS platform database | Subject to what is available in the console | Use a VPN gateway to synchronize data between an Alibaba Cloud RDS instance and an AWS EC2 instance |