Skip to content

Commit 29d9709

Browse files
authored
Update use-geo-replication.md
1 parent f4c72d1 commit 29d9709

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -22,27 +22,27 @@ To enable Geo-replication on a namespace during namespace creation:
2222

2323
1. Click on ‘Namespace’ to create a new Event Hubs namespace in an Event Hubs cluster in a region with Geo-replication enabled. Provide a name for the namespace and check the Enable Geo-replication box.
2424

25-
:::image type="content" source="./media/use-geo-replication/namespace-create.png" alt-text="Dedicated namespace create UI with geo-replication UI":::
25+
:::image type="content" source="./media/use-geo-replication/namespace-create.png" alt-text="Screenshot of dedicated namespace create UI with geo-replication UI.":::
2626

2727
2. Click on Add secondary region and select a secondary region and a corresponding Event Hubs Dedicated cluster running in that region.
2828

29-
:::image type="content" source="./media/use-geo-replication/region-selection.png" alt-text="Secondary region and cluster selection in namespace create UI":::
29+
:::image type="content" source="./media/use-geo-replication/region-selection.png" alt-text="Screenshot of secondary region and cluster selection in namespace create UI.":::
3030

3131
3. Select asynchronous or synchronous replication mode as the replication consistency mode. If selecting asynchronous consistency, enter the allowable amount of time the secondary region can lag behind the primary region in minutes.
3232

33-
:::image type="content" source="./media/use-geo-replication/create-replication-consistency.png" alt-text="Replication consistency UI in dedicated namespace create UI":::
33+
:::image type="content" source="./media/use-geo-replication/create-replication-consistency.png" alt-text="Screenshot of replication consistency UI in dedicated namespace create UI.":::
3434

3535
4. Then click on ‘Create’ to create the Geo Replicated Event Hubs namespace. The deployment takes a couple of minutes to complete.
3636
5. Once the namespace is created, you can navigate to it and click on "Geo-replication" tab to see your Geo-replication configuration.
3737

38-
:::image type="content" source="./media/use-geo-replication/geo-replication.png" alt-text="Geo-replication UI that shows configuration and allows various actions":::
38+
:::image type="content" source="./media/use-geo-replication/geo-replication.png" alt-text="Screenshot of geo-replication UI that shows configuration and allows various actions.":::
3939

4040
## Enable Geo-replication on an existing namespace
4141
1. Go into the namespace in the portal and click on "Geo-replication".
4242
2. Click on Add secondary region and select a secondary region and the corresponding Event Hubs Dedicated clusters running in that region.
4343
3. Select asynchronous or synchronous replication mode as the replication consistency mode. If selecting asynchronous consistency, enter the allowable amount of time the secondary region can lag behind the primary region in minutes.
4444

45-
:::image type="content" source="./media/use-geo-replication/geo-replication-consistency.png" alt-text="Replication consistency UI in geo-replication UI":::
45+
:::image type="content" source="./media/use-geo-replication/geo-replication-consistency.png" alt-text="Screenshot of replication consistency UI in geo-replication UI.":::
4646

4747
After a secondary region is added, all of the data held in the primary namespace is replicated to the secondary. Complete replication can take a while depending on various factors with the main one being how much data is in your primary namespace. Users can observe replication progress by monitoring the lag to the secondary region.
4848

@@ -51,11 +51,11 @@ You can promote your configured secondary region to being the primary region. Wh
5151

5252
To initiate a promotion of your secondary region to primary, select failover icon.
5353

54-
:::image type="content" source="./media/use-geo-replication/promotion-a.png" alt-text="Promotion UI selection in the geo-replication UI":::
54+
:::image type="content" source="./media/use-geo-replication/promotion-a.png" alt-text="Screenshot of the promotion UI selection in the geo-replication UI.":::
5555

5656
When in the promotion flow, you can select planned or forced. You can also choose to select forced after starting a planned promotion. Enter the word "promote" in the prompt to be able to start the promotion.
5757

58-
:::image type="content" source="./media/use-geo-replication/promotion.png" alt-text="Promotion UI in where you can select planned or forced":::
58+
:::image type="content" source="./media/use-geo-replication/promotion.png" alt-text="Screenshot of the promotion UI in where you can select planned or forced.":::
5959

6060
If doing a planned promotion, then once the promotion process is initiated, the new primary rejects any new events until failover is completed. The promotion process repoints the fully qualified domain name(FQDN) for your namespace to the selected region, complete data replication between the two regions and configure the new primary region to be active. Promotion does not require any changes to clients, and that they continue to work after the promotion event.
6161

@@ -64,7 +64,7 @@ In the case where your primary region goes down completely, you can still perfor
6464
## Remove a secondary
6565
To remove a Geo-replication pairing with a secondary, go into "Geo-replication", select the secondary region, and then select remove. At the prompt, enter the word "delete" and then you can delete the secondary.
6666

67-
:::image type="content" source="./media/use-geo-replication/remove-secondary.png" alt-text="Remove secondary function in the geo replcation UI":::
67+
:::image type="content" source="./media/use-geo-replication/remove-secondary.png" alt-text="Screenshot of the remove secondary function in the geo-replcation UI.":::
6868

6969
When a secondary region is removed, all of the data that it held is also removed. If you wish to re-enable Geo-replication with that region and cluster, it has to replicate the primary region data all over again.
7070

0 commit comments

Comments
 (0)