Skip to content

Commit c429e22

Browse files
authored
Merge pull request #301943 from johndowns/reliability-queue-1
Reliability guide: Azure Queue Storage
2 parents 483abd3 + d6619ae commit c429e22

File tree

37 files changed

+661
-0
lines changed

37 files changed

+661
-0
lines changed

articles/reliability/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -293,6 +293,8 @@
293293
href: reliability-elastic-san.md
294294
- name: Azure NetApp Files
295295
href: ../azure-netapp-files/cross-region-replication-manage-disaster-recovery.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
296+
- name: Azure Queue Storage
297+
href: reliability-storage-queue.md
296298
- name: Azure Storage Actions
297299
href: reliability-storage-actions.md
298300
- name: Azure Storage-Disk Storage

articles/reliability/availability-zones-service-support.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,7 @@ Some Azure services are *nonregional*, which means that you don't deploy the ser
8080
| [Azure Notification Hubs](reliability-notification-hubs.md) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | |
8181
| [Azure Private Link](../private-link/private-link-overview.md) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false":::||
8282
| [Azure Public IP](../virtual-network/ip-services/public-ip-addresses.md) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false":::
83+
| [Azure Queue Storage](./reliability-storage-queue.md)| :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | |
8384
| [Azure Red Hat OpenShift](/azure/openshift/openshift-faq#can-a-cluster-be-deployed-across-multiple-availability-zones) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: |
8485
| [Azure Route Server](../route-server/route-server-faq.md) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | |
8586
| [Azure Service Bus](../service-bus-messaging/service-bus-outages-disasters.md#availability-zones) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | |
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
title: Description of Azure Storage redundancy architecture
3+
description: Description of Azure Storage redundancy architecture
4+
author: anaharris-ms
5+
ms.service: azure
6+
ms.topic: include
7+
ms.date: 07/02/2024
8+
ms.author: anaharris
9+
ms.custom: include file
10+
---
11+
12+
[Locally redundant storage (LRS)](/azure/storage/common/storage-redundancy?#locally-redundant-storage), the lowest-cost redundancy option, automatically stores and replicates three copies of your data within a single datacenter. Although LRS protects your data against server rack and drive failures, it doesn't account for disasters such as fire or flooding within a datacenter. In the face of such disasters, all replicas of a storage account configured to use LRS might be lost or unrecoverable.
13+
14+
:::image type="content" source="../../media/reliability-storage/locally-redundant-storage.png" alt-text="Diagram showing how data is replicated in availability zones with LRS." lightbox="../../media/reliability-storage/locally-redundant-storage.png" border="false":::
15+
16+
Zone-redundant storage (ZRS) and geo-redundant storage (GRS/GZRS) provide additional protections, and are described in detail in this article.
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
title: Description of Azure Storage availability zone configuration
3+
description: Description of Azure Storage availability zone configuration
4+
author: anaharris-ms
5+
ms.service: azure
6+
ms.topic: include
7+
ms.date: 07/02/2024
8+
ms.author: anaharris
9+
ms.custom: include file
10+
---
11+
12+
- **Change replication type**. To learn how to change an existing storage account to ZRS, as well as learn about configuration options and requirements, see [Change how a storage account is replicated](/azure/storage/common/redundancy-migration).
13+
14+
- **Disable zone redundancy.** Convert ZRS accounts back to a nonzonal configuration (such as LRS) through the same redundancy configuration change process.
Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: Description of Azure Storage availability zone cost
3+
description: Description of Azure Storage availability zone cost
4+
author: anaharris-ms
5+
ms.service: azure
6+
ms.topic: include
7+
ms.date: 07/02/2024
8+
ms.author: anaharris
9+
ms.custom: include file
10+
---
11+
12+
When you enable ZRS, you're charged at a different rate than locally redundant storage due to the additional replication and storage overhead.
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
title: Description of Azure Storage availability zone zone-down experience
3+
description: Description of Azure Storage availability zone zone-down experience
4+
author: anaharris-ms
5+
ms.service: azure
6+
ms.topic: include
7+
ms.date: 07/02/2024
8+
ms.author: anaharris
9+
ms.custom: include file
10+
---
11+
12+
- **Detection and response:** Microsoft automatically detects zone failures and initiates failover processes. No customer action is required for zone-redundant storage accounts.
13+
14+
- **Active requests:** In-flight requests might be dropped during the failover and should be retried. Applications should [implement retry logic](#transient-faults) to handle these temporary interruptions.
15+
16+
- **Expected data loss:** No data loss occurs during zone failures because data is synchronously replicated across multiple zones before write operations complete.
17+
18+
- **Expected downtime:** A small amount of downtime - typically, a few seconds - may occur during automatic failover as traffic is redirected to healthy zones.
Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: Description of Azure Storage availability zone failback experience
3+
description: Description of Azure Storage availability zone failback experience
4+
author: anaharris-ms
5+
ms.service: azure
6+
ms.topic: include
7+
ms.date: 07/02/2024
8+
ms.author: anaharris
9+
ms.custom: include file
10+
---
11+
12+
When the failed availability zone recovers, Azure Storage automatically restores normal operations across all of the availability zones. During failback, the service automatically ensures data consistency by synchronizing any operations that occurred during the outage period.
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
title: Description of Azure Storage availability zone normal operations experience
3+
description: Description of Azure Storage availability zone normal operations experience
4+
author: anaharris-ms
5+
ms.service: azure
6+
ms.topic: include
7+
ms.date: 07/02/2024
8+
ms.author: anaharris
9+
ms.custom: include file
10+
---
11+
12+
- **Traffic routing between zones**: Storage with ZRS automatically distributes requests across storage clusters in multiple availability zones. Traffic distribution is transparent to applications and requires no client-side configuration.
13+
14+
- **Data replication between zones**: All write operations to ZRS are replicated synchronously across all availability zones within the region. When you upload or modify data, the operation isn't considered complete until the data has been successfully replicated across all of the availability zones. This synchronous replication ensures strong consistency and zero data loss during zone failures. However, it may result in slightly higher write latency compared to locally redundant storage.
Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: Description of Azure Storage availability zone region support
3+
description: Description of Azure Storage availability zone region support
4+
author: anaharris-ms
5+
ms.service: azure
6+
ms.topic: include
7+
ms.date: 07/02/2024
8+
ms.author: anaharris
9+
ms.custom: include file
10+
---
11+
12+
Zone-redundant Azure Storage accounts can be deployed [in any region that supports availability zones](../../regions-list.md).
Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: Diagram of Azure Storage zone redundant storage
3+
description: Diagram of Azure Storage zone redundant storage
4+
author: anaharris-ms
5+
ms.service: azure
6+
ms.topic: include
7+
ms.date: 07/02/2024
8+
ms.author: anaharris
9+
ms.custom: include file
10+
---
11+
12+
:::image type="content" source="../../media/reliability-storage/zone-redundant-storage.png" alt-text="Diagram showing how data is replicated in the primary region with ZRS." lightbox="../../media/reliability-storage/zone-redundant-storage.png" border="false":::

0 commit comments

Comments
 (0)