Skip to content

Commit 72a7413

Browse files
Merge pull request #287764 from flang-msft/fxl---fix-preview-tag-on-zone-availability-feature
fxl---added preview clarification
2 parents 0216e10 + 0147c1b commit 72a7413

File tree

3 files changed

+17
-11
lines changed

3 files changed

+17
-11
lines changed

articles/azure-cache-for-redis/cache-high-availability.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -61,11 +61,14 @@ Also, Azure Cache for Redis provides more replica nodes in the Premium tier. A [
6161

6262
## Zone redundancy
6363

64-
Applicable tiers: **Standard (preview)**, **Premium (preview)**, **Enterprise**, **Enterprise Flash**
64+
Applicable tiers: **Standard (preview)**, **Premium**, **Enterprise**, **Enterprise Flash**
6565

6666
Recommended for: **High availability**, **Disaster recovery - intra region**
6767

68-
Azure Cache for Redis supports zone redundant configurations in the Standard (preview), Premium (preview), and Enterprise tiers. A [zone redundant cache](cache-how-to-zone-redundancy.md) can place its nodes across different [Azure Availability Zones](../reliability/availability-zones-overview.md) in the same region. It eliminates data center or Availability Zone outage as a single point of failure and increases the overall availability of your cache.
68+
Azure Cache for Redis supports zone redundant configurations in the Standard (preview), Premium, and Enterprise tiers. A [zone redundant cache](cache-how-to-zone-redundancy.md) can place its nodes across different [Azure Availability Zones](../reliability/availability-zones-overview.md) in the same region. It eliminates data center or Availability Zone outage as a single point of failure and increases the overall availability of your cache.
69+
70+
> [!NOTE]
71+
> On the Premium caches, only _automatic zone allocation_ is in public preview. Manual selection of availability zones us unchanged. Manual selection is GA (General Availability).
6972
7073
If a cache is configured to use two or more zones as described earlier in the article, the cache nodes are created in different zones. When a zone goes down, cache nodes in other zones are available to keep the cache functioning as usual.
7174

articles/azure-cache-for-redis/cache-how-to-zone-redundancy.md

Lines changed: 12 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,9 @@ ms.date: 08/05/2024
1111

1212
# Enable zone redundancy for Azure Cache for Redis
1313

14-
In this article, you'll learn how to configure a zone-redundant Azure Cache instance using the Azure portal.
14+
In this article, you learn how to configure a zone-redundant Azure Cache instance using the Azure portal.
1515

16-
Azure Cache for Redis Standard (Preview), Premium (Premium), and Enterprise tiers provide built-in redundancy by hosting each cache on two dedicated virtual machines (VMs). Even though these VMs are located in separate [Azure fault and update domains](/azure/virtual-machines/availability) and highly available, they're susceptible to data center-level failures. Azure Cache for Redis also supports zone redundancy in its Standard (preview), Premium (preview) and Enterprise tiers. A zone-redundant cache runs on VMs spread across multiple [Availability Zones](../reliability/availability-zones-overview.md). It provides higher resilience and availability.
16+
Azure Cache for Redis Standard (preview), Premium, and Enterprise tiers provide built-in redundancy by hosting each cache on two dedicated virtual machines (VMs). Even though these VMs are located in separate [Azure fault and update domains](/azure/virtual-machines/availability) and highly available, they're susceptible to data center-level failures. Azure Cache for Redis also supports zone redundancy in its Standard (preview), Premium, and Enterprise tiers. A zone-redundant cache runs on VMs spread across multiple [Availability Zones](../reliability/availability-zones-overview.md). It provides higher resilience and availability.
1717

1818
## Prerequisites
1919

@@ -36,12 +36,15 @@ To create a cache, follow these steps:
3636
| **Subscription** | Select your subscription. | The subscription under which to create this new Azure Cache for Redis instance. |
3737
| **Resource group** | Select a resource group, or select **Create new** and enter a new resource group name. | Name for the resource group in which to create your cache and other resources. By putting all your app resources in one resource group, you can easily manage or delete them together. |
3838
| **DNS name** | Enter a globally unique name. | The cache name must be a string between 1 and 63 characters that contains only numbers, letters, or hyphens. The name must start and end with a number or letter, and can't contain consecutive hyphens. Your cache instance's *host name* will be *\<DNS name>.redis.cache.windows.net*. |
39-
| **Location** | Select a location. | Select a [region](https://azure.microsoft.com/regions/) near other services that will use your cache. |
39+
| **Location** | Select a location. | Select a [region](https://azure.microsoft.com/regions/) near other services that use your cache. |
4040
| **Cache type** | Select a [Premium or Enterprise tier](https://azure.microsoft.com/pricing/details/cache/) cache. | The pricing tier determines the size, performance, and features that are available for the cache. For more information, see [Azure Cache for Redis Overview](cache-overview.md). |
4141

4242
1. For Standard or Premium tier cache, select **Advanced** in the Resource menu. To enable zone resiliency with automatic zone allocation, select **(Preview) Select zones automatically**.
4343

44-
:::image type="content" source="media/cache-how-to-zone-redundancy/cache-availability-zone.png" alt-text="Screenshot showing the Advanced tab with a red box around Availability zones.:":::
44+
> [!NOTE]
45+
> On the Premium caches, only _automatic zone selection_ is in public preview. Manual selection of availability zones us unchanged. Manual selection is GA (General Availability).
46+
47+
:::image type="content" source="media/cache-how-to-zone-redundancy/cache-availability-zone.png" alt-text="Screenshot showing the Advanced tab with a red box around Availability zones.":::
4548

4649
For an Enterprise tier cache, select **Advanced** in the Resource menu. For **Zone redundancy**, select **Zone redundant (recommended)**.
4750

@@ -53,9 +56,9 @@ To create a cache, follow these steps:
5356
> Automatic Zone Allocation cannot be modified once enabled for a cache.
5457
5558
> [!IMPORTANT]
56-
> Enabling Automatic Zone Allocation is currently NOT supported for Geo Replicated caches or caches with VNET injection.
59+
> Enabling Automatic Zone Allocation (preview) is currently NOT supported for Geo-replicated caches or caches with VNET injection.
5760
58-
1. Availability zones can be selected manually for Premium tier caches. The count of availability zones must always be less than or equal to the Replica count for the cache.
61+
1. Availability zones can be selected manually for Premium tier caches. The number of availability zones must always be less than or equal to the total number of nodes for the cache.
5962

6063
:::image type="content" source="media/cache-how-to-zone-redundancy/cache-premium-replica-count.png" alt-text="Screenshot showing Availability zones set to one and Replica count set to three.":::
6164

@@ -83,11 +86,11 @@ Zone redundancy is available only in Azure regions that have Availability Zones.
8386

8487
### Why can't I select all three zones during cache create?
8588

86-
A Premium cache has one primary and one replica node by default. To configure zone redundancy for more than two Availability Zones, you need to add [more replicas](cache-how-to-multi-replicas.md) to the cache you're creating.
89+
A Premium cache has one primary and one replica node by default. To configure zone redundancy for more than two Availability Zones, you need to add [more replicas](cache-how-to-multi-replicas.md) to the cache you're creating. The total number of availability zones must not exceed the combined count of nodes within the cache, including both the primary and replica nodes.
8790

8891
### Can I update my existing Standard or Premium cache to use zone redundancy?
8992

90-
Yes, updating an existing Standard or Premium cache to use zone redundancy is supported. You can enable it by selecting **Allocate Zones automatically** from the **Advanced settings** on the Resource menu. You cannot disable zone redundancy once you have enabled it.
93+
Yes, updating an existing Standard or Premium cache to use zone redundancy is supported. You can enable it by selecting **Allocate Zones automatically** from the **Advanced settings** on the Resource menu. You can't disable zone redundancy once you enable it.
9194

9295
> [!IMPORTANT]
9396
> Automatic Zone Allocation cannot be modified once enabled for a cache.
@@ -97,7 +100,7 @@ Yes, updating an existing Standard or Premium cache to use zone redundancy is su
97100
98101
### How much does it cost to replicate my data across Azure Availability Zones?
99102

100-
When your cache uses zone redundancy configured with multiple Availability Zones, data is replicated from the primary cache node in one zone to the other node(s) in another zone(s). The data transfer charge is the network egress cost of data moving across the selected Availability Zones. For more information, see [Bandwidth Pricing Details](https://azure.microsoft.com/pricing/details/bandwidth/).
103+
When your cache uses zone redundancy configured with multiple Availability Zones, data is replicated from the primary cache node in one zone to the other nodes in another zone. The data transfer charge is the network egress cost of data moving across the selected Availability Zones. For more information, see [Bandwidth Pricing Details](https://azure.microsoft.com/pricing/details/bandwidth/).
101104

102105
## Next Steps
103106

6.24 KB
Loading

0 commit comments

Comments
 (0)