Migration Tools
Last updated: 2025-05-07 09:47:36
Note:
CTSDB 2.0 and CTSDB 3.0 use different data models. You need to understand some key concepts in CTSDB 3.0. For details, see Key Concepts of TencentDB for CTSDB 3.0.
Migration Tools
Migration Tool | Description | Version and Download |
addax | An offline synchronization tool for heterogeneous data sources, featuring parallel processing, resource optimization, error recovery, fault tolerance, and high scalability. | |
dbversify | A tool for verifying the integrity of data in the database. | |
JDK | - | 1.8 and later |
Data Model Requirements
Note:
The following requirements should be met before data migration to CTSDB 3.0:
Each row of data can be uniquely identified by time + tag. If it cannot be uniquely identified, the data will be overwritten.
The migration granularity of the migration tools is index level. For database-level migration, you need to configure a migration task for each index.
Data write should be stopped for the cluster. Otherwise, data inconsistency may occur.
Data Model Suitable for Migration
With the use of region and timestamp (time column), you can identify a unique data entry. After migration to CTSDB 3.0, region serves as a tag, cpuUsage as a field, and timestamp as the time column, which is compatible with the data model of CTSDB 3.0.
Data Model Not Suitable for Migration
With tag and timestamp (time column) only, you cannot identify a unique data entry. It means that different data entries may have the same time and tag. After migration to CTSDB 3.0, only one data entry will be retained among those with the same time and tag, resulting in data loss.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback