You can use Data Transmission Service (DTS) to migrate data between homogeneous and heterogeneous data sources. Typical scenarios include data migration to Alibaba Cloud, data migration between instances within Alibaba Cloud, and database splitting and scale-out. This topic describes the database types, database versions, and migration types that are supported by the data migration feature. This topic also provides links to the relevant references.
- The data migration feature can achieve data synchronization in specific scenarios. However, data migration and data synchronization differ in scenarios, supported databases, features, and billing. For more information, see What are the differences between data migration and data synchronization?
- DTS can read the instances that are created in an ApsaraDB for MyBase cluster. The topics listed in the following table are also applicable to migration scenarios for ApsaraDB for MyBase clusters. For example, you can migrate data from a self-managed MySQL database to an ApsaraDB RDS for MySQL instance that is created in an ApsaraDB for MyBase cluster.
Migration types
| Migration type | Description |
|---|---|
| Schema migration |
DTS migrates the schemas of the required objects from the source database to the destination database. Tables, views, triggers, and stored procedures can be migrated. For schema migration between heterogeneous databases, DTS converts the schema syntax based on the syntax of the source and destination databases. For example, it converts the NUMBER data type in Oracle databases into the DECIMAL data type in MySQL databases. |
| Full data migration | DTS migrates historical data of the required objects from the source database to the
destination database. If you select only Schema Migration and Full Data Migration
as the migration types, DTS does not migrate incremental data generated in the source
database.
Note To ensure data consistency, we recommend that you do not write data to the source
database during full data migration. To ensure service continuity, you must select
Schema Migration, Full Data Migration, and Incremental Data Migration when you configure a data migration task.
|
| Incremental data migration | DTS retrieves static snapshots that are used for full data migration from the source
database, and migrates the snapshot data to the destination database. Then, DTS synchronizes
incremental data generated in the source database to the destination database.
Note During incremental data migration, data is synchronized between the source and destination
databases in real time. The migration task does not automatically stop. You must manually
stop the migration task.
|
Supported databases and migration types
A self-managed MySQL, SQL Server, or Oracle database can be one of the following types:
- Self-managed database with a public IP address
- Self-managed database that has no public IP address or port number (connected over Database Gateway)
- Self-managed database that is connected over Cloud Enterprise Network (CEN)
- Self-managed database that is hosted on Elastic Compute Service (ECS)
- Self-managed database that is connected over Express Connect, VPN Gateway, or Smart Access Gateway
| Source database | Destination database | Migration type |
|---|---|---|
|
Self-managed MySQL database Version 5.1, 5.5, 5.6, 5.7, or 8.0 |
|
|
ApsaraDB RDS for MySQL All versions |
|
|
|
PolarDB for MySQL All versions |
|
|
|
PolarDB-X 1.0 All versions Note The databases in the PolarDB-X 1.0 instance must be created based on ApsaraDB RDS for MySQL instances. DTS does not
support DRDS databases that are created based on PolarDB for MySQL clusters.
|
|
|
|
AnalyticDB for PostgreSQL Version 4.3 or 6.0 |
|
|
|
AnalyticDB for MySQL Version 2.0 or 3.0 |
|
|
|
|
|
|
Self-managed Oracle database (RAC or non-RAC architecture) Version 9i, 10g, 11g, 12c, 18c, or 19c |
|
|
|
Message Queue for Apache Kafka Version 0.10.1.0 to 2.x Self-managed Kafka cluster Version 0.10.1.0 to 2.7.0 |
|
|
|
|
|
|
ApsaraDB RDS for MariaDB TX Version 10.3 |
ApsaraDB RDS for MariaDB TX Version 10.3 |
|
|
ApsaraDB RDS for MySQL All versions |
|
|
|
Self-managed MySQL database Version 5.1, 5.5, 5.6, 5.7, or 8.0 |
|
|
| ApsaraDB RDS for PPAS
All versions |
PolarDB O Edition All versions |
|
|
PolarDB for MySQL All versions |
PolarDB for MySQL All versions |
|
|
Self-managed MySQL database Version 5.1, 5.5, 5.6, 5.7, or 8.0 |
|
|
|
ApsaraDB RDS for MySQL All versions |
|
|
|
PolarDB-X 1.0 All versions Note The databases in the PolarDB-X 1.0 instance must be created based on ApsaraDB RDS for MySQL instances. DTS does not
support DRDS databases that are created based on PolarDB for MySQL clusters.
|
|
|
|
AnalyticDB for MySQL Version 3.0 Note You can configure a data migration task for this scenario only in the DTS console
of the new version.
|
|
|
|
Self-managed Oracle database (RAC, PDB, or non-RAC architecture) Version 9i, 10g, 11g, 12c, 18c, or 19c |
|
|
|
PolarDB O Edition All versions |
PolarDB O Edition All versions |
|
|
Self-managed Oracle database (RAC or non-RAC architecture) Version 9i, 10g, 11g, 12c, 18c, or 19c |
|
|
|
Message Queue for Apache Kafka Versions 0.10.1.0 to 2.x Self-managed Kafka cluster Versions 0.10.1.0 to 2.7.0 |
|
|
|
PolarDB PostgreSQL Version 11 |
Self-managed Oracle database (RAC or non-RAC architecture) Version 9i, 10g, 11g, 12c, 18c, or 19c |
|
|
MaxCompute All versions |
|
|
|
Self-managed SQL Server database Version 2005, 2008, 2008 R2, 2012, 2014, 2016, or 2017 Note DTS does not support SQL Server clusters or SQL Server Always On availability groups
(AOAGs).
|
|
|
ApsaraDB RDS for SQL Server Version 2008, 2008 R2, 2012, 2014, 2016, or 2017 |
|
|
| ApsaraDB RDS for SQL Server
Version 2008, 2008 R2, 2012, 2014, 2016, or 2017 Note If the version of the source database is 2008 or 2008 R2, incremental data migration
is not supported.
|
AnalyticDB for MySQL
Version 2.0 or 3.0 |
|
|
Self-managed Oracle database (RAC or non-RAC architecture) Version 9i, 10g, 11g, 12c, 18c, or 19c |
Self-managed Oracle database (RAC or non-RAC architecture) Version 9i, 10g, 11g, 12c, 18c, or 19c |
|
|
PolarDB O Edition All versions |
|
|
|
ApsaraDB RDS for PPAS Version 9.3 or 10 |
|
|
|
Self-managed MySQL database Version 5.1, 5.5, 5.6, 5.7, or 8.0 |
|
|
|
ApsaraDB RDS for MySQL All versions |
|
|
|
PolarDB for MySQL All versions |
|
|
|
PolarDB-X 1.0 All versions Note The databases in the PolarDB-X 1.0 instance must be created based on ApsaraDB RDS for MySQL instances. DTS does not
support DRDS databases that are created based on PolarDB for MySQL clusters.
|
|
|
|
AnalyticDB for MySQL Version 2.0 or 3.0 |
|
|
|
AnalyticDB for PostgreSQL Version 4.3 or 6.0 |
|
|
|
Message Queue for Apache Kafka Version 0.10.1.0 to 2.x Self-managed Kafka cluster Version 0.10.1.0 to 2.7.0 |
|
|
|
PolarDB PostgreSQL Version 11 |
|
|
|
|
|
|
Note You can configure a data migration task for this scenario only in the DTS console
of the new version.
|
|
|
|
|
|
PolarDB O Edition All versions Note You can configure a data migration task for this scenario only in the DTS console
of the new version.
|
|
|
|
|
Note
|
|
Self-managed Redis database (standalone architecture) Version 2.8, 3.0, 3.2, 4.0, 5.0, or 6.0 |
Self-managed Redis database (standalone or cluster architecture) Version 2.8, 3.0, 3.2, 4.0, 5.0, or 6.0 |
Note Redis is a NoSQL database that does not require schema migration.
|
|
ApsaraDB for Redis instance (standalone or cluster architecture) Community Edition 4.0, 5.0, or 6.0 |
|
|
| Self-managed TiDB database |
Self-managed MySQL database Version 5.1, 5.5, 5.6, 5.7, or 8.0 |
|
|
ApsaraDB RDS for MySQL All versions |
|
|
|
PolarDB for MySQL All versions |
|
|
|
|
|