Overview
Most organisations make backups, yet few have ever tested one by bringing it back, and that gap tends to reveal itself at the worst moment: a nightly job quietly broken since last season, or a 400GB recovery that eats eleven hours nobody planned for. We bring your data back inside a sealed-off environment, check it is complete and consistent, then clock the whole process from start to finish. You leave with real recovery timings plus a procedure your team can follow at 3am.
What you receive
- Inventory of backup coverage for your databases, file storage and configuration
- A full restore carried out into a separate, isolated environment
- Integrity checks after the restore, comparing checksums and row totals
- Per-system measurements of recovery duration and potential data loss
- Gap analysis highlighting anything that is not backed up
- Step-by-step restore runbook written for use under pressure
- Costed remediation plan addressing every issue the drill uncovers
How it runs
-
Step - 01
Inventory
We map each system's backups, their frequency and where they are stored.
-
Step - 02
Restore
A genuine restore is run into an isolated environment away from production.
-
Step - 03
Verify
We check that nothing is missing and the application behaves correctly.
-
Step - 04
Report
You receive measured figures, identified gaps and a costed remediation plan.
Timeline: 7 working days, counted from the day we receive what we need from you.
Is it a fit?
A good match for
- Organisations that have never tested restoring from backup
- Teams with recovery commitments written into customer contracts
- Businesses reacting to an incident that revealed missing backups
What we need from you
- Read access to where backups are kept and to each system in scope
- A target cloud account or server space to receive the restored data
- Your definition of a successful, accurate restore
Why it helps
- Recovery times taken from an actual exercise rather than guesswork
- Unprotected data is found before you urgently need it
- A restore procedure any teammate can carry out without its author
Questions
Then the drill has done its most important job by exposing the problem early. Fixing the restore path becomes the top priority in the remediation plan we hand over.
No. Every restore lands in a sealed-off environment, and we only read from your backup storage, so production systems and data are never touched during the drill.
For critical systems, once a quarter is sensible. With the runbook in hand, your own team can run later drills without needing us involved.