Data Transmission Service (DTS) is a data transfer service that integrates such features as data migration, sync, and subscription, helping you migrate your databases without interrupting your business and build a high-availability database architecture for remote disaster recovery through real-time sync channels. Its data subscription feature grants you real-time access to incrementally updated data in your TencentDB instance, so that you can consume such data based on your business needs. Currently, DTS for Redis supports data migration on different versions of Redis and in various network scenarios.
|Source instance||Source instance to be migrated.|
|Target instance||Target instance to be migrated to, i.e., user-purchased TencentDB for Redis.|
|CVM-based self-created database||Redis service deployed on a CVM instance.|
|Public network-based self-created database||Redis service deployed on the public network.|
For compatibility issues with migration from Standalone Edition to Memory Edition (Cluster Architecture), please see Notes on Migration from Standalone Edition to Cluster Edition.
DTS supports data migration and data sync in common scenarios, such as public network-based, CVM-based self-created, Direct Connect-based, VPN-based, and CCN-based databases.
| Target Instance
|2.8 Memory Edition (Standard Architecture)||4.0 Memory Edition (Standard Architecture)||4.0 Memory Edition (Cluster Architecture)||5.0 Memory Edition (Standard Architecture)||5.0 Memory Edition (Cluster Architecture)|
|2.8 Memory Edition (Standard Architecture)||✓||✓||✓||✓||✓|
|4.0 Memory Edition (Standard Architecture)||x||✓||✓||✓||✓|
|4.0 Memory Edition (Cluster Architecture)||x||✓||✓||✓||✓|
|5.0 Memory Edition (Standard Architecture)||x||✓||✓||✓||✓|
|5.0 Memory Edition (Cluster Architecture)||x||✓||✓||✓||✓|
1) Log in to the DTS Console and click Create Migration Task on the data migration page.
2) Select the corresponding region in Linkage Region and click Buy at 0 CNY.
- To modify the scheduled task, you must click Scheduled Start again after the check is passed, so as to make the task start at the specified time.
- If the specified time has passed, the task will start immediately. You can also click Start Now to start the task immediately.
Redis instances on CVM are used here as an example, and the same is true for migration of instances over the public network.
|Task name||Migration task name||Facilitates task management||Yes|
|CVM instance ID||ID of the CVM instance where the source Redis instance resides||The migration task checks the CVM running conditions based on the CVM instance ID||Yes|
|CVM private IP||Private IP of the CVM instance where the source Redis instance resides||The migration task checks the CVM private IP||Yes|
|Port||Port number of the source instance||The migration task will access the source instance||Yes|
|Password||Source instance password||The password is used for authentication for accessing the source instance||No|
|Instance ID||Target instance ID||Data is synced to the target instance||Yes|
Notes on migration in the Cluster Edition
DTS supports migration in the Redis Cluster Edition. For cluster schemes with the Redis Cluster, Codis, or twemproxy architecture, simply enter the addresses and passwords of all shard nodes of the source cluster as the node information when creating the task. It is strongly recommended to perform data migration from a replica node (slave) of the source instance to avoid any impact on business access to the source instance. DTS supports password-free migration. The following is an example for entering relevant information for migration:
1) After the network connectivity test is successful, click Save.
2) DTS begins to verify the migration task, and once the migration requirements are met, the migration task will be started.
3) Upon task start, the task status will change to Verifying, indicating that another round of parameter verification is underway. During this process, you are only able to cancel or view the task or check the verification progress.
4) After parameter verification is successful, data migration will start.
During data sync, changes in data offset, source instance, and target instance key will be displayed.
DTS supports migration interruption alarming to keep you informed of any exceptions. A migration alarm can be configured as follows:
1) Log in to the Cloud Monitor Console and select Alarm Configuration > Alarm Policy on the left sidebar.
2) Click Create to create an alarm policy.
Before disabling data sync, the data can be verified on the target instance, and if everything is correct, the migration task can be completed.
If the keys of the source instance and the target instance are identical, click Complete to finish data sync.