The 3-2-1 backup rule is the closest thing data protection has to a universal standard. It comes from IT and enterprise backup, but it applies just as well to the photos on your phone, the documents in your cloud account, and the files you’d be devastated to lose.
The rule: keep 3 copies of your data, on 2 different types of storage media, with 1 copy stored offsite.
It sounds simple because it is. Most people with reliably protected personal files aren’t following some complex system — they’re following a variation of this principle, sometimes without knowing what it’s called.
Why Three Copies, Not Two
The instinct when thinking about backup is to think in pairs: the original and one copy. If the original is lost, you restore from the copy.
The problem is that backup failures tend to cluster. A house fire that destroys the computer also destroys the external drive sitting next to it. Ransomware that encrypts your files often also encrypts mounted drives and synced cloud folders. An account compromise that locks you out of your primary cloud might also lock you out of a backup that used the same password.
Three copies provide a statistical buffer against correlated failures. If two copies fail simultaneously — which is already unlikely — there’s a third. Two copies passing through the same failure event leaves you unprotected. Three copies across genuinely separate locations makes that scenario functionally impossible.
Why Two Different Media Types
This is the most counterintuitive part of the rule.
“Media type” here means the storage technology, not just the location. Two copies on different cloud services are two copies, but they’re both cloud storage — they share a failure mode (account access, provider shutdown) even if they’re physically in different data centers.
Two different media types might mean:
- Cloud storage + external hard drive
- Cloud storage + a local NAS device
- SSD + optical media (used for very long-term archival)
- Phone internal storage + a drive in a different physical location
The point isn’t that any specific combination is uniquely safe. It’s that different storage technologies fail differently. A cloud provider going out of business doesn’t take your local drive with it. A hard drive failure doesn’t affect your cloud copies. Diversifying across types reduces the chance that a single category of failure takes out multiple copies at once.
Why One Copy Offsite
The offsite requirement solves for location-based failures: fire, flood, theft, or any physical event affecting a specific place.
Two copies in the same house provide redundancy against one drive failing. They provide zero redundancy against the house burning down.
“Offsite” in practice can mean:
A cloud storage service. This is the most common implementation — a cloud backup counts as offsite because the servers are physically elsewhere. For most people, this satisfies the offsite requirement cleanly.
A drive at another location. A family member’s house, a safe deposit box, an office — any physical location that’s geographically separate from where the other copies live.
For most personal photo libraries, cloud storage as the offsite copy is the practical choice. The requirement is geographic separation, not any specific technology.
What a 3-2-1 Setup Actually Looks Like
A realistic implementation for a personal photo library:
Copy 1: Your phone or computer (the working copy)
This is the original — the photos on your camera roll, the files actively in use on your laptop. This isn’t really a “backup” so much as the source of truth for recent content.
Copy 2: An external drive or local backup (local secondary)
A dedicated external drive, running automated regular backups. This gives you fast, offline recovery if your device fails or is stolen. No internet required to restore.
Copy 3: Cloud storage (the offsite copy)
An encrypted cloud service with automatic sync or regular upload. This protects against location-based failures — the drive and the computer in the same bag, a house fire, anything that takes out your physical location.
This combination covers:
- Device failure → restore from local backup (fast, no internet needed)
- Stolen device → restore from cloud (available anywhere)
- Local disaster → cloud copy is unaffected
- Cloud provider failure → local backup is available
- Accidental deletion → cloud version history or local backup covers this
The Frequency Problem
Three copies don’t help if two of them are months out of date.
A backup frequency that most people can realistically maintain:
Continuous for cloud. Most cloud storage apps offer automatic sync — files are uploaded as they’re created. The cloud copy stays current without any manual work.
Weekly for local backup. Automated software running weekly (Time Machine on Mac, File History on Windows, or a dedicated backup application) gives you a recent local copy without requiring manual effort.
After significant events. Manually verifying that a backup ran successfully after an important event — a trip, a wedding, a birth — is worth doing even if you have automation. Automation can fail silently, and you don’t want to find out during a restore.
Common Mistakes That Break the Rule
Using sync as a backup. Cloud sync (Google Drive, iCloud Drive, Dropbox) is not a backup in the 3-2-1 sense. If you delete a file, sync removes it from the cloud too. If ransomware encrypts all your files, sync uploads the encrypted versions. A backup needs version history or point-in-time snapshots, not just mirroring.
Counting two copies in the same account. If both copies are in the same Google account (Google Photos + Google Drive), they’re not independent. A compromised account, a policy violation ban, or a billing failure takes both out simultaneously.
Treating photo sharing as backup. Photos in a shared album, on a family group chat, or posted to social media are not backups. They’re often compressed, you may not have admin control, and they can be deleted by other participants or platform policy.
Not testing restoration. A backup you’ve never restored from may not work when you need it. Periodically restoring a few random files — especially after changing backup systems or hardware — is the only way to confirm your backup actually functions.
The Privacy Dimension
The 3-2-1 rule is usually taught as data loss prevention, but there’s a parallel privacy consideration: which of the three copies is most private depends on where it lives.
Local copies are fully under your control. No third party can access them without physical access to your device.
Cloud copies depend on the provider’s privacy practices, security architecture, and business model. A cloud copy at a service that encrypts at rest, doesn’t use content for AI training, and doesn’t sell data is a meaningfully different privacy position than a free service funded by advertising.
If you’re applying the 3-2-1 rule to sensitive content — personal photos, medical records, private documents — the offsite cloud copy should be at a service you’ve actively chosen for its privacy commitments, not the default sync that came with your device.
daftei serves the cloud copy role with AES-256 encryption at rest, TLS 1.3 in transit, no advertising, no third-party AI training on your content, and GDPR and CCPA compliance — on iOS, Android, and web. 5GB free to start, with unlimited storage on Pro at $5.99/month or $44.99/year.
Making It Concrete
The 3-2-1 rule is useful because it’s specific enough to act on. Most backup failures aren’t technical — they’re the result of no clear decision having been made.
A minimal implementation that most people can set up in an afternoon:
- Enable automatic cloud backup for your phone’s photos
- Set up automated weekly backups from your computer to an external drive
- Verify both ran successfully after setting them up
Three copies (phone, external drive, cloud). Two media types (local drive, cloud). One offsite (cloud). Nothing exotic, nothing expensive, nothing that requires ongoing maintenance beyond occasional verification.
The most reliable backup is the one that exists, runs automatically, and you’ve confirmed actually restores.