01
Recovery targets set in plain terms
How much data you can lose and how long you can be down, agreed first, then a design that meets it.
Continuity
A backup nobody has tested is a hope.
Monitored backup, documented recovery steps and restores that get tested on purpose rather than discovered during an incident. Built around how long the business can actually afford to be down.
Monitored through Datto and proven with real restores, not status screens.
02
Monitored, not set and forgotten
Failures surface as alerts to us, not as a discovery six months later when a restore is needed.
03
Restores tested on purpose
A restore that has been run is the only evidence a backup works. We run them.
Common questions
Before you write.
We already back up. Is that enough?
It depends entirely on whether anyone has restored from it. A job that reports success can still be missing the thing you need, or take three days to bring back. The test is a restore, and if nobody has run one, that is the first thing worth doing.
Isn’t Microsoft 365 already backed up by Microsoft?
Not in the way most people assume. Microsoft keeps the service running. What happens to a mailbox or a file after someone deletes it, or after an account is compromised, is your responsibility, and there is a time limit on getting it back. It is one of the most common gaps we find.
How long would we actually be down?
That is the number the design starts from rather than the one you discover afterwards. We agree how much data the business can afford to lose and how long it can afford to be offline, then build to it. If the current setup cannot meet that, you hear so first.