Skip to content

Commit cace3d6

Browse files
committed
Squashed commit of the following:
commit 5701791 Author: flang-msft <[email protected]> Date: Tue May 13 11:07:07 2025 -0700 created redirect commit 582e3c1 Author: flang-msft <[email protected]> Date: Tue May 13 11:02:59 2025 -0700 Fixed broken link commit 0f9983b Author: flang-msft <[email protected]> Date: Tue May 13 10:32:33 2025 -0700 removed unused file commit 8fd94ee Merge: de7fe81 b34633f Author: Langlois,FX <[email protected]> Date: Mon May 12 16:46:32 2025 -0700 Merge branch 'main' into fxl---managed-redis-GA-preview commit de7fe81 Author: flang-msft <[email protected]> Date: Mon May 12 15:39:22 2025 -0700 Fix broken links commit 9476ef0 Merge: 9711faa 4f37573 Author: flang-msft <[email protected]> Date: Mon May 12 15:07:16 2025 -0700 Merge branch 'main' into fxl---managed-redis-GA-preview commit 9711faa Author: flang-msft <[email protected]> Date: Mon May 12 14:05:48 2025 -0700 Remove bogus entries
1 parent 3bfb1c9 commit cace3d6

10 files changed

+14
-135
lines changed

articles/redis/.openpublishing.redirection.redis.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,11 @@
55
"source_path_from_root": "/articles/redis/administration.md",
66
"redirect_url": "/azure/redis/configure",
77
"redirect_document_id": false
8+
},
9+
{
10+
"source_path_from_root": "/articles/redis/high-availability.md",
11+
"redirect_url": "/azure/azure-cache-for-redis/cache-high-availability",
12+
"redirect_document_id": false
813
}
914
]
1015
}

articles/redis/TOC.yml

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,6 @@ items:
1616
href: quickstart-create-managed-redis.md
1717
- name: Create an Azure Cache for Redis instance in the Basic, Standard and Premium tiers
1818
href: ../azure-cache-for-redis/quickstart-create-redis.md
19-
- name: Create an Azure Cache for Redis instance in the Enterprise tiers
20-
href: ../azure-cache-for-redis/quickstart-create-redis-enterprise.md
2119
- name: Create and manage with Azure PowerShell
2220
href: how-to-manage-redis-cache-powershell.md
2321
- name: Create and manage with Azure CLI
@@ -167,11 +165,12 @@ items:
167165
items:
168166
- name: Persist your cache with Redis data persistence
169167
href: how-to-persistence.md
170-
- name: Set up Enterprise active geo-replication
168+
- name: Set up active geo-replication
171169
href: how-to-active-geo-replication.md
172170
- name: Failover and patching
173171
href: failover.md
174172

173+
175174
- name: Diagnose and troubleshoot
176175
items:
177176
- name: Troubleshoot connectivity issues

articles/redis/best-practices-managed-cache.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Here are some best practices for Azure Managed Redis.
1515

1616
## Zone redundancy
1717

