redis
LearnOperateMigrationMemorystore

Learn

Memorystore to Redis Cloud

Before migrating to Redis Cloud, you should evaluate the migration and consider the best option. Read this guide to determine which migration strategy is right for you.

  1. 1.Open Google Cloud Storage bucket.
  2. 2.Create a new bucket to store Memorystore backups.
  3. 3.Under Choose how to control access to objects, uncheck Enforce public access prevention on this bucket
  4. 4.In the Google Cloud Storage bucket, under the Permissions tab, click Grant Access.
  5. 5.In the Grant access menu under Add principals, enter: [email protected]
  6. 6.Under Assign roles, select Cloud Storage ⇒ Storage Object User
  7. 7.Click Save.
  1. 1.In the Redis Cloud console, select the target database from the database list.
  2. 2.Click Import.
  3. 3.Enter the details for the RDB file:
  4. 4.Source type - Select Google Cloud Storage.
  5. 5.Source path - Enter the URL for the RDB file: gs://bucketname/[path/]filename.rdb
  6. 6.For sharded databases with multiple RDB files, select Add source to add another RDB file.
  7. 7.Select Import.
  8. 8.Validate your migration and redirect your application’s traffic to the new Redis Cloud endpoint.

Your Memorystore instance must be accessed from a Compute Engine instance with proper permissions. The following guide assumes that your Memorystore instance is reachable from the internet via a Compute Engine instance.

  1. 1.Go to the Memorystore for Redis page in the Google Cloud console. 
  2. 2.Click the Instance ID of your migration source.
  3. 3.Click Edit.
  4. 4.The Configurations section is now visible. Click click Add Configuration to add a new configuration.
  5. 5.In the configuration dropdown, select notify-keyspace-events
  6. 6.For the Value, enter KEA
  7. 7.Click Save.
  1. 1.Go to the Google Cloud Compute Engine console.
  2. 2.Click Create Instance
  3. 3.For the operating system, Ubuntu is preferred.
  4. 4.Ensure that the Compute Engine instance is created in the same region as your Memorystore instance
  5. 5.Ensure that the Compute Engine instance uses the same Authorized network.
  6. 6.Click Create.

  1. 1.In the Google Cloud Compute Engine console, click SSH to connect to your instance.
  2. 2.Install the redis-cli tool:

3. Verify the connectivity with the Memorystore instance, replace MEMORYSTORE_ENDPOINT with your Memorystore endpoint.

4. Install Java, we recommended using OpenJDK 21 or later:

5. Install RIOT. Download the desired release. Then, unzip the package and make sure the RIOT binaries are in place, as shown here:

6. You can check the version of RIOT by running the command below:

Once Java and RIOT are installed, you are all set to begin the migration process which replicates data directly from the source (Memory) to the target (Redis Cloud). 

  1. 1.Log into the Redis Cloud console.
  2. 2.Click on your migration target and take note of the public endpoint, username, and password
  3. 3.You can replicate the data from Memorystore to Redis Cloud by running the below command: sudo ./riot replicate redis://MEMORYSTORE_ENDPOINT:port redis://username:password@REDIS_CLOUD_ENDPOINT:port --mode live
  4. 4.If you are migrating from a Memorystore cluster, you must include the --source-cluster option
  5. 5.If you are migrating to a Redis Cloud cluster, you must include the --target-cluster option.
  6. 6.Validate your migration and redirect your application’s traffic to the new Redis Cloud endpoint.

Note:

The live replication mechanism does not guarantee data consistency. Redis sends keyspace notifications over pub/sub which does not provide guaranteed delivery. It is possible that RIOT can miss some notifications in case of network failures for example.

Also, depending on the type, size, and rate of change of data structures on the source it is possible that RIOT cannot keep up with the change stream. For example if a big set is repeatedly updated, RIOT will need to read the whole set on each update and transfer it over to the target database. With a big-enough set, RIOT could fall behind and the internal queue could fill up leading up to updates being dropped.

For those potentially problematic migrations it is recommended to perform some preliminary sizing using Redis statistics and bigkeys/memkeys in tandem with --mem-limit. If you need assistance please contact your Redis account team.

For more information, see:

Last updated on Mar 13, 2025
PreviousRedis Community to Redis Cloud
NextElastiCache to Redis Cloud