- Release Notes
- Product Introduction
- Purchase Guide
- Quick Start
- Preparations
- NewDTS
- Databases Supported by Data Migration
- Migration from MySQL to TencentDB for MySQL
- Migration from MariaDB or Percona to TencentDB for MySQL
- Migration from MySQL to TDSQL for MySQL
- Migration from MySQL to TencentDB for MariaDB (Percona)
- Migration from PostgreSQL to TencentDB for PostgreSQL
- Migration from MongoDB to TencentDB for MongoDB
- Migration from SQL Server to TencentDB for SQL Server
- Offline Migration of MySQL Data
- Task Management
- Creating Data Consistency Check Task
- Data Sync
- Data Subscription Kafka Edition
- Data Subscription (Legacy)
- Data Migration (Legacy)
- MySQL Data Migration
- Migrating from Public Network-based External MySQL to TencentDB for MySQL
- Migrating from External MySQL Based on Direct Connect/VPN Gateway to TencentDB for MySQL
- Migrating from CCN-based Self-created MySQL to TencentDB for MySQL
- Migrating from AWS RDS for MySQL to TencentDB for MySQL
- Migrating from AWS Aurora for MySQL to TencentDB for MySQL
- Migrating from Alibaba Cloud RDS for MySQL to TencentDB for MySQL
- Migrating from Alibaba Cloud PolarDB for MySQL to TencentDB for MySQL
- Migration between TencentDB for MySQL Instances
- Online Import of MySQL Data
- Offline Migration of MySQL Data
- Migrating from Alibaba Cloud ApsaraDB for RDS to TencentDB
- Redis Data Migration
- MongoDB Data Migration
- MariaDB Data Migration
- MySQL Data Migration
- Fix for Verification Failure
- Check Item Overview
- Database Connection Check
- Peripheral Check
- Version Check
- Source Database Permission Check
- Partial Database Parameter Check
- Target Database Content Conflict Check
- Target Database Space Check
- Binlog Parameter Check
- Foreign Key Dependency Check
- View Check
- Warning Item Check
- RDS Check
- DLL Ring Sync Check for Single Database/Table Object
- DLL Sync Conflict Check for Single Database/Table Object in the Same Target
- Parameter Configuration Conflict Check
- Incremental Migration Precondition Check
- Extension/Plugin Compatibility Check
- Account Conflict Check
- Oplog Check
- Source Database Balancer Check
- Source Database Node Role Check
- ShardKey Check
- Target Database Load Check
- Local Disk Space Check
- Source Database Existence Check
- Target Database Existence Check
- Migration Network Check
- Cutover Description
- Connection to Cloud Monitor
- Best Practices
- API Documentation
- SDK Documentation
- FAQs
- Release Notes
- Product Introduction
- Purchase Guide
- Quick Start
- Preparations
- NewDTS
- Databases Supported by Data Migration
- Migration from MySQL to TencentDB for MySQL
- Migration from MariaDB or Percona to TencentDB for MySQL
- Migration from MySQL to TDSQL for MySQL
- Migration from MySQL to TencentDB for MariaDB (Percona)
- Migration from PostgreSQL to TencentDB for PostgreSQL
- Migration from MongoDB to TencentDB for MongoDB
- Migration from SQL Server to TencentDB for SQL Server
- Offline Migration of MySQL Data
- Task Management
- Creating Data Consistency Check Task
- Data Sync
- Data Subscription Kafka Edition
- Data Subscription (Legacy)
- Data Migration (Legacy)
- MySQL Data Migration
- Migrating from Public Network-based External MySQL to TencentDB for MySQL
- Migrating from External MySQL Based on Direct Connect/VPN Gateway to TencentDB for MySQL
- Migrating from CCN-based Self-created MySQL to TencentDB for MySQL
- Migrating from AWS RDS for MySQL to TencentDB for MySQL
- Migrating from AWS Aurora for MySQL to TencentDB for MySQL
- Migrating from Alibaba Cloud RDS for MySQL to TencentDB for MySQL
- Migrating from Alibaba Cloud PolarDB for MySQL to TencentDB for MySQL
- Migration between TencentDB for MySQL Instances
- Online Import of MySQL Data
- Offline Migration of MySQL Data
- Migrating from Alibaba Cloud ApsaraDB for RDS to TencentDB
- Redis Data Migration
- MongoDB Data Migration
- MariaDB Data Migration
- MySQL Data Migration
- Fix for Verification Failure
- Check Item Overview
- Database Connection Check
- Peripheral Check
- Version Check
- Source Database Permission Check
- Partial Database Parameter Check
- Target Database Content Conflict Check
- Target Database Space Check
- Binlog Parameter Check
- Foreign Key Dependency Check
- View Check
- Warning Item Check
- RDS Check
- DLL Ring Sync Check for Single Database/Table Object
- DLL Sync Conflict Check for Single Database/Table Object in the Same Target
- Parameter Configuration Conflict Check
- Incremental Migration Precondition Check
- Extension/Plugin Compatibility Check
- Account Conflict Check
- Oplog Check
- Source Database Balancer Check
- Source Database Node Role Check
- ShardKey Check
- Target Database Load Check
- Local Disk Space Check
- Source Database Existence Check
- Target Database Existence Check
- Migration Network Check
- Cutover Description
- Connection to Cloud Monitor
- Best Practices
- API Documentation
- SDK Documentation
- FAQs
DTS supports sync of self-built, TencentDB, and third-party cloud databases. Below are the specific network connection methods:
- Public Network: the source database can be accessed through a public IP.
- Self-Build on CVM: the source database is deployed in a CVM instance.
- Direct Connect: the source database can be interconnected with VPCs through Direct Connect.
- VPN Access: the source database can be interconnected with VPCs through VPN Connection.
- VPC: the source and target databases are both deployed in Tencent Cloud VPCs. The data sync feature supports the VPC access type. To use it, submit a ticket for application.
- Database: the source database is a TencentDB database.
- CCN: the source database can be interconnected with VPCs through CCN.
For a third-party cloud database, you can select Public Network generally or select VPC Access, Direct Connect, or CCN based on your actual network conditions.
Databases that support sync are as detailed below:
| Data Flow Direction | Sync Direction | Source Database | Target Database | Data Initialization Type |
|---|---|---|---|---|
| MySQL > TencentDB for MySQL | To Tencent Cloud | TencentDB for MySQL 5.5, 5.6, 5.7, and 8.0 | ||
| TencentDB for MySQL > PostgreSQL | To Tencent Cloud | TencentDB for MySQL 5.6 and 5.7 | Cloud Data Warehouse PostgreSQL (CDWPG) 1.0.0 | |
| TencentDB for MySQL > TDSQL-A for PostgreSQL | To Tencent Cloud | TencentDB for MySQL 5.6 and 5.7 | TDSQL-A for PostgreSQL | |
| MySQL > TDSQL-C | To Tencent Cloud | TDSQL-C 5.7 | ||
| TDSQL-C > TencentDB for MySQL | To Tencent Cloud | TDSQL-C 5.7 | TencentDB for MySQL 5.7 and 8.0 | |
| TDSQL-C > TDSQL-C | To Tencent Cloud | TDSQL-C 5.7 | TDSQL-C 5.7 | |
| TencentDB for MySQL > local MySQL | From Tencent Cloud | TencentDB for MySQL 5.5, 5.6, 5.7, 8.0 | MySQL 5.5, 5.6, 5.7, and 8.0 | - |
Note：
- "To Tencent Cloud" refers to scenarios where the target database is a Tencent Cloud database product. "From Tencent Cloud" refers to scenarios where the target database isn't a Tencent Cloud database product.
- Sync requirement: at least one of the source and target databases must be a Tencent Cloud database instance.
- The target database version must be above or equal to the source database version.
Yes
No
Was this page helpful?