You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Regional availability | All Azure regions | * See the list of regions after this section.|
57
+
| Redis version | 6 | 7.4|
58
+
| Supported TLS versions | 1.2 and 1.3 | 1.2 and 1.3|
59
59
60
60
## Regional availability for Azure Managed Redis
61
61
62
62
Azure Managed Redis is current supported in the following regions. This list is updated regularly. Eventually, Azure Managed Redis will be supported all regions in Azure. Work with your sales contact to raise requests on regions where you need support.
63
63
64
-
| Americas | Europe | Middle East | Africa | Asia Pacific |
65
-
|---|---|---|---|---|
66
-
|Brazil South |Germany West Central |||East Asia |
67
-
|West Central US | UK South ||| Australia East |
68
-
|North Central US | West Europe ||| Japan East |
69
-
|West US 3 |Sweden Central |||South East Asia |
70
-
|East US 2 ||||Central India |
71
-
|South Central US |||||
72
-
|West US 2 |||||
73
-
|East US |||||
74
-
|West US |||||
75
-
|Central US |||||
76
-
|Canada Central |||||
64
+
- Americas
65
+
- Brazil South
66
+
- Brazil Southeast
67
+
- Canada Central
68
+
- Canada East
69
+
- Central US
70
+
- East US
71
+
- East US 2
72
+
- Mexico Central
73
+
- North Central US
74
+
- South Central US
75
+
- West Central US
76
+
- West US
77
+
- West US 2
78
+
- West US 3
79
+
80
+
- Europe
81
+
- France South
82
+
- Germany North
83
+
- Germany West Central
84
+
- Italy North
85
+
- Norway East
86
+
- Norway West
87
+
- Spain Central
88
+
- Sweden Central
89
+
- Sweden South
90
+
- Switzerland North
91
+
- Switzerland West
92
+
- Taiwan Northwest
93
+
- UK South
94
+
- UK West
95
+
- West Europe
96
+
97
+
- Middle East
98
+
- Israel Central
99
+
- UAE Central
100
+
- UAE North
101
+
102
+
- Africa
103
+
- South Africa North
104
+
- South Africa West
105
+
106
+
- Asia Pacific
107
+
- East Asia
108
+
- Australia Central
109
+
- Australia Central 2
110
+
- Australia East
111
+
- Australia Southeast
112
+
- Central India
113
+
- Indonesia Central
114
+
- Japan East
115
+
- Japan West
116
+
- Jio India Central
117
+
- Jio India West
118
+
- Korea Central
119
+
- Korea South
120
+
- South East Asia
121
+
- South India
122
+
- Taiwan North
77
123
78
124
## Migrate your Azure Cache for Redis instance to Azure Managed Redis
79
125
@@ -87,24 +133,24 @@ Azure Managed Redis is current supported in the following regions. This list is
87
133
> [!NOTE]
88
134
> Use non High Availability option of Azure Managed Redis for Migrating Basic SKUs
-*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.
110
156
-** This option is for abundant memory consumption.
@@ -124,12 +170,12 @@ Learn more at:
124
170
125
171
#### Options for Migrating Azure Cache for Redis to Azure Managed Redis
126
172
127
-
| Option| Advantages | Disadvantages |
128
-
|------------|----------|-------------|
129
-
| Create a new cache | Simplest to implement. | Need to repopulate data to the new cache, which might not work with many applications. |
130
-
| 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. |
131
-
| 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. |
132
-
| Migrate data programmatically | Full control over how data are moved. | Requires custom code. |
| Create a new cache | Simplest to implement. | Need to repopulate data to the new cache, which might not work with many applications.|
176
+
| 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. |
177
+
| 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.|
178
+
| Migrate data programmatically | Full control over how data are moved. | Requires custom code.|
133
179
134
180
#### Create a new Azure Cache for Redis
135
181
@@ -192,10 +238,10 @@ Create a custom migration process by programmatically reading data from an exist
192
238
General steps to implement this option are:
193
239
194
240
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.
195
-
2. Create a new Azure Managed Redis instance.
196
-
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.
241
+
1. Create a new Azure Managed Redis instance.
242
+
1. 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.
197
243
Important: Make sure to NOT flush from the source cache.
198
-
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.
244
+
1. 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.
0 commit comments