Skip to content

Commit da68064

Browse files
Merge pull request #279074 from axisc/eh_geo_rep_region_list
adding regions for eh geo replication
2 parents 73bdab1 + a3c4dfe commit da68064

File tree

1 file changed

+11
-1
lines changed

1 file changed

+11
-1
lines changed

articles/event-hubs/geo-replication.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,16 @@ ms.custom: references_regions
1010

1111
There are two features that provide Geo-disaster recovery in Azure Event Hubs. There's ***Geo-disaster recovery*** (Metadata DR) that just provides replication of metadata and then a second feature, in public preview, ***Geo-replication*** that provides replication of both metadata and the data itself. Neither geo-disaster recovery feature should be confused with Availability Zones. Both geographic recovery features provide resilience between Azure regions such as East US and West US. Availability Zone support provides resilience within a specific geographic region, such as East US. For more details on Availability Zones, read the documentation here: [Event Hubs Availability Zone support](./event-hubs-availability-and-consistency.md).
1212

13+
> [!IMPORTANT]
14+
> - This feature is currently in public preview, and as such shouldn't be used in production scenarios.
15+
> - The below regions are currently supported in the public preview.
16+
>
17+
> | US | Europe |
18+
> |------------------|---------------|
19+
> | Central US EUAP | Italy North |
20+
> | | Spain Central |
21+
> | | Norway East |
22+
1323
**High level feature differences**
1424

1525
The Metadata DR feature replicates configuration information for a namespace from a primary namespace to a secondary namespace. It supports a one time only failover to the secondary region. During customer initiated failover, the alias name for the namespace is repointed to the secondary namespace and then the pairing is broken. No data is replicated other than configuration information nor are permission assignments replicated.
@@ -19,7 +29,7 @@ The Geo-replication feature replicates configuration information and all of the
1929
This rest of this document is focused on the Geo-replication feature. For details on the metadata DR feature, read [Event Hubs Geo-disater recovery for metadata](./event-hubs-geo-dr.md).
2030

2131
## Geo-replication
22-
For public preview, Geo-replication is initially only enabled in a small subset of regions. The public preview of the Geo-replication feature is supported for namespaces in Event Hubs self-serve scaling Dedicated clusters. You can use the feature with new, or existing namespaces in dedicated self-serve clusters. The following features aren't supported with Geo-replication:
32+
The public preview of the Geo-replication feature is supported for namespaces in Event Hubs self-serve scaling Dedicated clusters. You can use the feature with new, or existing namespaces in dedicated self-serve clusters. The following features aren't supported with Geo-replication:
2333
- Customer Managed Keys (CMK)
2434
- Managed Identity for Capture
2535
- VNet features (service endpoints, or private endpoints)

0 commit comments

Comments
 (0)