Migrate from Basic, Standard, and Premium tiers to Azure Managed Redis

This article explains why and how to migrate from Azure Cache for Redis (including Basic, Standard, and Premium tiers) to Azure Managed Redis.

You learn about:

• The benefits of choosing Azure Managed Redis over previous tiers.
• Key feature differences between the services.
• Strategies for migrating your cache data.
• Ways to ensure a smooth migration process.
• Guidance on selecting the right Azure Managed Redis SKU and performance tier for your needs.
• Considerations and recommendations for updating your client applications.

Whether you're using Basic, Standard, Premium, or OSS tiers, this guide helps you plan and execute your migration to Azure Managed Redis.

Benefits of moving from Basic, Standard, or Premium caches to Azure Managed Redis

If you use any of the OSS SKUs, Basic, Standard, or Premium, moving to Azure Managed Redis offers you more features at every level cache.

Here's a table that compares the features from Azure Cache for Redis to the features in Azure Managed Redis

OSS refers to Azure Cache for Redis
AMR refers to Azure Managed Redis

Here are some other differences to consider when implementing Azure Managed Redis. Consider these client application changes:

Migrate your Basic, Standard, or Premium cache to Azure Managed Redis

Based on the table, here are some mappings between the Azure Cache for Redis SKUs and options for caches in Azure Managed Redis.

• * This option is for cost efficiency. Ensure the peak of total used memory in the past month is less than the suggested Azure Managed Redis memory to choose this option.
• ** This option is for abundant memory consumption.

Azure Cache for Redis Premium clustered

• For sharded cluster, choose a Memory Optimized tier that has equivalent total memory.
• For clusters with more than one read replica, choose a Compute Optimized tier with equivalent total memory as the primary replica.

Migration options

Client applications should be able to use an Azure Managed Redis instance that has different clustering modes and endpoints. Azure Cache for Redis and Azure Managed Redis are compatible so no application code changes other than connection configurations are required for most scenarios.

Learn more at:

• Scale an Azure Managed Redis instance

Options for Migrating Azure Cache for Redis to Azure Managed Redis

Create a new Azure Cache for Redis

This approach technically isn't a migration. If losing data isn't a concern, the easiest way to move to Azure Managed Redis tier is to create new cache instance and connect your application to it. For example, if you use Redis as a look-aside cache of database records, you can easily rebuild the cache from scratch. General steps to implement this option are:

1. Create a new Azure Managed Redis instance.
2. Update your application to use the new instance.
3. Delete the old Azure Cache for Redis instance.

Export data to an RDB file and import it into Azure Managed Redis

This option is applicable only to premium tier caches. Open-source Redis defines a standard mechanism for taking a snapshot of a cache's in-memory dataset and saving it to a file. Another Redis cache can read the RDB file that was exported. Azure Cache for Redis premium tier supports exporting data from a cache instance via RDB files. You can use an RDB file to transfer data from an existing Azure Cache for Redis instance to Azure Managed Redis instance.

General steps to implement this option are:

1. Create a new Azure Managed Redis instance that is the same size (or bigger than) the existing Azure Cache for Redis instance.
2. Export the RDB file from existing Azure Cache for Redis instance using these export instructions or the PowerShell Export cmdlet
3. Import the RDB file into new Azure Managed Redis instance using these import instructions or the PowerShell Import cmdlet
4. Update your application to use the new Azure Managed Redis instance connection string.

Write to two Redis caches simultaneously during migration period

Rather than moving data directly between caches, you can use your application to write data to both an existing cache and a new one you're setting up. The application still reads data from the existing cache initially. When the new cache has the necessary data, you switch the application to that cache and retire the old one. Let's say, for example, you use Redis as a session store and the application sessions are valid for seven days. After writing to the two caches for a week, you'll be certain the new cache contains all nonexpired session information. You can safely rely on it from that point onward without concern over data loss.

General steps to implement this option are:

1. Create a new Azure Managed Redis instance that is the same size as (or bigger than) the existing Azure Cache for Redis instance.
2. Modify application code to write to both the new and the original instances.
3. Continue reading data from the original instance until the new instance is sufficiently populated with data.
4. Update the application code to reading and writing from the new instance only.
5. Delete the original instance.

Migrate programmatically

Create a custom migration process by programmatically reading data from an existing Azure Cache for Redis instance and writing them into Azure Managed Redis instance. There are two open source tools you can try:

• Redis-copy
  • This open-source tool can be used to copy data from one Azure Cache for Redis instance to another. This tool is useful for moving data between cache instances in different Azure Cache regions. A compiled version is available as well. You can also find the source code to be a useful guide for writing your own migration tool.
• RIOT
  • RIOT is another popular migration tool tested by Redis community. It's a command-line utility designed to help you get data in and out of Redis.

General steps to implement this option are:

1. Create a VM in the region where the existing cache is located. If your dataset is large, choose a relatively powerful VM to reduce copying time.
2. Create a new Azure Managed Redis instance.
3. Flush data from the new cache to ensure that it's empty. This step is required because the copy tool itself doesn't overwrite any existing key in the target cache. Important: Make sure to NOT flush from the source cache.
4. Use an application such as the open-source tool mentioned previously to automate the copying of data from the source cache to the target. Remember that the copy process could take a while to complete depending on the size of your dataset.

Regional availability for Azure Managed Redis

Azure Managed Redis is continually expanding into new regions. To check the availability by region, see Products available by region.

Related content

• What is Azure Managed Redis?
• Azure Managed Redis architecture