Migration Solution Notes

DCS console

Supports online migration (in full or incrementally) and backup migration (by importing backup files) with intuitive operations.

• Backup migration is suitable when the source and target Redis instances are not connected, and the source Redis instance does not support the SYNC and PSYNC commands. To migrate data, import your backup files to OBS, and DCS will read data from OBS and migrate the data to the target DCS Redis instance.
• Online migration is suitable when the source Redis instance supports the SYNC and PSYNC commands. Data in the source Redis instance can be migrated in full or incrementally to the target instance.

redis-cli

• The Redis command line interface (CLI), which can be used to export data as an RDB file or import the AOF file (that is, all DBs) of an instance.
• An AOF file is large file containing a full set of data change commands.

-

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.

redis-shake

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.

-

From self-hosted Redis to DCS

DCS console

• If the network between your self-hosted Redis instance and the DCS Redis instance is connected, follow to the instructions in Online Migration of Self-Hosted Redis.
• If the network between your self-hosted Redis instance and the DCS Redis instance is not connected, follow to the instructions in Backup Migration of Self-Hosted Redis.

-

redis-cli

Self-Hosted Redis Migration with redis-cli (AOF)

-

Self-Hosted Redis Migration with redis-cli (RDB)

-

redis-shake

Self-Hosted Redis Cluster Migration with redis-shake

-

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.

• If the network between the source and target DCS Redis instances is connected, follow to the instructions in Online Migration Between Instances.
• If the network between the source and target DCS Redis instances is not connected, follow to the instructions in Backup Import Between Instances.

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 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.

• For details, see Backup Import Between Instances.

• If the DCS Redis instances of the two accounts are connected, you can also follow the instructions in Online Migration Between Instances.

-

From another cloud to DCS

DCS console

• If the SYNC and PSYNC commands are not disabled for the Redis service provided by another cloud, follow the instructions in Online Migration from Another Cloud.
• If the SYNC and PSYNC commands are disabled for the Redis service provided by another cloud, follow the instructions in Backup Import from Another Cloud.

If online migration is required, contact the O&M personnel of another cloud to enable the SYNC and PSYNC commands.

Rump

Online Migration from Another Cloud Using Rump

-

redis-shake

Backup Import from Another Cloud Using redis-shake

-

Online Migration from Another Cloud Using redis-shake

-