Migrating Azure Redis Data to Azure Managed Redis
This guide covers migrating data from Azure Cache for Redis to Azure Managed Redis using the Import/Export tool.
Import/Export Tool - All Tiers Supported
When to use: When you need to migrate data between Redis instances. The destination (Azure Managed Redis) supports all tiers; source must have Premium SKU if using Azure Cache for Redis export feature.
How it works: Export from any Redis → Upload to Azure Storage → Import to Azure Managed Redis
Key Features:
All tiers supported - Works with Basic, Standard, Premium, and all Azure Managed Redis tiers
Export stays available - Source Redis remains accessible during export
Import causes downtime - Target cache unavailable during import
Destructive import - All existing data in target cache is deleted before import
Source Requirements:
Azure Cache for Redis: Must have Premium SKU (Basic/Standard tiers do not support export)
Azure Managed Redis: All tiers support export
Target Requirements: - Azure Managed Redis (any tier) - Must be same size or larger than source cache
Step: Export Data from Source Redis (Azure Portal)
If source is Azure Cache for Redis or Azure Managed Redis:
- Navigate to Azure Portal → Your Redis instance
- Select Export data from Resource menu (left sidebar)
- In the working pane, select Choose Storage Container
- Select storage account → Select or create container
- Type a Blob name prefix (e.g.,
migration-backup) - Click Export to start export
Export duration: Varies by cache size and data volume
Step: Verify Export Completed
- Go to Azure Portal → Storage Account → Containers
- Navigate to your container
- Verify RDB file exists:
migration-backup-<timestamp>.rdb.gz - Note the exact blob name for import step
Step: Import Data into Azure Managed Redis (Azure Portal)
- Navigate to Azure Portal → Your Azure Managed Redis instance
- Select Import data from Resource menu (left sidebar)
- Click Choose Blob(s)
- Select the storage account containing your RDB file
- Select the container
- Select one or more blobs to import (checkbox left of blob name)
- Click Select
- Click Import to begin import
Important Warnings: - Cache becomes UNAVAILABLE during import - Applications cannot connect - All existing data DELETED - Target cache is wiped before import begins - No rollback - Once started, the import cannot be undone
Step: Validate Data Imported
# Check key count on new Redis
redis-cli -h $NEW_HOST -p 10000 --tls \
--user default -a $NEW_KEY \
DBSIZE
To inspect the actual keys in the destination instance:
# Connect and list all keys
redis-cli -h $NEW_HOST -p 10000 --tls \
--user default -a $NEW_KEY \
KEYS "*"
# Get a specific key value to verify data integrity
redis-cli -h $NEW_HOST -p 10000 --tls \
--user default -a $NEW_KEY \
GET "your-test-key"
Step: Confirm No Downtime on Source Redis
You can verify that there is no downtime on the source Redis instance by continuously pinging it using the following script:
while true; do
redis-cli -h crumble-recipe-backend-session-storage-sandbox.redis.cache.windows.net \
-p 6380 --tls -a "key" \
PING && echo "$(date): CONNECTED" || echo "$(date): DISCONNECTED"
sleep 2
done
Automation Options:
# PowerShell Export
Export-AzRedisEnterpriseCache -ResourceGroupName <rg> -Name <cache> -StorageContainerUri <uri>
# PowerShell Import
Import-AzRedisEnterpriseCache -ResourceGroupName <rg> -Name <cache> -StorageContainerUri <uri>
# Azure CLI Export
az redisenterprise database export --resource-group <rg> --cluster-name <cache> --sas-uri <uri>
# Azure CLI Import
az redisenterprise database import --resource-group <rg> --cluster-name <cache> --sas-uri <uri>
Documentation: