Azure Event Hub Geo-Disaster recovery

Leonty Lahman 0 Reputation points
2025-01-07T02:16:33.1166667+00:00

Your revised version looks great! Here's a slightly refined version with minor adjustments for flow:


Hi,

I am interested in implementing a geo-disaster recovery mechanism for Azure Event Hub.

I have reviewed the guidelines regarding primary and secondary namespaces, but I would like to know if there is a straightforward way to automate the disaster recovery process.

Is there any service available that can monitor Event Hub namespace availability and automatically perform failover and failback?

Thank you!

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,300 questions
Azure Event Hubs
Azure Event Hubs
An Azure real-time data ingestion service.
671 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Smaran Thoomu 18,965 Reputation points Microsoft Vendor
    2025-01-07T17:01:30.5233333+00:00

    Hi @Leonty Lahman
    Welcome to Microsoft Q&A platform and thanks for posting your query here.
    Great question! Azure Event Hubs Geo-disaster recovery (Geo-DR) provides primary and secondary namespaces but automating the failover process requires some setup since there isn’t a fully automated service for this yet.

    Here’s how you can approach it:

    1. You can use Azure Monitor or Application Insights to monitor the health of your Event Hub namespaces. These services can alert you if the primary namespace becomes unavailable.
    2. While failover itself must be triggered manually or via API, you can automate it by creating an Azure Function or a Logic App.
    3. The function can listen for alerts (from Azure Monitor) and trigger the failover by calling the Event Hubs Geo-DR failover API. Here's the API documentation: Failover API
    4. Once the primary namespace is available again, you’ll need to reconfigure it manually or through automation scripts to restore it as the active namespace.

    If you’re looking for a more streamlined solution, you could combine these tools into a workflow:

    • Azure Monitor for detecting downtime.
    • Azure Function or Logic App for triggering failover.
    • PowerShell or Azure CLI for post-failover operations.

    Hope this helps. Do let us know if you any further queries.


    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.