Key Takeaways
- Keep three copies of your data, on two kinds of storage, with one copy off site.
- Add one copy that cannot be changed or deleted, so ransomware cannot reach it.
- Set backup frequency by how much work you can afford to redo, not by habit.
- A backup you have never restored is a guess. Test it on a schedule.
- Microsoft 365 and other cloud apps need their own backup. The vendor does not cover everything.
- Write down who restores what, in what order, and how long it should take.
Most business owners know they need backups. Fewer can say what is backed up, where it sits, and how long a full restore would take. That gap is where businesses get hurt. A dead server, a stolen laptop, a deleted folder or a ransomware note all end the same way: someone asks for the last good copy.
This guide walks you through the 3-2-1 rule and how it applies to a Chicago office. You will see what to protect first, how often to copy it, and how to test the result. If you would rather hand the whole job to a local team, data backup services in Chicago cover setup, monitoring and restore testing for a flat monthly fee.
The goal is plain. When something breaks on a Monday morning, you know where the data is, how old it is and how long it takes to get back. Everything below serves that goal.
What the 3-2-1 Rule Actually Means
The 3-2-1 rule is the oldest and most reliable backup plan in IT. Keep three copies of your data. Store them on two different types of media. Keep one copy somewhere other than your office. That is the whole rule.
The reason it works is that each part blocks a different failure. Three copies mean one bad file does not end the story. Two media types mean a single hardware flaw cannot wipe everything. One off-site copy means a fire, a burst pipe or a break-in at your location cannot take your only recovery option.
Your live data counts as copy number one. So the rule really asks for two backups on top of the working files. Many offices think a single external drive on a desk satisfies it. It does not. That drive sits in the same room as the thing it protects.
| Part of the Rule | What It Means | Common Chicago Example |
|---|---|---|
| 3 copies | Working data plus two backups | Server files, a local backup box, a cloud copy |
| 2 media types | Different storage technologies | Disk in the office and cloud storage |
| 1 off site | At least one copy away from the building | Encrypted copy in a remote data center |
A working file plus a local backup plus an off-site copy satisfies all three numbers in the rule.
Why the Old Version Is No Longer Enough
Many IT people now teach 3-2-1-1-0. The extra 1 is a copy that is offline or immutable, meaning it cannot be edited or erased for a set period. The 0 means zero errors found when you check the backup. Both additions exist because of ransomware.
Modern ransomware does not only lock your files. It hunts for backups first. If your backup drive is plugged into the same network, the attacker often encrypts or deletes it before you ever see a ransom note. An immutable copy closes that door.
This matters for ordinary offices, not only large companies. A twelve-person firm in the West Loop can be hit by the same automated tools as a bank. The attackers do not pick by size. They pick by what is reachable.
- Immutable storage refuses changes and deletions until a timer expires.
- Offline copies are physically disconnected from the network.
- Separate login credentials keep a stolen admin password from touching backups.
- Automated checks report errors so you do not find them during a crisis.
If you want help closing that gap, ransomware prevention services pair backup design with the security controls that keep attackers out in the first place.
What to Back Up First
Backing up everything sounds safe, but it hides priorities. Start by listing what would stop work if it vanished tomorrow. Then rank it. Customer records, accounting files, shared drives, email and any line-of-business software usually sit at the top.
- Business data: Shared folders, databases, accounting files and customer records.
- Email & calendars: Often the busiest system you own and the one people assume is safe.
- Servers & virtual machines: Full system images so you can rebuild fast, not just copy files.
- Laptops & desktops: Especially staff who work from home or travel and keep files locally.
- Cloud apps: Microsoft 365, Google Workspace, CRM and other software-as-a-service tools.
- Configuration: Firewall settings, switch configs and license keys that take hours to recreate.
That last item gets forgotten constantly. Data is easy to find. The settings that make your network behave are not. Keep them in the backup set.
Ranking systems by downtime cost usually puts email, shared files and the accounting database in the top three.
How Often Should You Back Up?
Frequency comes down to one question. If you lost everything since the last backup, how much work could you stand to redo? That window is called your recovery point objective. Pick it on purpose instead of accepting whatever the software defaults to.
A law office billing by the hour may not tolerate losing half a day. A seasonal retail shop in Lincoln Park may be fine with a nightly copy outside of the holiday rush. Both are reasonable. The mistake is not choosing.
| Type of Data | Typical Backup Frequency | Why |
|---|---|---|
| Accounting & customer databases | Every hour or continuous | Lost entries are hard to rebuild by hand |
| Shared file folders | Every few hours to nightly | Staff edit files all day |
| Email & Microsoft 365 | At least daily | High volume, constant change |
| Laptops | Daily when connected | Users move around and forget to save to the server |
| Archives & old projects | Weekly | Rarely change |
There is a second number to settle. How long can you be down while the restore runs? That is your recovery time objective. Write both numbers down. They drive the tools and the cost, which you can compare in backup and disaster recovery cost in Chicago.
Local, Cloud or Both
Local backups restore quickly. A box in your server closet can return a large folder in minutes. But it shares the building with everything else, so it fails to a fire, flood or theft. Cloud backups sit away from the building but depend on your internet speed when you need a big restore.
Most small and midsize offices do best with both. The local copy handles everyday mistakes. The cloud copy handles the disaster. This is also how you get the two media types and the off-site copy the rule asks for without much extra effort.
| Option | Strength | Weakness |
|---|---|---|
| Local disk or appliance | Fast restores, no internet needed | Lost with the building or stolen with the rack |
| Cloud backup | Off site, easy to scale | Large restores depend on bandwidth |
| Hybrid (both) | Fast and safe | Needs monitoring of two systems |
| Tape or rotated drives | Truly offline | Manual work, easy to skip or lose |
If you are weighing a hosted option, cloud backup services explain how encrypted off-site copies, retention periods and restore speeds are set up.
A hybrid setup typically restores everyday files from local disk in minutes and keeps the cloud copy for building-level disasters.
Do Not Forget Microsoft 365 & Cloud Apps
A common and costly belief is that Microsoft keeps your email and files safe, so no backup is needed. Microsoft keeps its service running. It does not promise to restore a mailbox you deleted last quarter or a folder an ex-employee wiped on the way out.
Retention in these tools is limited and built for convenience, not for recovery. Once an item ages out of the recycle bin, it may be gone for good. The same logic applies to other cloud apps your team depends on, such as your CRM or accounting platform.
- Accidental deletion by a staff member.
- Malicious deletion by someone leaving the company.
- Ransomware that syncs encrypted files into OneDrive or SharePoint.
- Retention limits that expire before you notice a problem.
A dedicated tool keeps independent copies of mailboxes, OneDrive, SharePoint and Teams data. See Office 365 backup for what that covers and how restores work for a single user or a whole tenant.
Test Your Restores
A backup that has never been restored is a hope, not a plan. Backups fail quietly. A job can report success while skipping a locked database. A drive can fill up and stop writing. You find out when you need the data most.
Set a schedule and keep notes. Pick a handful of files each month and restore them to a test location. Once a quarter, restore a full server or virtual machine and time it. Compare the time to the number you wrote down earlier.
- Monthly: Restore a few random files and open them to confirm they are readable.
- Quarterly: Restore a full system image to a test machine and record how long it took.
- Yearly: Run a mock outage. Pretend the server room is gone and walk through the plan.
- After changes: Retest whenever you add a server, move to a new application or change storage.
The yearly walkthrough shows gaps in people, not only technology. Who has the logins? Who calls the provider? Planning that process belongs in a wider disaster recovery solution, not only a backup job.
Common Backup Mistakes We See
Most failures are not exotic. They are small choices that nobody revisited. Look through this list and see how many apply to your office.
- Backup drive stays plugged into the same network and gets encrypted along with everything else.
- Only the file server is covered, while laptops and cloud apps are ignored.
- Alerts go to the email of someone who left two years ago.
- No one has ever restored anything, so the real recovery time is unknown.
- Retention is too short, so a problem found after a month cannot be undone.
- Passwords for the backup system live only in one person’s head.
- The plan covers data but not the order for bringing systems back.
That last point is where backup meets planning for the whole business. Knowing which systems come back first, who approves spending and how staff keep working in the meantime is the work behind business continuity consulting. A good backup is one piece of that larger plan.
A one-page restore order, kept on paper as well as online, saves time when the network itself is down.
A good backup plan is not complicated. Three copies, two kinds of storage, one off site, one that cannot be changed, and a restore you have actually tested. Add your cloud apps, set a frequency that matches your tolerance for lost work, and keep a short written recovery order where people can find it.
If you are not sure where your office stands, start small. Ask what is backed up, where each copy lives, how old the newest one is and when someone last restored from it. If those answers are unclear, a free IT assessment will put them on paper, with a written quote for anything that needs fixing.
FAQs
What is the 3-2-1 backup rule?
Keep three copies of your data, store them on two different types of media, and keep one copy off site. Your live data counts as the first copy. The rule protects against hardware failure, building-level disasters and accidental deletion by giving you several independent places to recover from.
How often should a small business back up its data?
It depends on how much work you can afford to redo. Databases and accounting files often need hourly or continuous protection. Shared folders and email are usually backed up several times a day or nightly. Archives can run weekly. Choose the interval on purpose and write it down.
Is a cloud backup enough on its own?
Rarely. Cloud backup gives you an off-site copy, but large restores depend on internet speed. Most offices pair it with a local copy for fast everyday recoveries. Together they cover both a deleted folder and a building-level event like a fire or flood.
Does Microsoft 365 back up my email and files?
Not in the way most people expect. Microsoft keeps the service running and offers limited recycle bin retention. It does not guarantee recovery of items deleted long ago or wiped on purpose. An independent backup keeps separate copies you control.
How do I know my backups actually work?
Restore from them. Check a few files each month, restore a full system quarterly and time it. Review job reports for errors and failed jobs. A backup that reports success but has never been restored should be treated as unproven.
What is an immutable backup?
An immutable backup cannot be changed or deleted for a set period, even by an administrator. That protects it from ransomware and from someone using stolen credentials. It is usually stored in specially configured cloud storage or on a protected appliance.
How long should I keep backups?
Keep enough history to catch problems you notice late. Many offices hold daily copies for a few weeks, weekly copies for a few months and monthly copies for a year or more. Some industries have record-keeping rules that set longer periods, so check yours.
Should laptops be backed up too?
Yes, especially for staff who work from home or travel. People often keep files on the local drive without realizing it. A laptop can be lost, stolen or encrypted. Automatic daily backup when the device connects keeps that data from disappearing with it.
Is a backup the same as disaster recovery?
No. A backup is a copy of your data. Disaster recovery is the plan and tooling to bring systems and services back, in order, within a target time. You need backups for recovery, but backups alone do not tell you how to restart the business.
Who should be in charge of backups in a small company?
One named person should own it, with a backup person who knows the logins. Many small offices hand day-to-day monitoring and testing to an outside IT provider and keep a manager responsible for reviewing the monthly report.
Reid Callahan
Editorial Director, Ping Chicago
Reid leads the Ping Chicago editorial team and works with our technicians to turn real support tickets, office moves and security reviews into plain-English guides for Chicago business owners. Born and raised in Chicago, he has spent more than 15 years in IT services, starting on the help desk and later running support and network projects for law firms, medical practices and manufacturers from the Loop to the western suburbs. He holds Microsoft 365 and CompTIA Security+ certifications and has helped hundreds of local offices move to the cloud. Today he focuses on how AI tools like Microsoft Copilot can save small teams time without putting company data at risk, and every guide he writes is checked by a working technician before it goes live.