Migrating AWS Elastic Cache for Redis Databases To GeminiDB Redis

Migration Principles

After backing up and exporting the RDB file in AWS ElasticCache for Redis, you can use the Redis-Shake to restore data to GeminiDB Redis.

Precautions

• AWS does not support the psync/sync command and data cannot be incrementally migrated.
• Before the migration, ensure that the network between the ECS where Redis-shake is deployed and the destination GeminiDB Redis is normal.
• Ensure that the security group configuration on the source and target ends is enabled.

Procedure

1. Deploy the required migration tool.
   1. Obtain the redis-shake package.
      

      Download the Redis-Shake release package and decompress it.

   2. Modify the Redis-Shake.conf configuration file and configuring the following items:

      log.level = info #Default log level. A printed INFO log contains migration progress information, based on which you can judge whether the migration is complete.

      source.rdb.input = /xx/xx.rdb # Absolute path of the source RDB file.

      target.address = <host>:8635 # Address for logging in to the destination instance.

      target.password_raw = ***** # Password for logging in to the destination.

      target.version = 5.0 # Version of the destination Redis instance.

      target.type = standalone # Type of the destination instance.

      target.db = 0 #Data is migrated to the specified database of the destination GeminiDB Redis. The default value is db0.

      big_key_threshold = 1 #Setting the big key threshold

   3. Specify whether data of the destination is overwritten.

      key_exists = none

   

   If there are duplicate keys on the source and destination, specify whether data of the destination is overwritten. The options are as follows:

   • rewrite indicates that the source overwrites the destination.
   • none indicates that the migration process exists once duplicate keys are detected.
   • ignore indicates that keys in the source are retained and keys in the destination are ignored. This value does not take effect in rump mode.

   none is recommended. There will be no duplicate data because the source is an RDB file. If the migration process exits unexpectedly, contact technical support.

2. Migrate data.

   Migration starting command:

   ./redis-shake.linux -conf=redis-shake.conf -type=restore

   

   Use the restore mode because the source is an RDB file.

   Stop the migration process after the migration is complete.

3. Verify data.

   Data is obtained from the RDB file. Therefore, you need to check the GeminiDB Redis data at the destination end from the service perspective.