Guide

The 3-2-1 backup rule, explained for a family photo archive

The 3-2-1 backup rule is old, boring, and not specific to photos at all — IT departments have used a version of it for decades to protect business data. But it happens to be exactly the right amount of structure for something as irreplaceable as a family's photo archive, and it's worth understanding properly rather than picking up secondhand as "have backups, I guess."

Here's the rule in one sentence: 3 total copies of your data, on 2 different kinds of media, with 1 of those copies offsite. That's it. The rest of this post is just what those three numbers actually mean when the data in question is twenty years of photos that can't be retaken.

A tax document you lose can be reissued. A photo of a grandparent who has since passed cannot.

The rule, as three numbers

3
total copies of your photos
2
different kinds of media
1
copy kept offsite

Each number is doing a specific job, and it's worth being clear about what that job is, because skipping any one of them quietly reintroduces a real failure mode.

Why 3 copies, not 2

Two copies sounds like a backup. It's actually a working copy and a spare, and the moment one of them fails, you're back down to a single copy with no safety net while you sort out a replacement. Three copies means that even while you're dealing with a failed drive, you still have two intact copies — the archive is never one single event away from having no backup at all.

Why 2 different kinds of media

This is the number people get wrong most often, because it's tempting to satisfy "more than one copy" with two drives that are, in every way that matters, identical: same model, same age, bought at the same time, possibly from the same batch. If one has a manufacturing flaw or fails from age, the other is disturbingly likely to fail the same way, on a similar timeline. "Two different kinds of media" means your second copy should differ from your first in some real way — a different drive, a NAS instead of a second plain drive, or a cloud service instead of physical hardware at all. The goal is that whatever kills one copy has no particular reason to also kill the other.

Why 1 copy offsite

Two copies sitting on the same desk, or even in the same house, both go up in the same house fire, both get taken in the same burglary, and both get destroyed in the same flood. "Offsite" means physically somewhere else — a drive at a relative's house, a safe deposit box, or a cloud backup service. It's the one part of the rule that specifically protects against a disaster big enough to take out an entire location, rather than just a single piece of hardware.

A dense pile of hundreds of vintage family photo prints
Photo by hatice via Pexels

What this looks like for an actual family

Translated out of abstract "copies" and into what a normal household actually has sitting around, 3-2-1 for a photo archive usually looks something like this:

Notice that none of this requires anything exotic. It's two drives you already understand how to use, plus a decision about where the third copy physically sits. The comparison of external drives, NAS devices, and cloud storage is the right next read if you haven't settled on what Copy 1 and Copy 2 should actually be — this post is about the shape of the plan; that one is about which physical option fits your household.

You don't have to do all three at once. Getting from zero backups to a single second copy is already a large improvement over a single drive. Add the offsite copy once the first two are in place and working. A partial 3-2-1 setup you actually maintain beats a complete one you set up once and never touch again.

Being honest about the effort

None of this is free. A second drive costs money. An offsite copy, whether it's a drive at a relative's house or a cloud subscription, costs either a recurring fee or the mild social overhead of asking someone to hold onto a drive for you and occasionally swap it. Keeping all of it in sync takes a recurring block of time, even if it's small — an hour every few months, not a daily chore, but a real recurring one nonetheless.

It's fair to ask whether that's worth it. Here's the honest case for why it is, specifically for photos, in a way that doesn't apply to most other data on your devices: a financial record, a contract, a spreadsheet — almost anything else you might lose has a second author. A bank can reissue a statement. A company can resend a contract. You can rebuild a spreadsheet from memory or from someone else's copy. A photo of a specific afternoon, with specific people, at a specific age, has exactly one author, and once it's gone, there is no institution or person anywhere who can recreate it. That asymmetry — replaceable data has other sources, family photos don't — is the actual argument for spending real effort on backups that you wouldn't necessarily spend on, say, your music library.

Most data has a second author somewhere. A family photo doesn't.

This matters most for an archive that's already worth protecting — meaning one that's actually organized, so it's not five scattered partial collections but one coherent thing worth the effort of a real backup plan. If you haven't done that step yet, our guide on organizing decades of scattered family photos is worth doing first; backing up a mess just gives you a backed-up mess.

The good news: this doesn't have to be manual forever

Once the 3-2-1 structure exists — a working copy, a second local copy, one offsite — the ongoing task is mostly just periodic syncing, which is a lot less daunting than the plan sounds on paper. And once your archive is actually organized and properly backed up across more than one location, it becomes worth investing in making it pleasant to actually use, not just safe to lose.

Once your archive is properly backed up, this is worth a look.
All Our Years doesn't replace any part of the 3-2-1 plan above — it doesn't back up, replicate, or store anything offsite. It's an organizing and viewing layer that reads your existing working copy in place, on your Mac, with nothing uploaded or moved. Once your archive is properly backed up, this is the kind of tool that makes it worth actually looking at. For the phone side of getting photos off a device before they're backed up at all, see our iPhone offload guide.
See how it works

FAQ

What does "2 different kinds of media" actually mean?

Your two local copies shouldn't be two identical drives from the same batch bought at the same time. Two different drives, or a drive plus a NAS, satisfy it — the point is that whatever causes one copy to fail shouldn't be equally likely to take out the other at the same time.

Does cloud storage count as my offsite copy?

Yes, if it's used purely as a backup rather than as your day-to-day way of viewing photos. A cloud service you actually browse from is really your working copy in a different location, not an independent offsite backup — it still inherits the recurring-cost and third-party-dependency tradeoffs of relying on one company.

How often should I update each backup copy?

The working copy updates itself as you add photos. The second local copy and the offsite copy just need refreshing often enough that a disaster today doesn't cost a year of unbacked-up photos — every few months, or right after a major event like a trip, is a reasonable rhythm for most families.

Is 3-2-1 overkill for a home photo archive?

For a folder of vacation snapshots, maybe. For decades of a family's only copies of moments that can never be retaken, no. The rule isn't really about the number three — it's about not letting one single point of failure stand between you and photos that have no second author who could ever recreate them.

What's the difference between 3-2-1 and just having a NAS with redundant drives?

A NAS with redundant drives protects against one drive inside it failing. It doesn't protect against the NAS itself being stolen, flooded, or destroyed in a fire, since every drive is still in one physical location. 3-2-1 requires at least one copy somewhere else entirely, which a NAS alone — however redundant — can't provide on its own.

← Back to all posts · Next: External drive vs. NAS vs. cloud for family photos →