An example engagement / Review + restore test
Your backups haven’t been put to the test
A backup notification says the job ran. Find out whether you can restore the systems and files your team actually needs.
The situation
Backups are running, but nobody can remember the last restore test. If a critical system failed, it is unclear who would recover it, how long it would take, or what might be missing.
How we approach it
We agree which systems matter most and what your team needs to get working again. With your IT provider, we review backup coverage, recovery access, and who owns each step.
Then we arrange a restore test in an isolated environment. We record what worked, what was missing, and what needs attention.
What you end up with
- A recovery plan with named contacts and clear responsibilities.
- Evidence from an agreed restore test, including gaps to address.
- A schedule for checking backups and testing recovery again.
Rough timeline
The first review and test are scoped around your systems and provider availability. Follow-up checks can form part of ongoing fractional CTO support.
Tell us what
isn’t working.
The system you work around. The project that stalled. The decision nobody has time to make.
Bring it to us. We’ll tell you honestly whether we’re the right people for it.
Let’s talk about it