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
Copy file name to clipboardExpand all lines: articles/redis/administration.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ appliesto:
12
12
---
13
13
# How to administer Azure Managed Redis
14
14
15
-
This article describes how to do administration tasks such as [rebooting](#reboot) and [Update channel and Schedule updates](#update-channel-and-schedule-updates) for your Azure Managed Redisinstances.
15
+
This article describes how to do administration tasks such as [rebooting](#reboot) and [Update channel and Schedule updates](#update-channel-and-schedule-updates) for your Azure Managed Redis instances.
@@ -77,17 +77,17 @@ The **Tags** section helps you organize your resources. For more information, se
77
77
78
78
Select **Diagnose and solve problems** to be provided with common issues and strategies for resolving them.
79
79
80
-
## Redis console
80
+
<!--## Redis console
81
81
82
-
Direct access to the Redis console is not yet supported in Azure Managed Redis. Instead, consider using the [Redis CLI](how-to-redis-cli-tool.md) or a tool like [Redis Insight](https://redis.io/insight/).
82
+
Direct access to the Redis console is not yet supported in Azure Managed Redis. Instead, consider using the [Redis CLI](how-to-redis-cli-tool.md) or a tool like [Redis Insight](https://redis.io/insight/).-->
83
83
84
-
## Move your cache to a new subscription
84
+
<!--## Move your cache to a new subscription
85
85
86
86
You can move your cache to a new subscription by selecting **Move**.
For information on moving resources from one resource group to another, and from one subscription to another, see [Move resources to new resource group or subscription](/azure/azure-resource-manager/management/move-resource-group-and-subscription).
90
+
For information on moving resources from one resource group to another, and from one subscription to another, see [Move resources to new resource group or subscription](/azure/azure-resource-manager/management/move-resource-group-and-subscription).-->
91
91
92
92
## Settings
93
93
@@ -123,24 +123,26 @@ Select **Microsoft Entra Authentication** to a password-free authentication mec
123
123
124
124
The following settings are configured on the **Advanced settings** on the left.
<!-- The only settings I see are Non-TLS access, Eviction Policy, Defer Redis DB Version -->
132
+
<!--
131
133
#### Access Ports
132
134
133
135
By default, only TLS access is enabled for new caches. To enable non-TLS access, Select **Enable** for **Non-TLS access only** and then Select **Save**.
134
136
135
137
> [!NOTE]
136
138
> Azure Managed Redis supports TLS 1.2 and 1.3. See [What are the configuration settings for the TLS protocol?](tls-configuration.md) for more details.
137
-
>
139
+
>-->
138
140
139
-
#### Memory policies
141
+
<!--#### Memory policies
140
142
141
-
When you create a cache, approximately 20% of the instance memory is reserved as a memory buffer for replication and other system processes. This helps the instance operate more effectively.
143
+
When you create a cache, approximately 20% of the instance memory is reserved as a memory buffer for replication and other system processes. This helps the instance operate more effectively. -->
142
144
143
-
**Eviction policy** configures the eviction policy for the cache and allows you to choose from the following eviction policies:
145
+
<!--**Eviction policy** configures the eviction policy for the cache and allows you to choose from the following eviction policies:
144
146
145
147
- `volatile-lru`: The default eviction policy. It removes the least recently used key out of all the keys with an expiration set.
146
148
- `allkeys-lru`: Removes the least recently used key.
@@ -151,16 +153,16 @@ When you create a cache, approximately 20% of the instance memory is reserved as
151
153
- `volatile-lfu`: Evicts the least frequently used keys out of all keys with an expire field set.
152
154
- `allkeys-lfu`: Evicts the least frequently used keys out of all keys.
153
155
154
-
For more information, see [Eviction policies](https://redis.io/topics/lru-cache#eviction-policies).
156
+
For more information, see [Eviction policies](https://redis.io/topics/lru-cache#eviction-policies).-->
155
157
156
-
#### Keyspace notifications
158
+
<!--#### Keyspace notifications
157
159
158
160
Redis keyspace notifications are configured using the **notify-keyspace-events** box. Keyspace notifications allow clients to receive notifications when certain events occur.
159
-
Keyspace notifications can be used to [trigger Azure Functions](tutorial-functions-getting-started.md) based on activity on your Redis instance.
161
+
Keyspace notifications can be used to [trigger Azure Functions](tutorial-functions-getting-started.md) based on activity on your Redis instance.
160
162
161
-
For more information, see [Redis Keyspace Notifications](https://redis.io/topics/notifications).
163
+
For more information, see [Redis Keyspace Notifications](https://redis.io/topics/notifications).-->
162
164
163
-
####Data persistence
165
+
### Data persistence (preview)
164
166
165
167
**Data persistence** allows you to enable, disable, or configure data persistence for your Redis instance. Azure Managed Redis offers Redis persistence using either RDB persistence or AOF persistence.
166
168
@@ -176,13 +178,13 @@ For more information, see [Configure disk encryption for Azure Managed Redis ins
176
178
This functionality can be used to replicate a cache across Azure regions, providing greater data durability and availability.
177
179
For more information, see [Configure active geo-replication for Azure Managed Redis instances](how-to-active-geo-replication.md)
178
180
179
-
### Scale
181
+
### Scale (preview)
180
182
181
183
Select **Scale** to view or change the size and performance tier of your Redis instance. For more information on scaling, see [How to Scale Azure Managed Redis](how-to-scale.md).
182
184
183
-
### Schedule updates
185
+
<!--### Schedule updates
184
186
185
-
Scheduled updates are not yet available in Azure Managed Redis.
187
+
Scheduled updates are not yet available in Azure Managed Redis.-->
186
188
187
189
<!--
188
190
The **Schedule updates** section allows you to choose a maintenance window for Redis server updates for your cache.
@@ -198,6 +200,8 @@ To specify a maintenance window, check the days you want. Then, specify the main
198
200
For more information and instructions, see [Update channel and Schedule updates](administration.md#update-channel-and-schedule-updates).
199
201
-->
200
202
203
+
<!-- ### Identity this missing from the list/toc -->
204
+
201
205
### Properties
202
206
203
207
Select **Properties** to view information about your instance, including the endpoint, Redis DB version, and clustering policy.
@@ -217,9 +221,7 @@ The **Administration** section allows you to access and configure the following
217
221
218
222
### Import/Export
219
223
220
-
Import/Export is an Azure Managed Redis data management operation that allows you to import and export data to/from the Redis instance.
221
-
You can import and export a Redis Database (RDB) snapshot to/from an Azure Storage Account.
222
-
Use Import/Export to migrate between different Azure Managed Redis instances or populate the cache with data before use.
224
+
Import/Export is an Azure Managed Redis data management operation that allows you to import and export data to/from the Redis instance. You can import and export a Redis Database (RDB) snapshot to/from an Azure Storage Account. Use Import/Export to migrate between different Azure Managed Redis instances or populate the cache with data before use.
223
225
224
226
You can use import with Redis-compatible RDB files from any Redis server running in virtually any cloud or environment including:
225
227
@@ -229,6 +231,7 @@ You can use import with Redis-compatible RDB files from any Redis server running
229
231
Importing data is an easy way to create a cache with prepopulated data. During the import process, Azure Managed Redis loads the RDB files from Azure storage into memory, and then inserts the keys into the cache.
230
232
231
233
Export allows you to export the data stored in Azure Managed Redis to Redis compatible RDB files. You can use this feature to move data from one Azure Managed Redis instance to another or to another Redis server.
234
+
232
235
During the export process, a temporary file is created on the VM that hosts the Azure Managed Redis instance. The temporary file is uploaded to the designated storage account. When the export operation completes with either a status of success or failure, the temporary file is deleted.
233
236
234
237
For more information and instructions, see [Import and Export data in Azure Managed Redis](how-to-import-export-data.md).
@@ -274,6 +277,7 @@ Further information can be found on the **Recommendations** in the working pane
274
277
### Diagnostic Settings Metrics
275
278
276
279
By default, cache metrics in Azure Monitor are [stored for 30 days](/azure/azure-monitor/essentials/data-platform-metrics) and then deleted.
280
+
277
281
To persist your cache metrics for longer than 30 days, select **Diagnostics Settings - Metrics** to [configure the storage account](monitor-cache.md#data-storage) used to store cache diagnostics.
278
282
279
283
>[!NOTE]
@@ -338,7 +342,7 @@ New Azure Managed Redis instances are configured with the following default Redi
338
342
339
343
### Databases
340
344
341
-
Currently, Azure Managed Redis only supports a single database per instance.
345
+
Currently, Azure Managed Redis only supports a single database per instance.
342
346
343
347
### Maximum number of clients
344
348
@@ -377,7 +381,7 @@ For cache instances using active geo-replication, the following commands are als
377
381
- FLUSHALL
378
382
- FLUSHDB
379
383
380
-
Instead, use the [control plane flush operation](how-to-active-geo-replication.md#flush-operation) through the portal, PowerShell, or CLI.
384
+
Instead, use the [control plane flush operation](how-to-active-geo-replication.md#flush-operation) through the portal, PowerShell, or CLI.
0 commit comments