Skip to content

Commit 247e3c8

Browse files
committed
fixing geo-replication how to
1 parent b32ebca commit 247e3c8

File tree

4 files changed

+26
-10
lines changed

4 files changed

+26
-10
lines changed
52.2 KB
Loading
33.1 KB
Loading

articles/event-hubs/use-geo-replication.md

Lines changed: 25 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,28 +6,39 @@ author: axisc
66
ms.author: aschhabria
77
ms.date: 06/10/2024
88
---
9-
# How to use Geo-replication (Public Preview)
9+
# How to use Geo-replication
1010

11-
This tutorial shows you how to use the Geo-replication with your Event Hubs Dedicated namespace. To learn more about this feature, read the Geo-replication article. In this article you learn how to:
11+
This tutorial shows you how to use the Geo-replication with Event Hubs. To learn more about this feature, read the Geo-replication article. In this article you learn how to:
1212

1313
- Enable Geo-replication on a new namespace.
1414
- Enable Geo-replication on an existing namespace.
1515
- Perform a planned promotion or failover.
1616
- Remove the secondary from your namespace.
1717

18-
## Prerequisites
19-
To use the Geo-replication feature, you need to have at least one Dedicated Event Hubs cluster in two regions where the Geo-replication feature is available.
20-
2118
## Enable Geo-replication on a new namespace
19+
2220

23-
You can enable Geo-replication during namespace creation and after namespace creation.
24-
To enable Geo-replication on a namespace during namespace creation:
25-
21+
### [Dedicated](#tab/Dedicated)
22+
23+
> [!NOTE]
24+
> To use geo-replication feature, at least one Dedicated Event Hubs cluster is needed in each region where Geo-replication feature is available.
25+
>
26+
2627
1. Navigate to the **Event Hubs Cluster** page for your Event Hubs cluster.
2728
1. On the left menu, expand **Entities**, and select **Cluster Namespaces**.
2829
1. To create an Event Hubs namespace in an Event Hubs cluster in a region with Geo-replication enabled, on the **Cluster Namespaces** page, on the toolbar, select **+ Namespace**. Provide a name for the namespace, and select **Enable Geo-replication**.
2930

30-
:::image type="content" source="./media/use-geo-replication/namespace-create.png" alt-text="Screenshot of dedicated namespace create UI with geo-replication UI.":::
31+
:::image type="content" source="./media/use-geo-replication/namespace-create.png" alt-text="Screenshot of dedicated namespace create UI with geo-replication UI.":::
32+
33+
### [Premium](#tab/Premium)
34+
35+
1. Follow the steps to create an Event Hubs namespace as listed [here](event-hubs-create.md) and pick the `Premium` tier.
36+
1. Provide a name for the namespace, and select **Enable Geo-replication**.
37+
38+
:::image type="content" source="./media/use-geo-replication/premium-namespace-create.png" alt-text="Screenshot of premium namespace create UI with geo-replication UI.":::
39+
40+
---
41+
3142
2. Select **Add secondary region**, and select a secondary region and a corresponding Event Hubs dedicated cluster running in that region.
3243

3344
:::image type="content" source="./media/use-geo-replication/region-selection.png" alt-text="Screenshot of secondary region and cluster selection in namespace create UI.":::
@@ -65,6 +76,11 @@ If doing a planned promotion, then once the promotion process is initiated, the
6576

6677
In the case where your primary region goes down completely, you can still perform a forced promotion.
6778

79+
## Switch replication mode
80+
81+
To switch between replication modes, or update the maximum replication lag, click on the link under **Replication consistency**, and click the checkbox to enable / disable synchronous replication, or update the value in the textbox to change the asynchronous maximum replication lag.
82+
:::image type="content" source="./media/use-geo-replication/update-namespace-geo-replication-configuration.png" alt-text="Screenshot showing how to update the configuration of the Geo-Replication feature.":::
83+
6884
## Remove a secondary
6985
To remove a Geo-replication pairing with a secondary, select **Geo-replication** on the left menu, select the secondary region, and then select **Remove**. At the prompt, enter the word **delete**, and then you can delete the secondary.
7086

articles/reliability/reliability-event-hubs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ There are two features that provide geo-disaster recovery in Azure Event Hubs.
6262

6363
For detailed information, samples, and further documentation, on Geo-Disaster recovery in Event Hubs, see [Azure Event Hubs - Geo-disaster recovery](../event-hubs/event-hubs-geo-dr.md).
6464

65-
- **Geo-replication (public preview)**, which provides replication of both metadata and data, replicates configuration information and all of the data from a primary namespace to one, or more secondary namespaces. When a failover is performed, the selected secondary becomes the primary and the previous primary becomes a secondary. Users can perform a failover back to the original primary when desired.
65+
- **Geo-replication**, which provides replication of both metadata and data, replicates configuration information and all of the data from a primary namespace to one, or more secondary namespaces. When a failover is performed, the selected secondary becomes the primary and the previous primary becomes a secondary. Users can perform a failover back to the original primary when desired.
6666

6767
For detailed information, samples, and further documentation, on Geo-replication in Event Hubs, see [Geo-replication ](../event-hubs/geo-replication.md).
6868

0 commit comments

Comments
 (0)