Disaster Recovery for Azure Service Bus scheduled messages

Question

We have multiple azure applications using Azure Service bus standard namespaces. We are not using premium sku due to increased cost and limited functionality for metadata replication only and not for messages. We use Scheduled mesages for lot of our uses cases where messages are being scheduled for up to 30 days. we need to implement disaster recovery for this use case where we can replicate scheduled messages to other region and can reply if needed. I read that service bus uses azure Sql server for data store and that Sql server is backed up in separate regions for standard sku. Will Microsoft be able to use that back up and tie it to the new service bus in case of disaster or as application users we can implement a solution for it.

Answer 1

@Piyush Gupta Thanks for reaching out.

I read that service bus uses azure Sql server for data store and that Sql server is backed up in separate regions for standard sku. Yes, you are correct that Azure Service Bus Standard uses Azure SQL Database as its data store.

A disaster is defined as the permanent, or longer-term loss of a Service Bus cluster, Azure region, or datacenter. The region or datacenter may or may not become available again, or may be down for hours or days. Examples of such disasters are fire, flooding, or earthquake. A disaster that becomes permanent might cause the loss of some messages, events, or other data. However, in most cases there should be no data loss and messages can be recovered once the data center is back up.

Will Microsoft be able to use that back up and tie it to the new service bus in case of disaster or as application users we can implement a solution for it.

In the event of a disaster, the message can or cannot be recovered depending on if it is a permanent disaster. We will try to recover to the older state of your namespace in time and there could be loss of message as mentioned in disaster scenario discussed here. No, it is not possible to retrive the message on another namespace.

As an application user, you will need to implement a solution to replicate your scheduled messages to the new Service Bus namespace in the event of a disaster. The same is discussed in detail in the message replaction document here.

Feel free to get back to me if you have any queries or concerns.

Please accept as "Yes" if the answer is helpful so that it can help others in the community. If you need any help/clarification/concerns/follow up questions, then please click on "Add Comment" on my answer and provide more details.