Incident Response Planning
A response plan your team has rehearsed, including who decides, who speaks, and who to notify.
Read moreCloud & Infrastructure
Disaster Recovery & Business Continuity Planning
Recovery you have actually rehearsed, at a cost the business can justify.
Overview
Most organisations have backups. Far fewer have restored from them recently, and fewer still know how long a full recovery would take. The gap between those two positions is where outages turn into existential events.
We start from the business side — how long can each service be down, and how much data can you afford to lose — then design recovery to meet those numbers and, critically, run a drill to prove it. A plan that has never been tested is a document, not a capability.
What you get
Targets set by the business
RTO and RPO agreed per service with the people who carry the consequences, not chosen by IT alone.
Backups that are verified
Automated restore testing, so a corrupt or incomplete backup is discovered on a Tuesday rather than during an incident.
Cost matched to risk
Warm standby where downtime is expensive, restore-from-backup where it is tolerable. Not everything needs the same tier.
A rehearsed plan
A documented runbook and a drill your team has run, including who calls whom.
How we work
- 01
Impact analysis
Each service is ranked by the business cost of downtime and of data loss.
- 02
Design
Backup, replication and failover approaches selected per tier, with the cost of each stated plainly.
- 03
Implement
Automated backups, cross-region copies, immutability where ransomware is a concern, and monitoring on all of it.
- 04
Drill
A live recovery exercise, with the runbook corrected afterwards based on what actually happened.
Common questions
How often should we test recovery?
At least annually for a full drill, with automated restore verification running continuously. Any major architecture change should also trigger a test.
Is cloud backup enough on its own?
Not by itself. Backups in the same account as production are vulnerable to the same compromise. Separate accounts, immutability and tested restores are what make them real.
What about ransomware specifically?
Immutable backups, isolated credentials and an offline or cross-account copy. We also make sure the recovery runbook does not depend on systems that may themselves be encrypted.
Often paired with
24/7 Managed IT Support
Ongoing support for your cloud and platform environment, with defined response times and a monthly written report.
Read moreAWS Cloud Solutions
Architecture, build and optimisation on Amazon Web Services, from a single workload to a multi-account landing zone.
Read moreReady to talk about disaster recovery & business continuity planning?
We will tell you what we would do, roughly what it costs, and whether it is worth doing yet.