Use redis-shake to migrate data under the same account

Prerequisites

• An ApsaraDB for Redis instance is created as the destination of data migration.
• An Elastic Compute Service (ECS) instance is created for running the redis-shake tool.
• The IP address of the ECS instance is added to the whitelists of both the source and destination ApsaraDB for Redis instances.
• The ECS instance is running the Linux operating system.

Background

The redis-shake tool is an open-source tool developed by Alibaba Cloud. You can use it to parse (decode mode), recover (restore mode), back up (dump mode), and synchronize (sync/rump mode) Redis data. In rump mode, the redis-shake tool can scan the source Redis to obtain full data and write the data to the destination Redis to migrate data. This migration solution does not use the SYNC or PSYNC command, and therefore has little impact on the service performance of Redis. It applies to Redis clusters and can be widely used to migrate data between on-premises Redis and ApsaraDB for Redis. This topic describes how to migrate data from an ApsaraDB for Redis instance to another ApsaraDB for Redis instance under the same Alibaba Cloud account.

Procedure

1. Log on to the ECS instance that can access both the source and destination ApsaraDB for Redis instances.
2. Download the redis-shake tool in the ECS instance.
   Note We recommend that you download the latest version.
3. Run the following command to decompress the downloaded redis-shake.tar.gz package:

   # tar -xvf redis-shake.tar.gz

   Note In the decompressed folder, the redis-shake file is a binary file that can be run in the 64-bit Linux operating system. The redis-shake.conf file is the configuration file of the redis-shake tool. You need to modify this configuration file in the next step.
4. Modify the redis-shake.conf file. The following table describes the parameters for the rump mode of the redis-shake tool.

   Table 1. Parameters for the rump mode of redis-shake

   Parameter	Description	Example
   source.address	The connection address and service port of the source ApsaraDB for Redis instance.	r-bp1xxxxxxxxxxxxx.redis.rds.aliyuncs.com
   source.password_raw	The password of the source ApsaraDB for Redis instance.	SourcePass233 Note If you use a database account other than the default database account to connect to the ApsaraDB for Redis instance, set this parameter in the following format: account:password.
   target.address	The connection address and service port of the destination ApsaraDB for Redis instance.	r-j6cxxxxxxxxxxxxx.redis.rds.aliyuncs.com
   target.password_raw	The password of the destination ApsaraDB for Redis instance.	TargetPass233
   rewrite	Specifies whether to overwrite the existing keys in the ApsaraDB for Redis instance that are identical to those in the RDB file. Valid values: true false Note Default value: true. We recommend that you back up the valid data of the destination ApsaraDB for Redis instance before migration. If you set this parameter to false and any keys are duplicate in the source and destination databases, an error message is returned.	true
   scan.key_number	The number of keys that the redis-shake tool obtains each time it scans the source ApsaraDB for Redis instance. If you do not set this parameter, the default value 100 is used.	100
   scan.special_cloud	The cloud of the source Redis instance.	aliyun_cluster Note The example indicates that the data is migrated from the source ApsaraDB for Redis instance of the cluster edition.

5. Run the following command to migrate data:

   # ./redis-shake -type=rump -conf=redis-shake.conf

   Note You must run this command in the same directory as the redis-shake and redis-shake.conf files. Otherwise, you need to specify the correct file path in the command.

   
   
   

   Note When the message framed in red in the preceding figure appears, the data is migrated. After migration is completed, you can use the redis-full-check tool to check whether the data is consistent between the source and destination databases. For more information, see Verify migrated data.