Implementing Geo-Disaster Recovery for a Service Bus Namespace
  • 24 Jun 2022
  • 1 Minute to read
  • Contributors
  • Comments
  • Dark
    Light
  • PDF

Implementing Geo-Disaster Recovery for a Service Bus Namespace

  • Comments
  • Dark
    Light
  • PDF

#ServerlessTips - Azure Functions
Author: Steef-Jan Wiggers Azure MVP

Combining Zone redundancy with Availability Zones with disaster recovery features offers high availability and fault tolerance that can withstand any zone and regional outages. The Azure Service Bus Tip - Make your Service Bus highly available using Availability Zones explains how to make a premium service bus namespace redundant in a region.

To enable Geo-Redundancy for a premium service bus namespace, you create a secondary namespace in a different region than your primary. Once the secondary is available, you go to the primary namespace and pair it with the secondary using the Geo-Recovery feature.

Azure Service Bus Tip 04 - Picture 1.png

You either pair to an existing namespace as described above, or through the feature create a new namespace in another region. Note that the region doesn’t necessarily need to have Availability Zones. Furthermore, the pairing of the namespaces will take some time.

Azure Service Bus Tip 04 - Picture 2.png

With Geo-Recovery in place, you ensured according to the documentation of the metadata (Queues, Topics, Subscriptions, Filters) being copied over from the primary namespace to secondary namespace. Furthermore, failover from one to the other namespace is manual i.e. a customer, or client application, which is detailed in the Microsoft documentation.

Also, get insights into Azure Service Bus monitoring on messaging issues and how you can improve them.

Service Bus-2


Was this article helpful?