Hi everyone, my team is working on creating disaster recovery procedures for geo-disaster to our applications and dependencies. We are using NService Bus and Azure Service Bus to handle our messages. For Azure Service Bus we can have zone redundancy but also replication to another instance in another region, and the second option is what we’re aiming for.
Our NService Bus is installed in a Virtual Machine, so we also can achieve zone redundancy but we need to aim for geo-redundancy.
In this case: does NService Bus has some architecture for geo-replication to handle disaster recovery? I can’t find any on the docs. If there’s none, is there any backup option that we can do to save the NService Bus state and restore it in another VM?
Hi and welcome to the Particular community @gklugsec !
Any geo-redundancy for NServiceBus would be dependent on the underlying infrastructure it is being hosted on. NServiceBus itself doesn’t have a state. It uses transports and persistence to know what it needs to do, so its a matter of whether you’ve configured Azure Service Bus to be geo-redundant and the NServiceBus VMs (and their transport connections to Azure Service Bus) to be geo-redundant. If you have persistence configured, the same would be true.
Here is some documentation on Azure Service Bus and VM disaster recovery: