Restore, do not assume
A green tick is not a recovery.
Why the backup failed
Because it had been running green for three years and nobody had ever restored from it.
How we work
Test it, document it, hand it over
Backup software reports success for all sorts of jobs that would not actually restore a working system — incomplete sets, missing databases, retention too short to reach the day the problem started. The only way to know is to restore, on a schedule, before it matters.
Documentation is the other half. A business whose IT exists only in one engineer's head is one resignation away from a bad quarter, which is why we write systems down and hand the documentation to the client rather than keeping it as leverage.
And ownership should never be in question. Your domain, tenant and data are yours. Any provider reluctant to give a client administrator access has confused a service relationship with a hostage situation, and switching away from them is the first thing worth doing.
Our principles
Three beliefs behind the method
Write it down
IT in one person's head is a risk.
You own everything
Domain, tenant and data stay yours.
Want a review?
Free, with an honest answer about what would happen in a failure.