The 3-2-1 rule says: keep three copies of anything you care about, on two different kinds of storage, with one copy somewhere else. It is easy to recite, and most setups that fail it fail because nobody asked what each number is actually for.
What each number defends against
Three copies exists because copies fail independently, and one spare is not enough once you account for the window where a failure has happened but you have not noticed. The copy count includes the original: your laptop plus two backups is three.
Two kinds of storage is about correlated failure. Two identical drives bought together, from the same batch, plugged into the same machine, have an unfortunate habit of failing in the same season. Different media - a drive and cloud storage, say - do not share failure modes.
One offsite is for the events that take out a whole location: fire, flood, theft, a power surge with opinions. An external drive on the same desk as the laptop it protects fails the spirit of the rule while satisfying the letter.
The ways setups quietly fail the rule
Sync is not a copy. A sync folder mirrors deletions and overwrites, so it counts as availability, not backup - the distinction matters. Versioned storage recovers individual mistakes, but for the 3-2-1 count you want at least one copy that a bad day on your primary machine cannot reach.
RAID is not a copy either. RAID keeps a disk failure from being an outage. It replicates deletions instantly, which makes it one copy with better uptime, not two.
The forgotten external drive. A backup that depends on remembering to plug something in degrades to whenever-you-last-remembered. Automation is not a luxury here; the schedule is the backup.
Setup one: a personal machine
The laptop is copy one. An external drive that a scheduled job writes to - Time Machine, File History, or a weekly rsync - is copy two. Cloud storage is copy three and the offsite.
For the cloud leg, rclone is the dependable workhorse. We expose an S3-compatible API precisely so tools like it work without anything bespoke:
rclone sync ~/Documents dosya:backup/documentson a schedule satisfies the offsite copy with one line. The developer docs cover the remote setup.
Setup two: a photo library
Photos are the file type people most regret losing, and the camera roll usually holds the only copy. Phone plus automatic photo backup to cloud storage is two copies, one offsite, achieved entirely by installing an app. A periodic export of the library to an external drive completes the three.
Setup three: a server
Machines nobody sits at need the schedule to do everything. Backing up a server to object storage with cron walks through the full arrangement - the short version is a nightly job, a retention policy, and a restore you have actually tested. The server’s own disk is copy one, object storage is the offsite, and a second bucket or a periodic pull to another machine is the third leg.
The parts people skip
Test a restore. A backup you have never restored from is a hope, not a backup. Once a quarter, pick a file and get it back. The first restore attempt finds the misconfiguration; you want that discovery on a calm afternoon.
Version the backups. A backup that only holds the latest state inherits the sync problem - it faithfully copies the ransomware-encrypted versions over the good ones. Storage that keeps prior versions means the offsite copy holds history, not just the present.
Size it honestly. The rule fails economically if the offsite leg cannot hold the real collection. Our sizing guide has the arithmetic, and for large archives the cold versus hot storage trade-off is worth understanding before choosing where the third copy lives.
The honest minimum
If three legs is more than you will actually maintain, do two well: automatic sync with versioning for the working set, and one scheduled offsite copy of the irreplaceable subset. That covers the failures that actually happen - deletion, device loss, one bad drive - and a maintained two-leg setup beats an abandoned three-leg one every time.
Frequently asked questions
What does the 3-2-1 backup rule mean?
Keep three copies of your data, store them on two different kinds of storage, and keep one copy somewhere physically separate. The original counts as one of the three.
Does RAID count as a backup?
No. RAID keeps a disk failure from causing downtime, but it replicates deletions and corruption instantly, so it is one copy with better uptime rather than two copies.
What is the easiest way to get an offsite backup copy?
Cloud storage is offsite by definition. A scheduled job with a tool like rclone pointed at S3-compatible storage satisfies the offsite leg with one command per night.
