Every hard drive dies eventually. Phones get stolen, laptops get dropped, and ransomware locks files that were perfectly fine yesterday. The good news is that protecting yourself does not require a complicated system — just a simple rule that has survived decades of storage technology: 3-2-1. This piece is research-based, drawn from published backup guides rather than hands-on testing, but the rule itself is straightforward enough to check against your own setup today.
The rule breaks down into three numbers. 3 means keep three copies of anything you care about: the original on your device, plus two backups. 2 means store those copies on two different kinds of media — for example, an external hard drive and a cloud service, rather than two folders on the same disk. 1 means keep at least one copy off-site, away from your home or office, so a fire, flood, or burglary cannot take everything at once.
The logic is about independent failures. A single backup protects you from a dead drive. Two different media protect you from one kind of storage failing in the same way. An off-site copy protects you from disasters that hit a whole location. Each layer covers a failure the previous one cannot.
The most common mistake is believing that a syncing service is a backup. It is not. Services that mirror your files to the cloud also mirror your mistakes: delete a photo on your phone, and the deletion syncs everywhere. Ransomware that encrypts your local files can, in the worst case, have those encrypted versions synced too.
A real backup keeps versions from the past. If you discover a file was corrupted or deleted weeks ago, a versioned backup lets you reach back to a copy from before the damage. When you set up a backup, check that it keeps older versions — that single feature is often the difference between recovering and shrugging.
A RAID array — several drives working together so one can fail without data loss — feels like safety, but it protects against exactly one thing: a drive dying. It does not protect against accidental deletion, ransomware, a power surge frying the whole box, or theft of the box itself. A RAID setup still needs a separate backup, ideally off-site, to satisfy the rule.
Manual backups fail because humans forget. The rule only works if the copies happen without you thinking about them. On a computer, that means a built-in tool like Time Machine on a Mac or File History on Windows, pointed at an external drive that stays connected, plus a cloud backup running in the background. On a phone, it means the built-in cloud backup switched on — and, just as importantly, checked occasionally.
For photos specifically, a self-hosted library can be part of the plan: our Immich guide walks through running your own photo library so your pictures live somewhere you control, not only on your phone. Whatever you choose, the test is the same — if you had to restore tomorrow, could you do it without hunting for a cable, a password, or a drive you last saw months ago?
A backup you have never restored from is a hope, not a guarantee. Drives fail silently, cloud accounts lapse, and backup software sometimes stops running without telling you clearly. Once in a while, pick a random file, delete your local copy (or move it aside), and restore it from the backup. If the restore works, your system works. If it does not, you have found the problem on a quiet afternoon instead of in a crisis.
The same applies to phones. Open your phone's backup settings and look at two things: the date of the last successful backup, and whether storage is full. A backup that stopped months ago because storage ran out is the digital equivalent of an empty fire extinguisher — reassuring to look at, useless in a fire. Note that chat apps often need separate attention: WhatsApp, for instance, has its own backup setting apart from the phone's general backup, so check it on its own.
In 1998, Pixar nearly lost Toy Story 2 when a delete command wiped roughly 90% of the film from its servers — and the studio's backups had silently failed for about a month. The production was saved by supervising technical director Galyn Susman, who was working from home on maternity leave and had a copy on her home computer. That machine was carried back to the studio wrapped in blankets, and the film was rebuilt from it. One off-site copy, in the least formal sense possible, saved a movie. It is the 3-2-1 rule's "1" in its purest form.
Today, do three small things. First, count your copies of your most important files: the original plus backups, on how many media, and is one off-site? Second, switch on automatic backup on every device that does not already have it — computer and phone both. Third, restore one file from a backup, just to prove the chain works. If any of those steps fails, you have found the gap before it mattered. And if you run your own services at home, the same discipline applies to them: a machine you control still needs a copy somewhere else, which is why guides like our run AI locally piece assume your data lives in more than one place.
Proton — The 3-2-1 backup rule
Backblaze — The 3-2-1 backup strategy
Fresh Tech Journal — Backup basics: the 3-2-1 rule
Collider — How Toy Story 2 was nearly lost forever