The 3-2-1 Backup Strategy for Narrative Clip Memories

Summary. The 3-2-1 backup rule is forty years old and still works: three copies, two media, one off-site. This guide adapts it specifically to a lifelogging archive — where the volumes are high, the years are long, and a single vendor going dark is the failure most owners actually live through. We walk through three working setups by budget, the mistakes people repeat, and a calm plan for getting your archive to 3-2-1 within a month.

The rule, in one paragraph

Keep three copies of every photo. Use at least two different kinds of storage so one bad batch or one bad event does not take all copies. Make sure one copy is physically separated from the others — a different building, ideally a different city. That is the rule. Everything else in this article is implementation.

Why this rule, for a lifelogging archive specifically

A lifelogging archive lives or dies on years, not weeks. The failure modes that take it out are:

1. Vendor closure. The Narrative Clip cloud is the cautionary tale that gave this domain its name. We wrote it up in what happened to Narrative Clip and the cloud shutdown explainer. Cloud-only archives die when the cloud dies. 3-2-1 prevents this because the other two copies still exist.
2. Account suspension. Google, Apple, and Microsoft all suspend accounts via automated review, sometimes incorrectly. The lockout duration is effectively a data loss for the lockout window. 3-2-1 prevents this because the local copies remain accessible.
3. Drive death. Mechanical and SSD drives both fail. Mirroring (RAID) helps but is not enough — RAID is for availability, not backup. 3-2-1 prevents this because at least one of the two media survives any single-drive event.
4. Ransomware. A drive plugged in continuously is a drive ransomware can encrypt. 3-2-1 prevents this when the cold local copy is unplugged most of the time, and the cloud copy is versioned.
5. House fire / flood / theft. All three local copies in the same building are one event from gone. 3-2-1 prevents this because the off-site copy is in a different building.
6. Accidental deletion or sync error. A Cmd+A, Delete in the wrong window propagates through any sync tool. 3-2-1 with a versioned cloud backup prevents this because the cloud has prior snapshots.

A single-cloud or single-NAS setup addresses one or two of these. 3-2-1 addresses all of them.

Three working setups by budget

Budget — about $260 first year, $80/year ongoing

For a 1–2 TB archive that grows slowly. Single household, single laptop.

1. Working library. Photos live on the laptop’s internal drive, organized by year/month. Apple Photos, Google Photos local sync, or plain folders.
2. Local backup. A 12 TB WD Elements desktop USB drive plugged in once a month. Time Machine on Mac, File History plus Arq on Windows, restic on Linux. Unplugged the rest of the time.
3. Off-site. Backblaze Personal Backup, $9 a month per machine for unlimited backup. Or restic snapshots to Backblaze B2 at roughly $6 per terabyte per month.

This is a real 3-2-1 setup. It is not exciting. It works for years.

Mid — about $1,000 first year, $90/year ongoing

For a 2–8 TB archive across multiple devices. Household with a Narrative or modern wearable plus a couple of phones plus a laptop.

1. Working library. Two-bay Synology DS224+ with two 8 TB drives in mirror, running Synology Photos plus Immich in Docker. Phones auto-upload; laptops sync.
2. Local backup. A 4 TB Samsung T9 portable SSD plugged into the NAS once a month for Hyper Backup. Unplugged the rest of the time.
3. Off-site. Backblaze B2 with restic, scheduled nightly from the NAS. Roughly $5 a month at 1 TB of changed data, scaling with archive size.

This is the setup most readers of this site end up at. The NAS handles the working library and a real backup target; the SSD is cold; the cloud is versioned.

Comprehensive — about $2,500 first year, $200/year ongoing

For an 8+ TB archive that you genuinely cannot afford to lose, often a multi-decade family photo + video pool.

1. Working library. Four-bay Synology DS423+ with four 8 TB drives in SHR-2 (two-drive fault tolerance), 16 TB usable. Immich + Synology Photos.
2. Local backup. A second two-bay NAS in another room, configured for Snapshot Replication from the primary. Plus a 4 TB external SSD rotated to a relative’s house quarterly.
3. Off-site. Backblaze B2 nightly via restic for the immediate off-site. Plus the rotated external SSD at the relative’s house for a true second-site copy that doesn’t depend on any cloud.

This setup has two off-site copies (cloud + relative) and survives essentially every realistic failure mode short of a global infrastructure event.

