Recovery is the point, not the copy
Plenty of offices believe they are backed up because a USB drive sits beside the server or files sync to OneDrive. Then a disk dies, a laptop disappears from a parked car, or ransomware encrypts the shared folders, and it turns out the USB drive stopped running months ago and the sync faithfully copied the damage. The question that matters is not whether a backup exists, but how much work you would lose and how long you would be down.
We start by agreeing two numbers with you: how much recent work you could afford to lose, and how quickly each system must be back. Those recovery point and recovery time targets shape a 3-2-1 design: local copies for fast restores, an off-site copy that cannot be altered, and separate backup for Microsoft 365. Restores are tested and reported, never assumed. It suits clinics, accounting and legal offices, and any business whose files are the business.
What’s covered
- Recovery planning Recovery point and recovery time targets set for each system, so the design matches what downtime would actually cost you.
- 3-2-1 backup design Your live data plus two backup copies, split between local storage and an off-site location, sized for your data and budget.
- Separate Microsoft 365 backup Independent backup of Exchange mailboxes, OneDrive, SharePoint and Teams files, with retention you control.
- Server and workstation imaging Full-system images that let a failed server or key workstation come back on new hardware or as a virtual machine.
- NAS setup and hardening Network storage configured with snapshots, separate admin accounts and no exposure to the internet, ready to act as a fast local backup target.
- Immutable off-site copies Cloud or off-site copies locked against deletion or encryption, even if an attacker gains admin access.
- Restore testing Test restores of files, mailboxes and whole systems on an agreed schedule, each one recorded with what came back and how long it took.
- Backup alert handling Backup alerts come to us rather than an unread inbox, and each failed job is investigated and rerun.
- Disaster recovery runbook Step-by-step recovery instructions, contact lists and restore order, stored outside your main systems so they are available during an outage.
Plans and pricing
| Service | Price |
|---|---|
| Backup assessment | Free |
| Cloud backup for computers and servers | From $15 per device/month |
| Backup setup (local, cloud and Microsoft 365) | Fixed quote based on data volume |
| NAS or backup appliance | Hardware itemized in your quote |
| Monitoring and restore testing | Included in managed IT plans |
Prices are in CAD. Every engagement starts with a short call and a written proposal.
Common questions
How often should a business back up its data?
It depends on how much work you could stand to redo. A busy accounting office may want file snapshots every hour during the day, while a small retailer might be fine with a nightly backup. We agree the targets for each system first, then set schedules, retention and alerts to match.
Is a NAS a backup?
A NAS is a good place for a fast local copy, but on its own it is just another storage device in the same building, exposed to the same fire, theft or ransomware. Paired with snapshots and an immutable off-site copy, it becomes a solid part of a 3-2-1 setup rather than a single point of failure.
Can backups protect us from ransomware?
They are your recovery path, as long as the attacker cannot reach them. Modern ransomware hunts for backup files and deletes them first, so we keep at least one copy immutable or offline and use separate credentials for the backup system. Prevention matters too; see business cybersecurity.
What if a drive has already failed and there is no backup?
Stop using the device, since every attempt to power it on can make things worse. Physical failures need specialist recovery, which is separate from backup work and starts with an assessment; see data recovery. Once the data is back, we put a proper backup in place so it does not happen again.
How long does it take to restore after a disaster?
We agree recovery targets with you in writing and test them, so you know the real numbers before you need them. Single files and mailboxes usually come back from a local copy quickly; a full server takes longer, which is why we test whole-system restores and record the real times in your recovery plan.