When something gets deleted at 4 p.m., it's back by 4:30.
Backups everyone has. Tested backups, almost no one. We build a backup setup you can actually restore from, run a real test every quarter, and document the playbook so anyone on our team can execute the restore — not just the one engineer who set it up.
What goes wrong with backups.
Backups are running, but no one's checked them.
Six months go by. The day you need a restore, half the jobs have been silently failing.
We have backups — they're on the same server.
Ransomware encrypts the backups too. Now you have nothing.
Microsoft 365 has my email forever, right?
Wrong. After 30 days the deleted mailbox is gone for good. M365 isn't a backup.
We tried to restore. It didn't work.
First time you ever tested. You learned it doesn't actually work the way you thought.
What's included.
- 01
Servers + databases
Image-level backups, incremental every hour, full daily. Stored locally for fast restore + offsite for disaster.
- 02
Microsoft 365 backup
Exchange, SharePoint, OneDrive, Teams. Yes — these need a separate backup. Microsoft will tell you so themselves.
- 03
Endpoint backup
Laptops backed up automatically. Stolen-laptop and ransomware-rollback scenarios covered.
- 04
Offsite + air-gapped copy
A copy attackers can't reach even if they compromise your network.
- 05
Quarterly restore tests
A real restore. Witnessed. Documented. We send you the report.
- 06
Written DR plan
Who calls who, in what order, with what passwords. Updated yearly.
What 'covered' actually looks like.
Three levels of preparedness. Most firms we audit are in column 1 and think they're in column 3.
| Basic (most firms) | Tested (good) | Drilled (Senator standard) | |
|---|---|---|---|
| Backups running | Yes | Yes | Yes |
| Backups verified weekly | No | Yes | Yes |
| Real restore tested every quarter | No | Sometimes | Yes |
| Offsite, air-gapped copy | No | Yes | Yes |
| Microsoft 365 backed up separately | No | Sometimes | Yes |
| Written disaster-recovery plan | No | Yes | Yes |
| Restore time you can predict | Unknown | Estimate | Tested, documented |
Backup platforms.
Operational numbers.
Typical for individual-item recovery.
For most servers, including database verification.
Of restore tests over the last 12 months.
Hourly snapshots mean worst-case is 60 minutes back.
“We had a partner accidentally delete a SharePoint folder of legal documents going back four years. Senator restored it in 20 minutes. The partner never even told the rest of the firm.”
Who needs this.
- Any firm that runs on Microsoft 365 (which is most of them).
- Healthcare, legal, financial firms where lost records are a regulatory event.
- Anyone holding cyber insurance — every policy now requires tested backups.
- Firms whose 'backup strategy' is 'we have backups.'
Q01Doesn't Microsoft back up M365 already?
Doesn't Microsoft back up M365 already?
No. Microsoft replicates your data for service availability, but the moment someone deletes a mailbox, you have 30 days before it's gone. That's not a backup.
Q02What about ransomware on backups?
What about ransomware on backups?
Our standard setup includes an immutable, air-gapped copy. Attackers can encrypt your primary backups and we still have an untouched copy to restore from.
Q03How fast is 'fast' for a full server restore?
How fast is 'fast' for a full server restore?
Most servers under 4 hours. Larger databases up to 12 hours. We measure during quarterly tests so the number is real, not aspirational.
Q04Do you keep backups forever?
Do you keep backups forever?
No — we set a retention policy with you. Typically 30 days hourly, 6 months daily, 7 years monthly for regulated data.
Free backup health check.
We audit your current backup setup, test a real restore, and tell you exactly what's working and what isn't. One-week engagement, fixed price.