Backup Checklist (3-2-1)
Three copies, two kinds of storage, one off-site, one with version history and one not permanently connected. Plus the restore test that proves any of it works.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the Backup Checklist?
Most people have one copy of everything and a vague sense that the cloud is handling it. The 3-2-1 rule exists because the common failures each defeat a different subset of copies: deletion propagates through sync, theft and fire take everything in one room, ransomware encrypts whatever is mounted, and drives bought together fail at similar times.
The section that changes the most minds is the one explaining why sync is not backup. A synced folder is one copy in several places, not several copies, and a deletion reaches all of them within seconds.
- Explains why each part of 3-2-1 exists, rather than just stating the rule
- Adds the two modern requirements: version history and a copy that is not always connected
- A dedicated section on why sync is not backup, which is the common misconception
- Includes the restore test, which is the only proof the rest of it works
- Editable and exportable as PDF, CSV, Markdown or a Google Form
Updated
How to use the Backup Checklist
- List what you could not recreate, including phone photos and anything only in a cloud service.
- Arrange three copies across two kinds of storage with one off-site.
- Make sure one copy keeps version history and one is not permanently connected.
- Automate it, encrypt the off-site and portable copies, and set a monthly reminder to check it ran.
- Restore a real file every few months, and once work out how you would restore everything.
Worked examples
Starting from nothing
Input
Essentials only
Output
Three copies, two media, one off-site, versioned, restore tested
Each item defeats a different failure.
Everything is in one cloud folder
Input
Sync section
Output
Version window checked, offline copy added
Sync is one copy in several places, not several copies.
Annual check
Input
Operate section
Output
Backup verified as running, a file restored, key located
An unmonitored backup fails silently by default.
Background and insight
Three copies means the original plus two backups, because a single backup means one failure during a restore loses everything, and restores are exactly when hardware is stressed. Two kinds of storage matters because identical drives bought at the same time have correlated failure. One copy off-site handles the whole-room failures: fire, flood and theft all take the backup drive sitting beside the computer.
Two additions to the classic rule have become essential. At least one copy needs version history, because ransomware and accidental overwrites both replace good files with bad ones, and a copy that faithfully mirrors the bad version is no help. And at least one copy should not be permanently connected, because an always-mounted drive is encrypted by the same attack that hits the machine.
What to back up is narrower than people assume for applications and wider for data. The operating system and installed software are replaceable. Your own files are not, and they are not all in your documents folder: browser bookmarks, mail archives, application settings, two-factor seeds and the folder on the desktop called work all count. Phones hold most of the photos and are the most commonly assumed and least often verified backup of all.
Data that exists only in someone else's service needs exporting rather than backing up. Email, notes, calendars and anything in a platform you do not control disappear with an account closure, a suspension or a dispute, and the export has to exist before that happens.
Finally, operation. A manual backup is a backup that stops during a busy month, so it has to be automated. Silently failed backups are the normal state of an unmonitored backup, so checking that it ran belongs on a schedule. And restoring a real file every few months is the item that separates a backup from a hope, which is why it is the one everybody skips.
Common use cases
Personal photos and documents
The irreplaceable data, and the places it hides outside your documents folder.
Freelancers and small businesses
Client work, records and the retention periods a tax authority expects.
Ransomware resilience
Why version history and a disconnected copy are the two that matter.
Leaving a platform
Exporting data that only exists in a service you do not control.
Tips and limitations
- Check how long your cloud service keeps deleted files. Often 30 days, sometimes less.
- Encrypt portable and off-site copies. A lost backup drive is everything you own, handed over.
- Your phone holds most of the photos and is the least verified backup you have.
- Export anything that exists only in someone else's service before you need to.
- Write down what is backed up where, and tell someone you trust how to find it.
Sources and further reading
- Data Backup Options, Cybersecurity and Infrastructure Security Agency. Backup types, media and off-site storage
- Offline backups in an online world, National Cyber Security Centre. Why a disconnected copy matters against ransomware
- Stop Ransomware, Cybersecurity and Infrastructure Security Agency. Recovery guidance and preparation
Frequently asked questions
What is the 3-2-1 backup rule?
Three copies of anything you cannot recreate, on two different kinds of storage, with one kept away from the building. Modern practice adds two things: at least one copy with version history, and at least one that is not permanently connected.
Why does a synced folder not count as a backup?
Because a synced folder is one copy in several places, so a deletion reaches all of them within seconds and so does ransomware encryption. Check how long your service keeps deleted files and old versions, because beyond that window there is nothing to recover.
How do I protect backups from ransomware?
Keep at least one copy with version history, so good versions survive the bad ones, and at least one copy that is not permanently mounted, because an always-connected drive is encrypted along with the machine. Both are more important than the backup software you choose.
What should I actually back up?
Anything you could not recreate: photos, documents, code, records. Not the operating system or installed applications. Look outside your documents folder too, for browser bookmarks, mail archives, application settings and two-factor seeds, and include your phone.
How often should I test a restore?
Restore one real file every few months, and at least once work out how you would restore everything, including where the encryption key is and whether you could reach it from a machine that has just died. This is the item that separates a backup from a hope.
Is there an in-depth guide to the Backup Checklist?
Yes. “Why Checklists Work, and How to Use One Properly” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.