This is the trend and must do work for all legacy Redis cache. Many customers are not very clear on how to map their legacy deployment to latest AMR.
Azure Managed Redis is the next generation of Redis on Azure
Migration ž The basic, standard, and premium tiers will have official 3-year retirement process ž Retirement won’t be initiated until early 2026. ž Enterprise tiers are similar to AMR, so migration process may be shorter. Still TBD. ž Public Preview will have limited migration capabilities (i.e. import/export of data) ž White-glove migration experience after GA (one-click migration).
This blog only document how to map legacy Azure Redis cache to Azure managed Redis (AMR) for future reference.
Feature comparison between Azure Cache for Redis and Azure Managed Redis (preview)
Expand table
|
Feature Description |
Basic |
Standard |
Premium |
Balanced (preview) |
Memory Optimized (preview) |
Compute Optimized (preview) |
|
Availability |
N/A |
99.9% |
99.9% |
N/A |
N/A |
N/A |
|
Data encryption in transit |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Network isolation |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Scaling up/out |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Scaling down/in |
Yes |
Yes |
Yes |
No |
No |
No |
|
OSS clustering |
No |
No |
Yes |
Yes |
Yes |
Yes |
|
Data persistence |
No |
No |
Yes |
Yes |
Yes |
Yes |
|
Zone redundancy |
No |
Yes (preview) |
Yes |
Yes |
Yes |
Yes |
|
Geo-replication |
No |
No |
Yes (Passive) |
Yes (Active) |
Yes (Active) |
Yes (Active) |
|
Connection audit logs |
No |
No |
Yes |
Yes(Event-based) |
Yes(Event-based) |
Yes(Event-based) |
|
Redis Modules |
No |
No |
No |
Yes |
Yes |
Yes |
|
Import/Export |
No |
No |
Yes |
Yes |
Yes |
Yes |
|
Reboot |
Yes |
Yes |
Yes |
No |
No |
No |
|
Scheduled updates |
Yes |
Yes |
Yes |
No |
No |
No |
|
Microsoft Entra ID authentication |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Microsoft Entra ID RBAC |
Yes |
Yes |
Yes |
No |
No |
No |
|
Keyspace notification |
Yes |
Yes |
Yes |
No |
No |
No |
|
Non High-availability |
N/A |
No |
No |
Yes |
Yes |
Yes |
Here are some other differences that aren't covered by the previous mapping. Consider these client application changes:
Expand table
|
Feature Description |
Azure Cache for Redis |
Azure Managed Redis (preview) |
|
DNS suffix (only for PROD cloud) |
.redis.cache.windows.net |
<region>.redis.azure.net |
|
TLS port |
6380 |
10000 |
|
Non-TLS port |
6379 |
Not supported |
|
Individual node TLS ports |
130XX |
85xx |
|
Individual node non-TLS port |
150XX |
Not supported |
|
Clustering support |
OSS clustering mode |
OSS and Enterprise cluster modes |
|
Unsupported commands |
Unsupported commands |
Multi-key commands |
|
Regional availability |
All Azure regions |
* See the list of regions after this section. |
|
Redis version |
6 |
7.4 |
|
Supported TLS versions |
1.2 and 1.3 |
1.2 and 1.3 |
|
Azure Cache for Redis |
Azure Managed Redis |
Additional memory (%) |
|
Basic/Standard - C0 |
Balanced - B0 |
50 |
|
Basic/Standard - C1 |
Balanced - B1 |
0 |
|
Basic/Standard - C2 |
Balanced - B3 |
17 |
|
Basic/Standard - C3 |
Balanced - B5 |
0 |
|
Basic/Standard - C4 |
Memory Optimized – M10* |
-8 |
|
Basic/Standard – C4 |
Memory Optimized – M20** |
46 |
|
Basic/Standard - C5 |
Memory Optimized – M20* |
-8 |
|
Basic/Standard – C5 |
Memory Optimized – M50** |
57 |
|
Basic/Standard - C6 |
Memory Optimized - M50 |
12 |
|
Premium - P1 |
Balanced - B5 |
0 |
|
Premium - P2 |
Balanced - B10* |
-8 |
|
Premium - P2 |
Balanced - B20** |
46 |
|
Premium - P3 |
Balanced - B20* |
-8 |
|
Premium - P3 |
Balanced - B50** |
57 |
|
Premium - P4 |
Balanced - B50 |
12 |
|
Premium - P5 |
Balanced - B100 |
0 |
- *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.
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 (preview) are compatible so no application code changes other than connection configurations are required for most scenarios.
Learn more at:
Options for Migrating Azure Cache for Redis to Azure Managed Redis
Expand table
|
Option |
Advantages |
Disadvantages |
|
Create a new cache |
Simplest to implement. |
Need to repopulate data to the new cache, which might not work with many applications. |
|
Export and import data via RDB file |
Compatible with any Redis cache generally. |
Some data could be lost, if they're written to the existing cache after the RDB file is generated. |
|
Dual-write data to two caches |
No data loss or downtime. Uninterrupted operations of the existing cache. Easier testing of the new cache. |
Needs two caches for an extended period of time. |
|
Migrate data programmatically |
Full control over how data are moved. |
Req |
This can be used as reference for any migration.
Microsoft