A backup nobody has restored from is not a backup. It is an assumption.
Almost every business we meet has something they call a backup. Rather fewer know when it last ran, what is actually in it, or how long a restore would take. Those three questions are the whole subject.
What a working setup looks like
- More than one copy, in more than one place — a backup on a drive next to the server does not survive fire, flood or theft.
- Something offline or immutable — ransomware encrypts every backup it can reach.
- Monitored — silent failure is the normal failure mode, and it is discovered at the worst moment.
- Tested — an occasional real restore, not a green tick in a dashboard.
Two questions before choosing anything
How much work can you afford to lose — an hour, a day, a week? And how long can you be stopped while it comes back? Those two answers determine the design and the cost. Everything else is product selection.
We design, set up and monitor backups for local files, servers and cloud services — including Microsoft 365, which is not backed up by default as often as people assume.