Disaster Recovery Plan Tool
Draw what is copied where and how traffic fails over, and keep each recovery step's owner, deadline and commands one click behind it.
Free forever on the Personal plan
Disaster recovery plans: an example
Copies beside what they protect
Primary and recovery side by side, with every replication path labelled by its lag.
A deadline on every step
Each recovery step shows the time it should be done by, counted from the declaration.
Commands where they are needed
Instructions, commands and contacts open from the step that needs them.
The basics
What is a disaster recovery plan?
A disaster recovery plan, or DR plan, describes how an organisation restores its critical systems after a major failure: which systems matter most, how quickly each must be back (the RTO), how much data it can lose (the RPO), where the copies are kept, and the steps, owners and contacts for the recovery itself.
Teams use DR plans to run recovery tests, answer audit and customer questionnaires, and act under pressure when a site or cloud region fails. A plan written as a long document drifts from the infrastructure it describes; a diagram makes it obvious what will be recovered, and the steps need to sit right beside it.
In Blueprintr the diagram shows the primary and recovery sides, and each copy and each step opens a stratum with its instructions, owner and deadline, so the picture and the procedure are one document.
Why Blueprintr
DR plans you can follow under pressure
Draw the recovery once, then keep the procedure behind every step.
Primary and recovery, side by side
Draw both sites or regions with containers and the AWS, Azure and network icons, and label each replication path with its lag or schedule.
VellumSteps with owners and deadlines
Give each step a stratum with numbered instructions, commands in a Raw tab, the owner and the time it should be done by.
StratumA copy for when systems are down
Export the blueprint as a zip of markdown, diagrams and strata, or the diagram as a PDF, and keep it with your offline plans.
Check the recovery side exists
On the Team plan, Continuum Cloud reads AWS and Azure read-only and draws what is there, so you can compare both regions with the plan.
ContinuumEvery test on record
Add a dated update after each recovery test and publish. Every publish keeps a snapshot, and on the Team plan you can browse earlier versions.
Walk the board through it
On Premium, Podium turns framed parts of the diagram into slides, so the plan you present is the plan you run.
Podium
How to
How to write a disaster recovery plan in Blueprintr
Create a private blueprint
Sign up free, create a blueprint for the service and keep it private while you write it.
Draw both sides
Draw the primary and recovery sites, with each copy beneath what it protects and every path labelled.
Set the targets
Write the RTO and RPO for each system in a stratum, with who agreed them and when.
Write the steps
Add a box for each recovery step and a stratum with its instructions, commands, owner and deadline.
Test it and record the result
Run a recovery test, add the date and result to the plan, fix what failed and publish.
FAQ
Questions about disaster recovery plans
Is this disaster recovery plan tool free?
Yes. The Vellum editor, strata and blueprint export are on the free Personal plan. Drawing your cloud from a scan with Continuum Cloud is part of Team, and presenting with Podium needs Premium.
What should a disaster recovery plan include?
The systems in scope and their tiers, an RTO and RPO for each, where copies are kept, who declares a disaster, each recovery step with an owner and deadline, contacts, and the result of the last test.
What is the difference between RTO and RPO?
The recovery time objective (RTO) is how long a system may be down before it must be restored. The recovery point objective (RPO) is how much data you can afford to lose, measured as time before the failure.
Can I keep a copy of the DR plan offline?
Yes. Export the blueprint as a zip with its diagrams, its rich text as markdown and every stratum, or export the diagram as PDF, PNG or SVG, and store it with your offline copies.
Does Blueprintr run the failover for me?
No. Blueprintr documents the plan; it does not run recovery steps or change your infrastructure. Continuum Cloud only reads AWS and Azure, with read-only access.
How often should a disaster recovery plan be tested?
Many teams test at least once a year and after any major change. Record each test with its date, result and actions in the plan, then publish, so the next reader knows how recent the evidence is.