If you ask anyone who works in data recovery what backup strategy individuals should follow, you will almost always get the same answer: the 3-2-1 rule. Three copies of your data, stored on two different types of media, with one copy kept off-site.
It is simple enough to fit on a sticky note, which is part of why it has lasted for decades. But most people who believe they are following it are not — and the most common reason is that uploading photos to a cloud service feels like backup when it is often something different entirely.
What the 3-2-1 Rule Actually Requires
The rule was formalized by photographer Peter Krogh as a practical standard for digital photography workflow. It has since been adopted by IT professionals, data recovery services, and backup software companies as the minimum baseline for reliable data protection.
Breaking it down:
Three copies means your original data plus two additional copies. The original alone is not a backup — it is just your data. The first additional copy protects you from accidental deletion, corruption, or hardware failure on the primary. The second protects you when the first copy also fails, which happens more often than people expect.
Two different types of media means not relying on the same technology for all copies. If you have three copies on the same external hard drive brand, a manufacturing defect that affects that model could take out all three. Two different media types — local hard drive and cloud storage, for instance — mean a failure mode that affects one type will not affect the other.
One off-site copy means at least one of your copies is physically located somewhere other than your home or primary location. This protects against events that affect a physical location: fire, flood, theft, and other disasters that destroy everything at a single site simultaneously.
The Critical Distinction: Sync vs. Backup
Here is the gap between believing you follow the rule and actually following it.
If your photos exist on your phone and in one cloud service, you have two copies — not three. You are short by one. More importantly, both copies are probably linked by a sync relationship, which is fundamentally different from a backup.
Cloud sync means the cloud copy mirrors whatever is on your device. If you delete a photo from your phone, the sync service deletes it from the cloud. If ransomware encrypts your device files and the sync catches up before you notice, it overwrites the cloud copy with encrypted versions. If you accidentally empty your trash, the sync propagates that deletion.
Sync protects against device hardware failure — if your phone breaks, you can restore from the cloud. But it does not protect against data you delete (accidentally or intentionally), ransomware that arrives before the cloud copy can be separately preserved, or account-level events that affect both your device and your cloud service simultaneously.
Backup creates a separate copy that is not automatically affected by changes to the original. True backup services version your files — keeping previous states that you can restore even after deletion or corruption. Many cloud storage services are primarily sync services, not backup services. The distinction matters enormously for the 3-2-1 calculation.
Applying the Rule Correctly
A minimal setup that actually satisfies the 3-2-1 rule for personal photos:
Copy 1 (original): Photos on your phone or primary device.
Copy 2 (different local media): An external hard drive or SSD at home, synchronized manually or on a schedule. This is your local safety net — fast to access, no internet required for recovery, and not affected by your cloud service going offline or changing its terms.
Copy 3 (off-site): A cloud storage service, or a physical drive kept at a separate location — a relative’s house, a safe deposit box. This is what saves you when your home is the problem.
For most people, a phone plus an external drive at home plus a cloud service satisfies the rule. The weakness is usually the middle element: most people have the phone and the cloud service, but no local backup they actually maintain.
What a 3-2-1 Setup Looks Like in Practice
Here is a concrete example that works without specialized knowledge:
- Copy 1: Google Photos or iCloud syncing your phone automatically
- Copy 2: A 2TB external SSD connected periodically to a laptop, with photos exported from the app to the drive
- Copy 3: A separate cloud storage account, or a drive kept at a trusted location away from home
The off-site element is where most people fall short. If copies 1 and 3 are both cloud services — iCloud and Google Photos, for example — you have two copies on cloud servers you do not control, and your local copy (if you even have one) is the only physically distinct location in the chain.
Two cloud accounts from different providers is better than one, because different vendors have different failure modes. But it still leaves you without a local copy you can access without internet, and without protection against account-level attacks that compromise both services via the same email address.
Why Single-Cloud Is Not Enough
It is easy to assume that a major cloud provider constitutes reliable redundancy on its own — that Google Photos or iCloud automatically keeps multiple copies in multiple data centers, so your one subscription is effectively giving you several copies.
This reasoning misses the point of the rule. The cloud service is one account, one vendor, and one attack surface. If your account is compromised, an attacker has access to your files regardless of how many data center redundancies the provider uses internally. If the provider changes its terms, raises prices dramatically, or discontinues the service, you have a problem with every copy of your data simultaneously. If ransomware on your device syncs to your cloud copy before you catch it, all versions in that account may reflect the encrypted state.
The 3-2-1 rule distributes risk across media types, vendors, and physical locations. The redundancy inside a single provider’s infrastructure addresses hardware failure, not the other risks.
The Case for a Dedicated Second Cloud
If maintaining a physical external drive feels like too much friction, a second cloud service from a different vendor — with a different email address and no sync relationship to your primary device — functions as a true off-site copy.
The key is that this second cloud account is not synced automatically to your primary device. You periodically upload your photo exports to it. Because it is not in a sync relationship with your device, a deletion on your phone does not propagate, and ransomware on your device cannot reach it without your manual action.
This is where a storage-focused service — one dedicated to keeping what you put there rather than syncing with your device — fills a distinct role in a layered backup strategy. You export photos from your primary service on a schedule and upload them here, giving you a versioned copy that is not affected by what happens on your primary device or your primary cloud account.
Updated Variations: 3-2-1-1-0 and Beyond
Data professionals have extended the original rule to account for modern threat models, particularly ransomware.
3-2-1-1-0 adds one offline or air-gapped copy — a drive not connected to the internet — and zero errors verified, meaning you have actually tested that your backups can be restored. The offline copy addresses the ransomware sync problem: an encrypted device cannot infect a drive that is not connected.
Immutable copies — a cloud copy with versioning that cannot be overwritten or deleted even by the account holder for a set period — are another extension. Some backup services offer this as a ransomware-specific protection: past file states are retained for 30, 90, or 180 days regardless of subsequent changes.
For most individuals protecting personal photos, the base 3-2-1 rule is sufficient if correctly implemented. The extensions matter most when the data is critical and irreplaceable — like a complete family photo archive spanning decades.
Testing Your Backup
The single most common failure mode in backup strategies is discovering the backups do not work when you actually need them.
Testing looks like: pick a file that exists in your backup copy and try to restore it to a different location. Confirm the file is intact and accessible. For an external drive backup, this means connecting the drive and verifying you can open the files. For a cloud backup, this means actually downloading a file and opening it — not just checking that the file is listed.
Many people skip this step because it feels redundant. The only time it becomes urgent is when something has gone wrong with the primary copy, which is exactly when discovering the backup is corrupt or inaccessible is catastrophic.
A simple testing schedule: pick one day every three to six months, download or open ten files from each backup copy, and confirm they are intact. That is enough to catch silent backup failures before they become data loss events.
Where daftei Fits in a 3-2-1 Strategy
daftei’s 5 GB free tier provides enough space to evaluate it as one component of a backup strategy — testing how the upload process works, how files are organized, and whether access from different devices is straightforward. The Pro tier offers unlimited storage for $5.99/month, $44.99/year, or $89.99 as a one-time lifetime payment (₹249/month or ₹1,799/year in India).
As a purpose-built storage service rather than a sync client, daftei stores what you upload without mirroring your primary device. Files are encrypted at rest with AES-256 and in transit with TLS 1.3. There is no advertising, no data selling, and no AI training on your uploaded content.
In a 3-2-1 setup, that makes daftei suitable as an intentional off-site copy — one that you populate by exporting and uploading rather than by syncing, and that is not subject to the same failure modes as your primary sync-based cloud account.
Building the Habit
The practical failure of the 3-2-1 rule is not conceptual — people understand the principle. It is behavioral: the off-site or secondary copy does not get updated because it requires manual action.
Automation helps where it is available. The harder element is the local backup — setting a recurring reminder to connect an external drive periodically removes the reliance on memory.
For photo libraries specifically, the stakes are high. Unlike most files, photos cannot be recreated. The irreplaceability of personal photos makes them exactly the category worth applying the full rule to, even when it requires more effort than a single cloud subscription provides.
The test of a backup strategy is not whether it exists. It is whether it protects you when everything goes wrong at once.