Affiliate disclosure: This page contains affiliate links. If you buy or sign up through them, NarrativeClip may earn a commission at no extra cost to you. Our recommendations are editorially independent. Read more.

The mistakes people repeat

After years of editorial coverage and reader stories, the mistakes that cost people their archives cluster into a small set. Don’t make them.

”The drive is plugged in 24/7, so it’s always backed up.”

A drive that is always mounted is a drive that ransomware can encrypt, that an rm -rf can wipe, and that a power surge past the UPS can fry. Plug in to back up. Unplug after. The drive in the drawer is the one that survives the bad day.

”iCloud has my photos, so I’m fine.”

iCloud is a sync, not a backup. A delete on one device propagates everywhere. Apple’s account-recovery story is among the best of any consumer cloud, but it is still one suspension or family-share argument from being inaccessible. Use iCloud as part of a 3-2-1, not as the whole strategy.

”I made the backup, so I’m done.”

A backup that has never been restored is a hope. Test the restore once a quarter for the first year, then every six months. Pick a random folder, restore it to a different location, open one of the files. If the restore tool refuses, you have just learned the most important thing your archive has to teach you, and you have learned it before you needed the data back.

”I’ll set up off-site once the local part is done.”

Local-only is one fire from total loss. Set up the off-site leg at the same time as the local one, even if it starts with only the most important folders. You can scale off-site later; you cannot un-burn a house.

”I’ll just buy two of the same external drive.”

Two identical drives from the same order have correlated failure timing. Mix brands and ideally batches. A WD Elements and a Samsung T9 are a better pair than two T9s.

”I’ll just dump everything to the cloud, it’s their problem.”

Storage providers run real businesses with real terms. Even the best of them — and we recommend several — have closed services, reset pricing, or suspended accounts. The cloud is one leg of three, not the whole table.

The off-site copy, in detail

This is the leg people skip most often, so it gets its own section.

Encrypted cloud. Backblaze B2 or Cloudflare R2 with restic, rclone crypt, or Duplicacy. The provider sees ciphertext only; you hold the key. Pricing in 2026 is roughly $5–$6 per TB per month at B2, with sensible egress. We use B2 ourselves for our test archive.

Versioned commercial backup. Backblaze Personal Backup, IDrive, or Carbonite. Less control, simpler operation. Versioning protects against accidental deletes propagating.

Rotated drive at a second location. A 4 TB external SSD that lives at a parent’s or sibling’s house, swapped quarterly. Free of recurring cost, dependent on the relationship. Best paired with a cloud copy rather than instead of.

A safe-deposit box. Rare but legitimate. A small SSD in a bank safe-deposit box, updated annually, is a real off-site backup for the most important slice of an archive — wedding photos, the early years of a child’s life, the irreplaceable.

What is not off-site: a USB drive in a desk drawer in the same building. A house fire is the most likely event that takes the working library; that drive goes with it.

A 30-day plan to get to 3-2-1

If you are not at 3-2-1 today, here is a calendar that gets you there in a month without panic.

• Week 1: inventory. Find every place your photos currently live. Phones, laptops, old hard drives in a shoebox, Google Photos, iCloud, the Narrative export ZIP from 2016. Make a list. Estimate the total size. You will be surprised; everyone is.
• Week 2: pick a tier. Use the three tiers above. Order the hardware in one purchase — drive, NAS if applicable, UPS if applicable. Sign up for the cloud leg the same week. Do not optimize for six months while your only copy is on a phone.
• Week 3: build the working library. Import everything into one canonical location. Plain folders by year/month if you want maximum portability; Immich or Synology Photos if you want the app experience. Resolve duplicates (PhotoSweeper on Mac, Czkawka cross-platform).
• Week 4: build the backup legs. Run the first local backup. Run the first cloud backup. Test a restore from each. Block ninety minutes; you will need them. Write down the encryption keys on paper and put them somewhere your executor can find them.

After the month, the maintenance load is small: a monthly external-drive plug-in, a check on the cloud backup status, and a restore test every six months.

Related reading

• Best cloud storage for Narrative Clip photos and lifelogging archives
• Best NAS setups for personal photo and video archives
• How much storage do you need for years of wearable camera photos?
• Backblaze B2, Wasabi, Amazon S3, or consumer cloud — what should photo archivists use?
• How to back up lifelogging photos in 2026
• How to build a simple home archive for old wearable camera photos

Frequently asked questions