If your office lost its main server, a laptop full of client files, or its Microsoft 365 mailboxes tomorrow, how many separate copies of that data would still exist, and where would they be? For a lot of small businesses the honest answer is “one, and it’s in the same building.” The 3-2-1 backup rule is the simple, long-standing pattern designed to fix exactly that.
This guide explains what each number means, how the rule translates to a real small-business setup, where the classic version needs reinforcing against ransomware and cloud-app risks, and how to put it into practice. It draws on the backup planning, monitoring and recovery readiness services listed on IronGate MSP’s Backup & Disaster Recovery page.
What the 3-2-1 Backup Rule Actually Means
The 3-2-1 backup rule says to keep three copies of your data, on two different types of storage, with one copy stored offsite. The three copies include your original working data plus two backups.
Number | What it means | Why it matters |
|---|---|---|
3 | Your live data plus two separate backup copies | One failed backup doesn’t leave you with nothing |
2 | Two different kinds of storage, such as a local disk or NAS and a cloud service | A single type of failure, fault or attack is less likely to hit both |
1 | One copy kept offsite, away from your office | Fire, flood, theft or a building-wide event can’t destroy every copy |
Three copies
The original data counts as the first copy, which surprises people. Two backups on top of that means any single loss, whether a deleted folder, a dead drive or a corrupted file, still leaves you at least two ways back. Two copies that live in the same place and fail for the same reason are not really two copies, so independence matters as much as the count.
Two types of storage
The goal of the “2” is diversity. A backup on an external drive and another on the same server, or two backups in the same cloud account, can share a weakness, such as a power surge, a configuration error or one stolen password. Pairing, for example, a local appliance or NAS with a cloud backup service spreads that risk. Tape, removable drives and cloud object storage all count as different types.
One copy offsite
Offsite simply means somewhere a local disaster can’t reach. For most small businesses that means a cloud backup service or a secure remote location. It also means the offsite copy should be separated from your everyday systems, so that someone with access to your office network can’t casually reach it.
Where the Rule Came From and Why It Still Works
The rule was popularized by photographer Peter Krogh in his 2005 book on digital asset management, written for people trying to protect irreplaceable image libraries. IT teams adopted it because it is easy to remember, and easy to audit: anyone can look at a backup design and count whether it meets the three numbers.
It has lasted because it targets the failures that actually happen: hardware dying, people deleting things, disasters destroying a site, and software going wrong. What it doesn’t do on its own is guarantee that a copy is safe from deliberate attack or that it can be restored, which is where the next sections come in.
What a 3-2-1 Setup Looks Like in a Small Office
The rule is a pattern, not a product. Here is how it can look for three common small-business situations. These are illustrations, not recommendations for any particular product.
Business setup | Possible 3-2-1 arrangement | Gap to watch |
|---|---|---|
Office with an on-site file server | Live data on the server; a second copy on a local backup appliance or NAS; a third copy sent to a cloud backup service | The local backup sitting on the same network as the server and exposed to the same attack |
Mostly cloud-based, on Microsoft 365 | Live data in Microsoft 365; a separate backup of mailboxes, OneDrive and SharePoint with a third-party backup service; a periodic copy of critical files elsewhere | Assuming the cloud provider’s retention settings are a backup |
Hybrid: server plus cloud apps | On-site backup for the server, cloud backup for the server and for the cloud apps, kept under separate credentials | Some systems backed up twice while others, like a new SaaS app, are missed entirely |
Where the Classic Rule Falls Short
Ransomware and immutable copies
Modern ransomware often goes looking for backups before it encrypts anything, because deleting them removes your easiest way out. A copy that is always connected and always writable can be encrypted or deleted along with everything else. That is why many providers now describe an extended version, often written 3-2-1-1-0: the same three-two-one structure, plus one copy that is immutable or offline, plus zero errors confirmed through restore testing. An immutable copy can’t be changed or deleted for a set retention period, even by someone holding administrator credentials. Our ransomware protection guide covers protecting backups in more depth.
Microsoft 365 and cloud apps
Email, files and Teams data held in Microsoft 365 or other software-as-a-service apps are easy to overlook, because they already live “in the cloud.” But a provider keeping the service running is not the same as keeping a recoverable, independent copy of your data. IronGate MSP’s Cloud & Microsoft 365 page notes that Microsoft 365 is not a full backup service on its own, so cloud data needs to be inside your 3-2-1 plan rather than assumed safe.
Sync is not backup
File-sync tools mirror changes across devices, including accidental deletions and encrypted files. They are convenient and useful for availability, but if a file is wiped or overwritten in one place, the change often replicates everywhere. A backup keeps older, recoverable versions; sync usually doesn’t. Treat a sync service as part of your working data, not as one of your backup copies unless it has been set up with versioned recovery for exactly that purpose.
How to Put the Rule Into Practice, Step by Step
- List what matters. Identify critical data and systems: file shares, line-of-business applications, databases, email, and cloud apps. Note which ones would stop the business if they were unavailable.
- Map where it lives today. For each item, write down where the live data and any existing copies are, including laptops and cloud services.
- Count honestly. Check each system against the three numbers. Many offices find they have one backup in one place, or a copy that is really just a sync folder.
- Fill the gaps. Add the missing copy, storage type or offsite location, keeping at least one copy outside the reach of everyday office credentials.
- Protect the backups. Use separate logins, multi-factor authentication, encryption and, where possible, an immutable or offline copy.
- Monitor and test. Make sure someone sees failures, and restore real files and systems on a schedule. Our guide to how often to test backups sets out a practical rhythm.
- Write it down. Record what is backed up, where, who is responsible, and how to restore it, so recovery doesn’t depend on one person’s memory.
Keep in mind that the rule describes copies, not recovery speed. How quickly you need to be running again, and how much recent data you can afford to lose, are separate questions covered in our backup vs. disaster recovery guide.
Common 3-2-1 Mistakes
- Counting two backups on the same device, in the same account, or in the same room as two separate copies
- Leaving the “offsite” copy permanently connected and editable from the office network
- Using one set of administrator credentials for production systems and backups alike
- Treating file-sync or a cloud provider’s recycle bin as a backup
- Leaving laptops, new servers or newly adopted cloud apps out of the backup scope
- Never restoring from the backups, so problems stay hidden until a real emergency
- Setting it up once and never reviewing it as the business and its data grow
Backup design can also affect insurance conversations, since insurers increasingly ask about it. Our guide to what cyber insurers require explains what to expect.
Where IronGate MSP Fits
IronGate MSP’s Backup & Disaster Recovery page lists backup planning and strategy, data backup support, recovery process planning, business continuity guidance, support for Microsoft 365 environments, monitoring and maintenance of backup systems, and review of backup reliability and recovery readiness. Those are the pieces that turn the 3-2-1 rule from a diagram into something that works on a bad day. Backup oversight can also sit alongside ongoing managed IT support. The site doesn’t publish specific backup architectures or testing schedules, so when talking to any provider, ask how your copies would be arranged, what is stored offsite, how backups are protected from tampering, and how often restores are tested.
Frequently Asked Questions
Is the 3-2-1 backup rule still enough in 2026?
It is a strong foundation but not a complete plan. Ransomware that deletes or encrypts reachable backups, and backups that were never tested, are the two gaps the classic rule doesn’t cover on its own. Adding an immutable or offline copy and regular restore tests closes most of that distance.
Does a NAS or RAID array count as a backup?
Not by itself. RAID protects against a single disk failure, but it mirrors mistakes, deletions and malware instantly. A NAS can be one of your backup copies if it holds a separate, versioned backup of your data, but it should not be the only one and it should not sit on the same open network share as your everyday files.
How far away should the offsite copy be?
Far enough that one local event, such as a fire, flood, theft or building-wide power problem, can’t reach both copies. For most small businesses a reputable cloud backup service meets this need, as long as it is separate from your day-to-day file sharing.
Can a small business afford a 3-2-1 setup?
Usually, because the rule is about how copies are arranged rather than about buying specific products. A cloud-first office may only need one local or secondary copy added to what it already has. Cost varies with how much data you protect and how quickly you need it back, so ask for a scoped quote rather than assuming.
Conclusion
The 3-2-1 backup rule works because it is simple: three copies, two types of storage, one offsite. Treat it as the floor rather than the ceiling. Add a copy that ransomware can’t reach, include your cloud apps, and prove the whole arrangement works by restoring from it regularly.
If you’re not sure how many independent copies of your data you really have, IronGate MSP offers a no-obligation consultation to review your backup and recovery readiness. Schedule a consultation.