Azure Service Bus Geo-disaster recovery is now generally available


Geo-disaster recovery for Service Bus is now generally available! The following articles give an overview of how to enable regional disaster recovery capability for Service Bus.

Previously, the only way to protect from events which would qualify as disaster or Geo-disaster was by manually managing high availability in your respective clients, and keeping independent data centers in different regions in sync from within your client code. Any entity created in one data center had to be replicated to the other data center.

With this new feature, this is no longer necessary. Any entity created in one “primary” namespace is replicated to a “secondary” namespace.

Please note: This release does not contain data disaster recoverability. If this is required you would still need to proceed like before. We will also add data replication at a later point in time.

This feature is only available for Service Bus Premium namespaces.

Please see the full documentation of the feature, including code samples here:
https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-geo-dr

This feature is geared towards Geo disaster recovery and not for handling short outages. This article includes good samples on how to harden your client code against those events.

https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-async-messaging

https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-outages-disasters

Please also find a link to the GitHub repository showing a sample on how to utilize multiple namespaces in a custom disaster recovery solution here:

https://github.com/Azure/azure-service-bus/tree/master/samples/DotNet/Microsoft.ServiceBus.Messaging/GeoReplication


Skip to main content