Backup & recovery
A backup nobody has restored from is an assumption.
We restore and open files on a schedule, write down the time and who did it, and tell you exactly how long a recovery would take.
Daily
Every backup job monitored, failures investigated
Monthly
A restore tested and a file opened (Secured, Complete)
4 h
Default recovery point on Complete
Written
A recovery plan: what comes back first, and who decides
The model
Three copies. One you can’t lose. And a test that proves it.
The 3-2-1 rule, run properly: the working copy, a second copy on different storage, and an off-site copy ransomware can’t reach. Then the part most businesses skip: bringing a file back and opening it.
- 1The working copyOn your server or in the cloud
- 2A second copyOn different storage, on site
- 3An off-site copyWhere ransomware on your network can’t reach it
- ➜The restore testA file brought back and opened, with the time and who did it
How it’s run
Four things, every time, in order.
- 01
Monitored daily
A failed job is investigated the same business day on Secured and Complete, not left in a log.
- 02
Kept apart
One copy lives where ransomware on your network can’t reach it.
- 03
Restore-tested
A real restore on a schedule, with the file opened and the time and person recorded.
- 04
Written down
What comes back first, who decides, and who to call, in a plan reviewed every year.
By plan
What each plan does, in writing.
| Item | Essential | Secured | Complete |
|---|---|---|---|
| Backup monitored | Daily | Daily | Daily |
| Failed job investigated | Next business day | Same business day | Same business day |
| Restore test | Quarterly | Monthly | Monthly |
| Recovery point, default | 24 hours | 24 hours | 4 hours |
| Recovery time, default | Best effort | 8 business hours | 4 business hours |
| Disaster recovery plan | Not included | Written, reviewed yearly | Written, reviewed yearly |
| Continuity test | Not included | Tabletop, yearly | Executed failover, yearly |
Recovery point: how much work you could lose
If the worst happened at 3pm, a 24-hour recovery point means you’d get back yesterday afternoon’s data. A 4-hour point means this morning’s.
Recovery time: how long until you’re working
The clock from “it’s gone” to “we’re working again.” Yours is set at onboarding and written into the agreement, and the recovery plan is designed against it.
Ransomware
The difference between an inconvenience and an ending.
With a copy ransomware can’t reach, and a restore that has been tested, an attack costs you a day and a clean-up. Without one, the attacker sets the price.
The first four things to do if it happens
Questions
Straight answers about backup.
We already have backups. Isn’t that enough?
How long would a recovery take?
Does ransomware reach backups?
Do you back up Microsoft 365?
Who can see the restore records?
Get started
Find out whether your backup restores.
1‑855‑OPSWORQ855‑677‑9677 · Mon–Fri, 8am–5pm ET
If the business has stopped, call. Don’t use the form.
We review what you have and say plainly whether it would bring your business back, and how long it would take.