Overview of data migration and synchronization solutions
PolarDB-X 1.0 supports several migration and synchronization solutions. The right choice depends on your source or destination system, data volume, and whether you need continuous synchronization after the initial migration.
How to choose a solution
Use the table below to match your scenario to the appropriate solution. Two capabilities determine which solution fits:
-
Full migration: copies all existing data in one pass
-
Incremental migration: continuously replicates changes after the initial copy — required for live cutovers and ongoing synchronization
| Solution | Scenario | Data volume | Full migration | Incremental migration |
|---|---|---|---|---|
| Data Transmission Service (DTS) | PolarDB-X to PolarDB-X | Large | Yes | Yes |
| DTS | PolarDB-X 1.0 to ApsaraDB RDS for MySQL | Large | No | Yes |
| DTS | PolarDB-X 1.0 to PolarDB MySQL | Large | Yes | Yes |
| Assess data import and export | ApsaraDB RDS to PolarDB-X 1.0 | Large | Yes | Yes |
| MySQL native commands | PolarDB-X 1.0 import/export | Small (fewer than 20 million records) | Yes | No |
| Programming methods | Database or text file import/export | Large | Yes | No |
| Data Integration | MaxCompute (formerly known as ODPS) and PolarDB-X 1.0 | Large | Yes | No |
DTS can only synchronize data from or to PolarDB-X 1.0 databases that are created based on ApsaraDB RDS for MySQL.
Solution details
Data Transmission Service (DTS)
DTS supports both full and incremental synchronization for large datasets, making it the standard choice for live migrations and continuous synchronization.
Supported scenarios:
-
Synchronize data between PolarDB-X instances — full and incremental
-
Synchronize data from a PolarDB-X 1.0 instance to an ApsaraDB RDS for MySQL instance — incremental only
-
Synchronize data from a PolarDB-X 1.0 instance to a PolarDB for MySQL cluster — full and incremental
Limitation: Only works with PolarDB-X 1.0 databases created based on ApsaraDB RDS for MySQL.
Assess data import and export
Use this solution to migrate data from an ApsaraDB RDS instance to a PolarDB-X 1.0 instance. Supports large datasets and both full and incremental migration.
MySQL native commands
Use the source command to import SQL files into PolarDB-X 1.0, or mysqldump to export SQL files from PolarDB-X 1.0. For detailed steps, see Import and export data by using mysqldump.
Limitation: Suitable for datasets with fewer than 20 million records only. For larger datasets, use DTS or programming methods.
Programming methods
Import data from a database or text file into PolarDB-X 1.0, or export data from PolarDB-X 1.0 to a database or text file. Handles large datasets but supports full migration only — no incremental synchronization. For detailed steps, see Import big data through a program.
Data Integration
Move data between MaxCompute (formerly known as ODPS) and PolarDB-X 1.0 in either direction. Handles large datasets but supports full migration only. For detailed steps, see the Data Integration overview.
Limitation: Supports full migration only — no incremental synchronization.
Next steps
After selecting a solution, follow the linked guide for step-by-step instructions. If you need ongoing synchronization after migration, use DTS — the only solution in this list that supports incremental replication.