A Photography Backup Workflow That Never Loses a Wedding

There is exactly one unrecoverable failure in this business: losing a client's photographs. Everything else (a missed frame, a late delivery, a difficult client) can be apologised for. A lost wedding cannot. And it happens, mostly to competent people who had a backup routine that was one drive short of adequate.

This is a working backup routine for a photography business: the standard professionals use, what it looks like on a wedding day, and the specific failure modes that catch people out.

Table of Contents

• The 3-2-1 rule
• On the day: before you leave the venue
• That night
• During the edit
• After delivery: the archive
• How long to keep client work
• Six ways backups fail
• The checklist

The 3-2-1 rule

The industry standard, borrowed from IT and worth following exactly: three copies of the data, on two different media, with one off-site.

The reasoning is about correlated failure. Two copies on two drives in the same bag are one theft, one fire or one spilled drink away from zero. Off-site means a different physical place: cloud storage counts, and for most photographers cloud is the practical third copy.

On the day: before you leave the venue

• Shoot to dual card slots with the camera writing the same images to both cards simultaneously. This is the single highest-value habit in this article: a card failure mid-ceremony becomes a non-event. If your body doesn't have dual slots, changing cards more often at least limits the loss.
• Never format a card in the field. Carry enough cards for the whole day. The cost of extra cards is trivial against the cost of a formatted ceremony.
• Keep the two cards separate. One in the camera bag, one on your person. Different physical locations, immediately.

That night

Tired is exactly when this gets skipped, which is why it should be mechanical:

1. Copy both cards to your working drive, a laptop or a fast external SSD.
2. Copy again to a second drive. Two copies on two devices before you sleep.
3. Start the cloud upload. It can run overnight; you now have or are getting your third, off-site copy.
4. Verify. Check the file count matches and open a few frames at random. A copy that silently failed is worse than no copy, because you believe in it.
5. Only then consider the cards reusable, and ideally not until after delivery.

During the edit

Your catalogue and edits need backing up too, and this is where photographers who back up raw files diligently still lose weeks of work. Back up the catalogue file itself, and remember that most editing software stores edits in the catalogue rather than the image, so losing it means re-editing everything even though the raws survived. Most tools offer scheduled catalogue backups; switch it on.

After delivery: the archive

Once delivered, the working copy stops mattering and the archive begins. A sane structure:

• Delivered JPEGs. Small, and the thing clients ask for again. Keep these indefinitely; they're a few gigabytes per wedding.
• Selected raws. The keepers, for re-edits and album work.
• Everything else. The full raw take. Large, rarely needed. Keep for a defined period, then thin.

If your delivery reads from cloud storage rather than a separate upload, your delivered JPEGs are simultaneously your archive and your live gallery, which removes a copy rather than adding one. The storage math covers what each strategy costs annually.

How long to keep client work

Say it in the contract so it's a policy rather than an anxiety. Common practice: delivered images kept indefinitely (they're small), full raws for one to three years. Couples come back at anniversaries wanting a print or a re-edit, and being the photographer who still has them is worth more than the storage costs.

Just be careful the promise matches reality: "we keep your photos forever" is a commitment, and it should be one you've actually engineered.

Six ways backups fail

1. All copies in one bag. One theft from a car, everything gone. Separate them the moment you can.
2. A single external drive treated as a backup. Drives fail without warning; one copy is not a backup.
3. Never verifying. Silent copy failures are common. Check counts, open files.
4. Cloud sync mistaken for backup. Sync propagates deletions: delete locally, it deletes remotely. Versioning or a separate backup destination is what saves you.
5. Formatting cards too early. Wait until delivery.
6. Forgetting the catalogue. Raws without edits is weeks of lost work.

The checklist

When	Action
Before the day	Enough cards for the whole event; dual-slot backup enabled; drives have space
During	Never format; keep cards in two places
That night	Copy to two drives; start cloud upload; verify counts
Edit week	Catalogue backup scheduled
On delivery	Delivered JPEGs into the archive; cards now reusable
Quarterly	Test-restore something at random; an untested backup is a hope

The last row is the one everybody skips and the one that reveals whether any of the rest actually worked.