Local, off-site, and actually tested
A backup you have never restored is a rumour.
Nearly every business we assess has a backup. A striking number have one that has been silently failing for months, or one that ransomware would encrypt alongside everything else. The difference only shows up on the worst day of your year.
What it costs
Backup design and implementation quoted after an assessment; off-site storage billed on data volume. Ongoing monitoring and test restores sit in the $650/month retainer.
The three ways backups fail
It stopped running. Months ago. A drive filled, a credential expired, or an update broke the agent, and the failure notice went to somebody who has left. Nobody checked because it had always just worked.
It was reachable from the network. Ransomware hunts backups before encrypting anything, because that is what makes people pay. A drive plugged into the server, or a share the server can write to, gets encrypted with everything else.
It was never restored. The job reported success nightly for two years. The first real restore reveals it was backing up the wrong volume, or that nobody documented the encryption key. Success in a log is not data you can get back.
What gets configured
A local copy for speed, because restoring a deleted folder should take minutes rather than a download. An off-site copy for the fire, flood and theft case. And immutability on the off-site copy, so that even fully compromised credentials cannot delete or encrypt the history.
That is the modern form of the old 3-2-1 rule, and immutability is the part that matters most now. It is also the part missing from most setups we inherit.
Testing is the whole point
Restores get tested and the result written down, including how long it took. That number is what matters when you are deciding whether to keep waiting or start ringing customers.
The test also catches the boring failures: a database backed up while running that restores corrupt, a share whose permissions do not survive, an encryption key nobody wrote down.
Two questions that decide the design
How much data can you afford to lose — a day, an hour, none? And how long can the business be stopped — a week, a day, two hours?
Tighter answers cost more and there is a real trade. A business that can work off paper for two days needs something very different from one where a stopped system means idle staff and missed shipments. That conversation beats being sold the most expensive option by default.
Server backup, cloud backup and Microsoft 365 backup
Server backup. Image-level backups of each server, so the whole machine can be brought back onto new hardware or a virtual server rather than rebuilt by hand. File-level restores come from the same backup, so recovering one deleted folder does not mean restoring a server.
Online backup to the cloud. The off-site copy goes to cloud storage with immutability switched on and a retention period that suits how far back you might need to go. It is billed on the amount of data stored, and you get the figure up front.
Laptops and remote staff. Anyone who keeps work on a laptop rather than a server gets backed up wherever they are, not just when they are in the office.
Microsoft 365. Mailboxes, OneDrive, SharePoint and Teams backed up separately from Microsoft, because Microsoft’s own retention is designed for accidental deletion rather than recovery. See Microsoft 365 migration for why this matters on the way in.
Disaster recovery for Chicago offices
Disaster recovery is the plan for getting the business working again, not just the data back. In a downtown building that plan has to allow for things outside your suite: a building-wide power cut, a water leak from the floor above into the comms closet, a riser fault that takes out the internet for every tenant, or a building you cannot get into at all for a few days.
Chicago has form here. The 1992 Loop flood shut downtown buildings for days when river water filled the old freight tunnels underneath them. The practical lesson still holds: a backup that only exists in the same building as the server is not disaster recovery.
The written plan covers who does what, what gets restored first, where it gets restored to, and how long each step took when it was tested. It fits on a few pages and lives somewhere other than the server it describes.
Ransomware, specifically
If it happens, backups decide whether it is an expensive week or the end of the business. The ones who recover well have an off-site immutable copy, know their restore time because they measured it, and have somewhere clean to restore onto.
The ones who pay are the ones whose backup was reachable from the machine that got encrypted. Nothing else about their security posture matters as much as that single detail.
FAQ
Questions we get asked
How often should backups run?
For most businesses, image-level backups through the working day and a nightly off-site copy. If you can genuinely tolerate losing a day's work, nightly alone is cheaper and that is worth saying.
Is a backup drive plugged into the server enough?
No, and it is actively risky. Ransomware encrypts attached and reachable drives deliberately. You need a copy the compromised machine cannot write to.
Does OneDrive or Google Drive count as a backup?
It is sync, not backup. A file that gets encrypted, corrupted or deleted syncs faithfully in that state. Version history helps for one file and falls apart across thousands.
How do we know the backup works?
Because somebody restored from it recently and wrote down how long it took. Any provider who cannot tell you the date of your last successful test restore is guessing.
Can you recover data after a ransomware attack?
If there is a clean off-site copy, usually. Without one the options narrow to whatever decryptor happens to exist. This is a problem solved beforehand, not afterwards.
What is the difference between backup and disaster recovery?
Backup is having a copy of the data. Disaster recovery is the plan and the tested procedure for getting the business running again from that copy — what comes back first, onto what hardware, and how long it takes.
How much does online backup cost for a small business?
Off-site cloud storage is billed on the volume of data kept, and the design and setup are quoted after an assessment. Ongoing monitoring and regular test restores sit in the $650/month retainer. You get the numbers before anything is set up.
Do you provide backup services outside downtown Chicago?
Yes. Backup is set up and monitored largely remotely, so businesses across Chicago and the near suburbs are covered, with on-site work scheduled evenings or weekends.
Ready when you are.
Ring and describe it in plain English. You will get a number before anyone drives anywhere.