18-
We strongly recommend that you deploy new caches in a [zone redundant](high-availability.md) configuration. Zone redundancy ensures that Redis Enterprise nodes are spread among three availability zones, boosting redundancy from data center-level outages. Using zone redundancy increases availability. For more information, see [Service Level Agreements (SLA) for Online Services](https://azure.microsoft.com/support/legal/sla/cache/v1_1/).
18+
We strongly recommend that you deploy new caches in a zone redundant configuration. Zone redundancy ensures that Redis Enterprise nodes are spread among three availability zones, boosting redundancy from data center-level outages. Using zone redundancy increases availability. For more information, see [Service Level Agreements (SLA) for Online Services](https://azure.microsoft.com/support/legal/sla/cache/v1_1/).
1919

2020
Zone redundancy is important on the Enterprise tier because your cache instance always uses at least three nodes. Two nodes are data nodes, which hold your data, and a _quorum node_. Increasing capacity scales the number of data nodes in even-number increments.
2121

articles/redis/high-availability.md

Lines changed: 0 additions & 116 deletions
This file was deleted.

articles/redis/how-to-active-geo-replication.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -262,4 +262,3 @@ Manage access to the feature using [Azure role-based access control](/azure/role
262262
## Next steps
263263

264264
- [Azure Managed Redis service tiers](overview.md#choosing-the-right-tier)
265-
- [High availability for Azure Cache for Redis](high-availability.md)

articles/redis/how-to-manage-redis-cache-powershell.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,6 @@
22
title: Manage Azure Redis with Azure PowerShell
33
description: Learn how to create and perform administrative tasks for Azure Redis using Azure PowerShell.
44
ms.date: 05/18/2025
5-
65
ms.topic: conceptual
76
ms.custom:
87
- devx-track-azurepowershell

articles/redis/how-to-persistence.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.custom:
1111
---
1212
# Configure data persistence (preview) for an Azure Managed Redis instance
1313

14-
[Redis persistence (preview)](https://redis.io/topics/persistence) allows you to persist data stored in cache instance. If there's a hardware failure, the cache instance is rehydrated with data from the persistence file when it comes back online. The ability to persist data is an important way to boost the durability of a cache instance because all cache data is stored in memory. Data loss is possible if a failure occurs when cache nodes are down. Persistence should be a key part of your [high availability and disaster recovery](high-availability.md) strategy with Azure Managed Redis.
14+
[Redis persistence (preview)](https://redis.io/topics/persistence) allows you to persist data stored in cache instance. If there's a hardware failure, the cache instance is rehydrated with data from the persistence file when it comes back online. The ability to persist data is an important way to boost the durability of a cache instance because all cache data is stored in memory. Data loss is possible if a failure occurs when cache nodes are down. Persistence should be a key part of your high availability and disaster recovery strategy with Azure Managed Redis.
1515

1616
> [!IMPORTANT]
1717
>
@@ -187,4 +187,3 @@ For more information on scaling, see [What happens if I've scaled to a different
187187

188188
- [Azure Managed Redis service tiers](overview.md#choosing-the-right-tier)
189189
- [Export data from Azure Managed Redis](how-to-import-export-data.md)
190-
- [High availability and disaster recovery](high-availability.md)

articles/redis/index.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -87,8 +87,6 @@ landingContent:
8787
url: how-to-redis-cli-tool.md
8888
- linkListType: concept
8989
links:
90-
- text: High availability
91-
url: high-availability.md
9290
- text: Storing embeddings vectors and performing vector similarity search
9391
url: overview-vector-similarity.md
9492
- text: Redis modules

articles/redis/scripts/create-manage-cache.md

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,11 @@
22
title: Create, query, and delete a cache using Azure CLI
33
description: Use the Azure CLI to create an Azure Redis instance, get cache details like status, hostname, ports, and keys, and delete the cache.
44
ms.devlang: azurecli
5-
ms.date: 05/18/2025
65
ms.topic: sample
7-
zone_pivot_groups: redis-type
86
ms.date: 05/18/2025
9-
ms.custom:
10-
- devx-track-azurecli
11-
- ignite-2024
12-
- build-2025
7+
zone_pivot_groups: redis-type
8+
ms.custom:
9+
- devx-track-azurecli, ignite-2024, build-2025
1310
appliesto:
1411
- ✅ Azure Managed Redis
1512
- ✅ Azure Cache for Redis
@@ -45,8 +42,8 @@ You can use the Azure CLI script in this section to create an Azure Managed Redi
4542

4643
- [Azure portal](../quickstart-create-managed-redis.md)
4744
- [Azure PowerShell](../how-to-manage-redis-cache-powershell.md?pivots=azure-managed-redis)
48-
- [ARM template](../redis-cache-arm-provision.md#azure-managed-redis-preview)
49-
- [Bicep template](../redis-cache-bicep-provision.md#azure-managed-redis-preview)
45+
- [ARM template](../redis-cache-arm-provision.md#azure-managed-redis)
46+
- [Bicep template](../redis-cache-bicep-provision.md#azure-managed-redis)
5047

5148
The cache `name` must be a string of 1-63 characters that's unique in the [Azure region](https://azure.microsoft.com/regions/). The name can contain only numbers, letters, and hyphens, must start and end with a number or letter, and can't contain consecutive hyphens.
5249

articles/redis/troubleshoot-connectivity.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,4 +90,3 @@ If you've configured any networking or security resource to use your cache's pub
9090
## Related content
9191

9292
- [Best practices for connection resilience](best-practices-connection.md)
93-
- [High availability for Azure Managed Redis](high-availability.md)

0 commit comments

Comments
 (0)