TencentDB for Redis®
- Release Notes and Announcements
- Product Introduction
- Product Series
- Purchase Guide
- Getting Started
- Operation Guide
- Access Management
- SDK Connection
- Daily Instance Operation
- Upgrading Redis Edition Instances
- Managing Redis Edition Nodes
- Multi-AZ Deployment Management
- Backup and Restoration
- Downloading Redis Edition Backups
- Data Migration for Redis Edition Instances
- Account and Password (Redis Edition)
- Parameter Configuration
- Redis Parameter Operations
- Network and Security
- Monitoring and Alarms
- Redis Edition Event Management
- Global Replication for Redis Edition
- Performance Optimization
- Development Guidelines
- Connection Pool Configuration
- Command Reference
- Commands Supported by Different Versions
- Additional Command Operations in the Redis Edition
- Troubleshooting
- Connection Exception
- Performance Troubleshooting and Fine-Tuning
- Practical Tutorial
- API Documentation
- Making API Requests
- Instance APIs
- Parameter Management APIs
- Other APIs
- Backup and Restoration APIs
- Monitoring and Management APIs
- Service Agreement
DocumentationTencentDB for Redis®Operation GuideData Migration for Redis Edition InstancesSSDB-to-Redis Data Migration Scheme
SSDB-to-Redis Data Migration Scheme
Last updated: 2024-11-05 10:15:53
How migration works
The Siphon migration tool developed based on Go is disguised as the SSDB slave to subscribe to data and sync the data to Redis.
Siphon is automatically connected to the SSDB server upon startup to perform key addressing. It starts sync from the starting position until all the existing data is synced and then syncs the incremental data. That is to say, the tool establishes a persistent connection after startup and keeps running.
Tool and version descriptions
Migration tool: Siphon. It applies to all SSDB kernel versions.
If SSDB involves big keys or over 100 million keys, you need to submit ticket to obtain the modified Siphon V2 version to improve data synchronization efficiency
Note:
The modified tool solves the problem of inefficiency of the native edition in data sync. In particular, it increases the efficiency in syncing big keys such as hashes and sorted sets (zsets) by about 12 times.
Notes
Migration from SSDB in single-instance mode to Redis Cluster Edition involves logic compatibility issues, such as cross-slot transactions and pipelines.
Migration directions
1. Collect the parameters required to run the migration command as shown below:
-p: Specifies the number of concurrent threads.
-f: Specifies the address of the SSDB server.
-t: Specifies the address of the Redis server.
-T: Specifies the password of the Redis database.
2. Start the migration tool with
siphon_v2 sync and view the migration log../siphon_v2 sync -p 1 –f X.X.X.X:8888 -t X.X.X.x:6379 –T XXX
The status is displayed as follows after the command is executed:
Copy Start: Indicates the start of full data sync.
Copy Stop: Indicates the end of full data sync.
3. Wait for new data to be generated and incrementally synced to Redis without exiting the process.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No