Backup, disaster recovery and incident response
A plan for the bad day, tested before you need it. We make sure backups exist and can actually be restored, write recovery and incident plans, and rehearse them with your team.
What’s included
Backup strategy
What’s backed up, how often, where, and for how long.
Restore tests
Backups restored for real on a schedule, because a backup you’ve never restored is a guess.
Disaster recovery plans and drills
How long you can be down, how much data you can lose, and the steps to get back.
Incident response playbooks
Who does what when something goes wrong.
Alerts for suspicious activity
Unusual logins and access patterns flagged quickly.
When it makes sense
- You’ve never tried restoring a backup.
- Ransomware or a deleted database would stop your business.
- A customer asked for your disaster recovery plan.
What you get
- A backup and recovery plan
- Restore test results
- Incident response playbooks
- A drill with your team
Tools we work with
We pick what fits your project and your team, and we’ll say why.
- Cloud backup services
- Immutable backups
- Runbooks
- Alerting
Questions about backup, recovery and incident response
How often should we test restores?
At least a few times a year, and after any big change to your systems. The test should restore real data and measure how long it takes.
What are RTO and RPO?
How long you can afford to be down (the recovery time objective) and how much data you can afford to lose (the recovery point objective). We agree both with you before designing the plan.
Related services
Tell us what you need built.
A free 30-minute call with an engineer. You get the scope, timeline and price in writing before you commit, and a reply within one working day.