Backup & disaster recovery
Backups you have actually restored.
Backup and recovery designed around agreed recovery targets, with off-site copies and regular restore tests.
Why teams call us
Problems this solves
-
01
Backups never restored
Backups run every night, but nobody has tried a restore.
-
02
Ransomware reaches the backups
Backups on the same network get encrypted too.
-
03
No agreed recovery targets
Nobody knows how much data you could lose or how long recovery takes.
-
04
SaaS data not backed up
Microsoft 365 or Google Workspace data assumed safe by default.
Our approach
Recovery starts with two numbers agreed with the business: how much data you can afford to lose (recovery point objective, RPO) and how long you can be offline (recovery time objective, RTO). We design backup and recovery to meet them, following the 3-2-1 principle with at least one copy off-site and protected from deletion.
Restores are tested on a schedule and the results recorded, so you have evidence for auditors and confidence for the day you need it.
What is included
-
RPO and RTO definition
Recovery targets agreed per system.
-
Backup design
3-2-1 backups with off-site and immutable copies.
-
Ransomware resilience
Backups isolated from the production network and credentials.
-
SaaS backup
Microsoft 365 and Google Workspace data protected.
-
Disaster recovery plan
Step-by-step recovery runbooks.
-
Restore testing
Scheduled tests with recorded results.
What you receive
- Recovery targets per system
- Backup architecture
- Disaster recovery plan and runbooks
- Restore test reports
- Monitoring and alerts for backup failures
Technology we work with
- AWS Backup
- Azure Backup
- Veeam
- Restic
- Microsoft 365 backup
- Object storage with object lock
Industries
How an engagement runs
Every engagement starts with a signed agreement and an advance payment as set out in your proposal. Work begins once both are complete.
-
01
Assess
Systems, data and current backups reviewed.
-
02
Agree targets
RPO and RTO set with the business.
-
03
Implement
Backups, isolation and recovery runbooks.
-
04
Test
Regular restore tests and reporting.
Ready to start? Talk to us directly.
Tell us what you need in a few lines. A specialist replies with next steps and a written proposal before any work begins.
Frequently asked questions
Can't find your answer? Ask us
How often should we test restores?
Does Microsoft 365 back up our data?
Can backups survive ransomware?
Start with a conversation.
Share a few details. A specialist replies with next steps, usually starting with a short call.