Plan migration execution - Basic, Standard, and Premium tiers to Azure Managed Redis

This article provides step-by-step instructions for migration paths. We highly recommend performing the migration during off-business hours, as it will result in a brief connectivity blip similar to behavior during regular maintenance operations.

Step 1: Update deployment scripts

Once you have identified the appropriate Azure Managed Redis SKU, update your deployment scripts (such as ARM templates, Bicep files, or Terraform configurations) to provision Azure Managed Redis instead of Azure Cache for Redis.

Step 2: Create a new Azure Managed Redis instance

1. Use the SKU mapping table to select the right size (same size or bigger than the existing cache) and performance tier.
2. Create the instance by following the Quickstart: Create an Azure Managed Redis Instance.

Step 3: Migrate your data

Choose a data migration strategy based on your tolerance for downtime and data loss.

Export and import data using an RDB file

Only supported for Premium tier. Provides a point-in-time snapshot of your data.

• Pros: Simple, compatible with any Redis cache.
• Cons: Data written after the snapshot is taken isn't captured.

Steps:

1. Export the RDB file from the existing Azure Cache for Redis instance using the export instructions or the PowerShell Export cmdlet.
2. Import the RDB file into the new Azure Managed Redis instance using the import instructions or the PowerShell Import cmdlet.
3. Proceed to Step 4: Update your application.

Dual-write strategy

Best when you need zero data loss and can tolerate running two caches temporarily.

• Pros: No data loss, no downtime, uninterrupted operations.
• Cons: Requires running two caches for an extended period.

Steps:

1. Modify your application code to write to both the existing cache and the new Azure Managed Redis instance.
2. Continue reading data from the existing cache until the new instance is sufficiently populated.
3. Update the application code to read and write from the new instance only.
4. Proceed to Step 4: Update your application.

Programmatic migration

RIOT provides a way to migrate content from Enterprise to Azure Managed Redis. For more information, see Data Migration with RIOT-X for Azure Managed Redis.

• Pros: Full control, customizable.
• Cons: Requires development effort.

Steps:

1. Create a VM in the same region as the existing cache. If your dataset is large, choose a powerful VM to reduce copying time.
2. Flush data from the new cache to ensure it's empty. Don't flush the source cache.
3. Copy data from the source cache to the new Azure Managed Redis instance.
4. Proceed to Step 4: Update your application.

Step 4: Update your application

Update your application's connection configuration to point to the new Azure Managed Redis instance. At a minimum, you need to update:

• Hostname: The DNS suffix changes from .redis.cache.windows.net to <region>.redis.azure.net.
• Port: The TLS port changes from 6380 to 10000.
• Access key: Use the access key from the new Azure Managed Redis instance.

Azure Cache for Redis and Azure Managed Redis are compatible, so no application code changes other than connection configurations are required for most scenarios.

Step 5: Validate and decommission

1. Verify your application works correctly with the new Azure Managed Redis instance.
2. Monitor the new cache for expected behavior, performance, and error rates.
3. Once you're confident the new instance is working as expected, delete the old Azure Cache for Redis instance.

Related content

• Migration overview
• Understand the differences
• What is Azure Managed Redis?
• Azure Managed Redis architecture
• Scale an Azure Managed Redis instance