Skip to content

Commit b16ba0e

Browse files
committed
Updated resiliency article
1 parent 708f37b commit b16ba0e

File tree

3 files changed

+37
-4
lines changed

3 files changed

+37
-4
lines changed
Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
title: Resiliency in Azure Event Grid | Microsoft Docs
3+
description: Describes how Azure Event Grid supports geo disaster recovery (GeoDR) automatically.
4+
ms.topic: conceptual
5+
ms.date: 06/21/2022
6+
---
7+
8+
# Resiliency in Azure Event Grid
9+
10+
Azure availability zones are designed to help you achieve resiliency and reliability for your business-critical workloads. Azure maintains multiple geographies. These discrete demarcations define disaster recovery and data residency boundaries across one or multiple Azure regions. Maintaining many regions ensures customers are supported across the world.
11+
12+
## Availability zones
13+
14+
Azure Event Grid event subscription configurations and events are automatically replicated across data centers in the availability zone, and replicated in the three availability zones (when available) in the region specified to provide automatic in-region recovery of your data in case of a failure in the region. See [Azure regions with availability zones](../availability-zones/az-overview.md#azure-regions-with-availability-zones) to learn more about the supported regions with availability zones.
15+
16+
Azure availability zones are connected by a high-performance network with a round-trip latency of less than 2ms. They help your data stay synchronized and accessible when things go wrong. Each zone is composed of one or more datacenters equipped with independent power, cooling, and networking infrastructure. Availability zones are designed so that if one zone is affected, regional services, capacity, and high availability are supported by the remaining two zones.
17+
18+
With availability zones, you can design and operate applications and databases that automatically transition between zones without interruption. Azure availability zones are highly available, fault tolerant, and more scalable than traditional single or multiple datacenter infrastructures.
19+
20+
If a region supports availability zones, the event data is replicated across availability zones though.
21+
22+
:::image type="content" source="../availability-zones/media/availability-zones-region-geography.png" alt-text="Image showing the availability zones that protect against localized disasters and regional or large geography disasters by using another region.":::
23+
24+
## Next steps
25+
26+
- If you want to understand the geo disaster recovery concepts, see [Server-side geo disaster recovery in Azure Event Grid](geo-disaster-recovery.md)
27+
28+
- If you want to implement your own disaster recovery plan, see [Build your own disaster recovery plan for Azure Event Grid topics and domains](custom-disaster-recovery.md)
29+
30+
- If you want to implement your own client-side failover logic, see [# Build your own disaster recovery for custom topics in Event Grid](custom-disaster-recovery-client-side.md)

articles/event-grid/geo-disaster-recovery.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,15 @@
22
title: Geo disaster recovery in Azure Event Grid | Microsoft Docs
33
description: Describes how Azure Event Grid supports geo disaster recovery (GeoDR) automatically.
44
ms.topic: conceptual
5-
ms.date: 03/24/2022
5+
ms.date: 06/21/2022
66
---
77

88
# Server-side geo disaster recovery in Azure Event Grid
99

1010
Event Grid supports automatic geo-disaster recovery of event subscription configuration data (metadata) for topics, system topics, domains, and partner topics. Event Grid automatically syncs your event-related infrastructure to a paired region. If an entire Azure region goes down, the events will begin to flow to the geo-paired region with no intervention from you.
1111

1212
> [!NOTE]
13-
> Event data is not replicated to the paired region, only the metadata is replicated. If a region supports availability zones, the event data is replicated across availability zones though.
13+
> Event data is not replicated to the paired region, only the metadata is replicated.
1414
1515
Microsoft offers options to recover from a failure, you can opt to enable recovery to a paired region where available or disable recovery to a paired region to manage your own recovery. See [Azure cross-region replication pairings for all geographies](../availability-zones/cross-region-replication-azure.md#azure-cross-region-replication-pairings-for-all-geographies) to learn more about the supported paired regions. The failover is nearly instantaneous once initiated. To learn more about how to implement your own failover strategy, see [Build your own disaster recovery plan for Azure Event Grid topics and domains](custom-disaster-recovery.md) .
1616

@@ -40,4 +40,5 @@ Event Grid’s automatic failover has different RPOs and RTOs for your metadata
4040
4141

4242
## Next steps
43+
4344
If you want to implement your own client-side failover logic, see [# Build your own disaster recovery for custom topics in Event Grid](custom-disaster-recovery.md)

articles/event-grid/toc.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -218,10 +218,12 @@ items:
218218
href: webhook-event-delivery.md
219219
- name: Custom delivery properties
220220
href: delivery-properties.md
221-
- name: Disaster recovery
221+
- name: Availability and disaster recovery
222222
items:
223+
- name: Resiliency
224+
href: availability-zone-resiliency.md
223225
- name: Geo disaster recovery
224-
href: geo-disaster-recovery.md
226+
href: geo-disaster-recovery.md
225227
- name: Security
226228
items:
227229
- name: Security baseline

0 commit comments

Comments
 (0)