Business continuity & backup
Know exactly how much data you could lose and how long you'd be down, then make both numbers acceptable.
What this is.
Everyone has backups. Far fewer have tested a restore, know how long it takes, or have written down what happens when the office floods or ransomware hits on a Friday night.
I design backups around two numbers you choose, how much data you can afford to lose and how long you can afford to be down, and then test the restore so the plan is real.
What you get
- Continuity plan: who does what, in what order
- 3-2-1 backup design (three copies, two media, one off-site)
- Restore test with timings, repeated on a schedule
- Ransomware playbook and communication templates
- Annual review and tabletop exercise
How it runs
- Agree the two numbers (RPO and RTO)
- Design and implement backups
- Test a full restore
- Write the playbook and rehearse it
A good fit if
- You're not certain a restore would work
- Downtime would cost more per day than the plan costs
- Insurance or a client is asking for a continuity plan
Try it: plan a recovery
Runs entirely in your browser. Nothing you enter is stored or sent anywhere.