Migration Solution Notes¶
Migration Tools¶
Tool/Command/Service | Feature | Description |
---|---|---|
DCS console | Supports online migration (in full or incrementally) and backup migration (by importing backup files) with intuitive operations. |
|
redis-cli |
|
|
Rump | Supports online migration between DBs of an instance or between DBs of different instances. | Rump does not support incremental migration. Stop services before migrating data. Otherwise, keys might be lost. For details, see Online Migration from Another Cloud Using Rump. |
RedisShake | An open-source tool that supports both online and offline migration. | redis-shake is suitable for migrating Redis Cluster data. |
Self-developed migration script | Flexible and can be adjusted as required. |
|
Migration Schemes¶
Self-hosted Redis refers to self-hosted Redis on this service, in another cloud, or in on-premises data centers.
Scenario | Tool | Use Case | Description |
---|---|---|---|
From self-hosted Redis to DCS | DCS console |
|
|
redis-cli |
| ||
| |||
RedisShake | Self-Hosted Redis Cluster Migration with redis-shake (Online) |
| |
Between DCS instances | DCS console | Migrate data from an earlier-version DCS Redis instance to a later-version DCS Redis instance, for example, from a DCS Redis 3.0 instance to a DCS Redis 4.0/5.0/6.0 instance.
| Attempts to migrate data from a later-version Redis instance to an earlier-version Redis instance are not recommended because they will fail due to data compatibility issues between different Redis versions. |
Migrate Redis data between regions. For details, see Backup Import Between DCS Redis Instances. | The SYNC and PSYNC commands are disabled by default for DCS Redis instances. These commands are enabled for online migration within a region, and remain disabled for online migration between regions. Therefore, you can only use backup migration when migrating DCS Redis instance data between regions. | ||
Migrate Redis data from one account to another.
|
| ||
From another cloud to DCS | DCS console |
| If online migration is required, contact the O&M personnel of another cloud to enable the SYNC and PSYNC commands. |
Rump |
| ||
RedisShake |
| ||
|