DRS: Disaster Recovery & Data Salvage for RabbitMQ
When downtime isn’t an option, you need more than RabbitMQ clustering.
DRS how it works
RabbitMQ is trusted to keep critical systems moving—but traditional clustering wasn’t designed to survive a complete site failure. Lose an entire data centre and the cluster can’t form a majority, so it fundamentally cannot operate.
DRS (Disaster Recovery & Data Salvage) is an enterprise-grade RabbitMQ plugin that provides a safety net for teams who can’t compromise on uptime: it’s designed to keep you online or get you back online fast, even when a whole site goes down.
Watch how DRS addresses site-wide failure risk in RabbitMQ, preserves data across data centres, and enables controlled, operator-led recovery.
Want to explore DRS in detail?
Built for operational certainty
DRS is a production-grade software for critical systems – a safety net for teams that can’t compromise on uptime.
This framing matters because disaster recovery is a risk and continuity problem—not a tooling upgrade. DRS is designed for organisations that need a production-grade capability, long-lived versioned software, and clear ownership when it matters.
Support for Disaster Recovery
For mission-critical environments, we strongly advise pairing DRS with Platinum Support for full platform assurance. While DRS can be deployed on its own, Platinum Support ensures it’s configured, monitored, and optimised by RabbitMQ experts who know the platform inside out.
This combination delivers maximum reliability, faster issue resolution, and ongoing guidance as your environment evolves, giving you complete confidence that DRS will perform exactly as intended when it matters most.
Why teams choose DRS
Disaster recovery for real site loss
Traditional clustering handles a node failure; DRS is designed for the loss of an entire data center and a fast, controlled recovery.
Data preservation across locations
Passive nodes keep a mirrored copy of data to minimise data loss during recovery scenarios.
Control for capable teams
DRS is built for teams that run RabbitMQ seriously: you keep operational control, with vendor-backed accountability when the plugin is part of the incident.
Clear operational boundaries
Assurance is focused on plugin behaviour and its interaction with RabbitMQ, enabling fast, reliable escalation when it matters.
Get even more from your RabbitMQ
Explore our range of commercial and open source RabbitMQ plugins’
Frequently Asked Questions
Is this “high availability”?
It supports HA outcomes, but DRS is primarily designed for disaster recovery across two data centres, especially when site loss is the failure mode you care about.
Why not just span a normal cluster across two data centres?
Consensus/majority behaviour means a stretched cluster isn’t resilient to full data centre failure; if you lose the majority, it can’t operate.
Why is failover manual?
To avoid unsafe automatic decisions during partitions and ambiguous network conditions DRS keeps a human operator in control.
