Migrate with tooling - Redis Enterprise to Azure Managed Redis

Azure provides built-in migration tooling that updates your Azure Cache for Redis Enterprise instance into an Azure Managed Redis instance. After the migration completes, your Redis Enterprise hostname will point to an Azure Managed Redis instance, and your client applications reconnect automatically to the Azure Managed Redis instance using the same hostname and access key as your Redis Enterprise instance. Once you validate the migration, update your client applications to use the new Azure Managed Redis hostname.

Use these steps if you choose migration tooling for Enterprise caches using Azure portal.

Step 1: Validate and start migration

1. Add the resource tag amr-migration-data-preserve: false to your Azure Cache for Redis Enterprise instance to explicitly disable best-effort data sync. This tag is required before migration can proceed. We recommend setting the resource tag to False as it will ensure migration is faster with more probability of success. If the data sync is absolutely needed then set the resource tag to True.

   az tag update --resource-id --operation Merge --tags amr-migration-data-preserve=False
   

2. In the Azure portal, use the Resource menu for your Azure Cache for Redis Enterprise instance and select Migrate to Azure Managed Redis from the top level command bar.

   

3. In the migration pane, select the existing Azure Managed Redis SKU to migrate to, then select Migrate. This will start migration process for your Azure Cache for Redis Enterprise instance.

Step 2: During migration

1. During migration, cache status changes to Updating. No other management operations can be performed until migration completes.
2. Your client application will experience a connection blip, similar to maintenance experience. When your client application reconnects, it will connect to Azure Managed Redis instance.

Step 3: Ensure success and delete old Azure Cache for Redis Enterprise hostname

1. After migration completes, validate that your application behaves as expected with the migrated endpoint. Note that the Azure Cache for Redis Enterprise hostname will continue to point to the new Azure Managed Redis instance even after the migration is complete.
2. Update applications to use the Azure Managed Redis hostname (<cachename>.<region>.redis.azure.net) and retire the unused Azure Cache for Redis Enterprise hostname.
   1. If your cache uses private endpoints, add a private endpoint for each virtual network that requires private access. After you update all applications to use the Azure Managed Redis endpoint, verify that every application resolves the Azure Managed Redis hostname and connects through the new private endpoint before you delete the legacy private endpoints.

Frequently asked questions

Do I need to update my automation after migration?

Yes. If you use ARM templates, Bicep templates, SDKs, Azure CLI, or other automation to manage your caches, update the automation to use values from the migrated Azure Managed Redis resource. Review and update properties such as the sku, zones, and capacity because Azure Managed Redis uses different SKU configurations.

Can I roll back to Azure Cache for Redis Enterprise after migration?

No. After the migration to Azure Managed Redis completes successfully using the migration tool, you can't roll back the resource to Azure Cache for Redis Enterprise. Review the available migration options before you start the migration.

Related content

• Migrate from Redis Enterprise to Azure Managed Redis
• Understand the differences
• Plan migration execution
• What is Azure Managed Redis?