You can use Data Transmission Service (DTS) to synchronize data between various data sources. The data synchronization feature is applicable to the following scenarios: active geo-redundancy, geo-disaster recovery, zone-disaster recovery, cross-border data synchronization, query load balancing, cloud BI systems, and real-time data warehousing. This topic describes the database types, initial synchronization types, and synchronization topologies that are supported by DTS.
For more information about data synchronization in various scenarios, see Overview of data synchronization scenarios.
Initial synchronization types
Initial synchronization type | Description |
---|---|
Initial schema synchronization |
DTS synchronizes the schemas of the required objects from the source database to the destination database. Tables, views, triggers, and stored procedures can be synchronized. Note Before you configure a data synchronization task, check whether initial schema synchronization
is supported. If initial schema synchronization is not supported, you must create
a destination database and tables based on the schemas of the required objects in
the source database.
|
Initial full data synchronization |
DTS synchronizes historical data of the required objects from the source database to the destination database. Historical data is the basis for subsequent incremental synchronization. To simplify data synchronization, we recommend that you select both initial schema synchronization and initial full data synchronization when you configure a data synchronization task. |
Synchronization topologies
For more information, see Synchronization topologies.
Database types, initial synchronization types, and synchronization topologies
A user-created MySQL or Redis database can be one of the following types:
- User-created database that is hosted on ECS
- User-created database that is connected over Express Connect, VPN Gateway, or Smart Access Gateway
- Database that has no public IP address or port number (connected over Database Gateway)
- User-created database that is connected over Cloud Enterprise Network (CEN)
Source database | Destination database | Initial synchronization type | Synchronization topology |
---|---|---|---|
|
User-created MySQL database Versions 5.1, 5.5, 5.6, 5.7, and 8.0 |
Initial schema synchronization Initial full data synchronization |
One-way synchronization Two-way synchronization |
RDS MySQL All versions |
Initial schema synchronization Initial full data synchronization |
One-way synchronization Two-way synchronization |
|
PolarDB MySQL All versions |
Initial schema synchronization Initial full data synchronization |
One-way synchronization |
|
AnalyticDB for MySQL
Versions 2.0 and 3.0 |
Initial schema synchronization Initial full data synchronization |
One-way synchronization | |
AnalyticDB for PostgreSQL
Versions 4.3 and 6.0 |
Initial schema synchronization Initial full data synchronization |
One-way synchronization | |
Elasticsearch Versions 5.5, 6.3, and 6.7 |
Initial schema synchronization Initial full data synchronization |
One-way synchronization | |
MaxCompute All versions |
Initial schema synchronization Initial full data synchronization |
One-way synchronization | |
User-created Kafka database Versions 0.10 and 1.0 |
Initial schema synchronization Initial full data synchronization |
One-way synchronization | |
DRDS
All versions Note A database in a DRDS instance must be created based on one or more ApsaraDB RDS for
MySQL instances. DTS does not support DRDS databases that are created based on PolarDB
for MySQL clusters.
|
DRDS
All versions Note A database in a DRDS instance must be created based on one or more ApsaraDB RDS for
MySQL instances. DTS does not support DRDS databases that are created based on PolarDB
for MySQL clusters.
|
Initial full data synchronization | One-way synchronization |
AnalyticDB for MySQL
Versions 2.0 and 3.0 |
Initial schema synchronization Initial full data synchronization |
One-way synchronization | |
AnalyticDB for PostgreSQL
Versions 4.3 and 6.0 |
Initial schema synchronization Initial full data synchronization |
One-way synchronization | |
PolarDB MySQL All versions |
User-created MySQL database Versions 5.1, 5.5, 5.6, 5.7, and 8.0 |
Initial schema synchronization Initial full data synchronization |
One-way synchronization |
RDS MySQL All versions |
Initial schema synchronization Initial full data synchronization |
One-way synchronization | |
PolarDB MySQL All versions |
Initial schema synchronization Initial full data synchronization |
One-way synchronization | |
AnalyticDB for MySQL
Versions 2.0 and 3.0 |
Initial schema synchronization Initial full data synchronization |
One-way synchronization | |
User-created Kafka database Versions 0.10 and 1.0 |
Initial schema synchronization Initial full data synchronization |
One-way synchronization | |
Elasticsearch Versions 5.5, 6.3, and 6.7 |
Initial schema synchronization Initial full data synchronization |
One-way synchronization | |
MaxCompute All versions |
Initial schema synchronization Initial full data synchronization |
One-way synchronization | |
PolarDB-O All versions |
PolarDB-O All versions |
Initial schema synchronization Initial full data synchronization |
One-way synchronization |
User-created Kafka database Versions 0.10 and 1.0 |
Initial schema synchronization Initial full data synchronization |
One-way synchronization | |
|
AnalyticDB for PostgreSQL
Versions 4.3 and 6.0 |
Initial full data synchronization | One-way synchronization |
|
|
Initial full data synchronization Note Redis is a NoSQL database that does not require initial schema synchronization.
|
One-way synchronization Two-way synchronization
Note Only ApsaraDB for Redis Enhanced Edition instances (version 5.0) support two-way synchronization.
|