A Photo Backup Strategy That Survives a Stolen Laptop

What 3-2-1 actually requires, and where people cheat

Each number in the rule closes a different failure. Reading them as separate questions makes it harder to cheat.

The laptop bag is the classic cheat. A stolen bag takes the laptop, the backup drive and often the cards in one event. If your only second copy travels with the first, you have one copy with extra weight.

Sync is the other. A folder mirrored to a cloud service is a copy, but it mirrors mistakes too. Delete a folder, or let ransomware encrypt it, and the sync dutifully propagates that. Treat sync as a convenience copy and make sure at least one copy is versioned or otherwise cannot be silently overwritten by the machine it protects.

Shoot day: protecting the card before ingest

The riskiest moment in the whole workflow is the stretch when the only copy of the shoot is a card in your pocket. A card that fails, is lost, or is left in a rental car has no second life. The fix is to make the card stop being the only copy as early as the shoot allows.

• Write to two cards in camera if your body has two slots. It costs nothing in workflow and removes the single-card failure entirely.
• Do not reformat until three copies exist. A common rule is to hold the cards until the files are verified on the working drive and one backup, then keep them until the off-site copy is done. The cards are your cheapest extra copy; do not erase them early.
• Ingest with verification. Use ingest software that checksums the copy against the source rather than a drag in Finder or Explorer, where a silently failed file looks like a finished transfer.
• Split the travel. Cards in one pocket, the ingest drive in a different bag, never both in the checked case.

On location, the same logic applies to the second copy. If you are shooting a multi-day job away from home, a small portable SSD that stays in a different place from the laptop is worth more than a larger drive that sits next to it. The aim is not a perfect system on day one; it is that no single event, whether a dropped bag, a hotel-room theft or a failed card reader, can take every copy at once. Ask of each moment in the shoot: what is the one thing that, if lost right now, loses the work?

The storage math for one shoot day

Whether you can afford three copies is a question of arithmetic, not guesswork. Take an example job, with numbers you should replace with your own: 3,000 frames at an average 45 MB per raw file.

3,000 frames × 45 MB = 135,000 MB, roughly 135 GB per shoot (using 1 GB = 1,000 MB, as drive makers do). Add exports and a catalog and call it 150 GB. Three copies is therefore 450 GB for one job.

10 TB is 10,000 GB, and 10,000 ÷ 450 is about 22. If you shoot two jobs of this size a week, that is a little over ten weeks of three-copy capacity before you must archive or expand. The point of doing the sum is to see that backup capacity is a recurring line item, and to decide which jobs graduate to cold storage rather than discover the drive is full mid-shoot.

The in-progress catalog: the copy people forget

Finished work is easy to back up because it sits still. The exposed copy is the catalog and the intermediate files of a job in progress: the cull, the ratings, the edit history, the layered files. A raw-only backup protects the pixels but throws away the hours you spent deciding which pixels matter.

Two practical habits cover most of it. First, keep the catalog and its working files inside the same folder tree the backup job already watches, so it cannot be left out by omission. Second, back up on a schedule that matches how much work you can afford to redo. If you edit for four hours a day and back up nightly, the exposure is a day. Back up hourly and the exposure is an hour. Pick the loss you can live with, then set the interval to match it.

Consistent folder and file naming matters here more than it seems. When you are restoring in a hurry, a tree you can read at a glance is the difference between ten minutes and an afternoon; our guide to file naming conventions for photo teams covers a scheme that survives a restore.

Off-site without drama

The off-site copy is the one most often skipped, because it feels like a chore. There are two realistic ways to do it, and they trade effort against recovery time.

Many photographers use both: a cloud backup for the always-current layer and a rotated drive for the archive. Whichever you choose, check the upload arithmetic before you rely on it. A 135 GB shoot on a 20 Mbps uplink is 135 × 8,000 megabits ÷ 20 Mbps = 54,000 seconds, which is 15 hours of continuous upload. Your own connection will differ, but the sum tells you whether overnight is enough or whether you need to prioritise the catalog and exports first and let raw files trail behind.

Also decide what happens to old jobs. Keeping every gallery online forever is a cost, and our piece on how long to keep client photo galleries online walks through the retention trade-off. Backup retention and client-facing retention are separate decisions, and mixing them up is how people delete the only copy of something a client later asks for.

Test the restore, because an untested backup is a hope

A backup you have never restored is a belief, not a fact. Drives fail quietly, backup jobs get misconfigured after an update, and a folder excluded last year stays excluded. The only real check is to restore something and open it.

1. Quarterly: pick a job at random, restore it to a different drive from the backup (not the original) and open a dozen raw files at full size.
2. After any change: new laptop, new backup software, new drive, restore once before trusting it.
3. Annually: pretend the laptop is gone. Can you get the active jobs, the catalog and your business files back using only the off-site copy and a blank machine? Write down what was missing.

Finally, write the plan down in plain language and keep a copy off the machine it describes: where each copy lives, which drive is rotated when, which account holds the cloud backup and where its recovery key is stored. A backup system that only you understand fails the day you are ill, travelling, or replaced by a stand-in who has to recover a client's job. Include the one-line answer to what you would do first if the laptop disappeared tonight. People who have rehearsed that answer lose hours; people who have not lose days.

One boundary worth stating: a client review link is not part of this. Review tools such as Appruva hold the versions and notes of a review round, but they are not a substitute for your own archive of masters, and you should not treat them as one.