How to Back Up Video Footage So You Never Lose a Client Project
Every production company has a story about the drive that died. Ours involved a two-day shoot, a portable SSD that survived the flight home, and a card reader that decided to corrupt the transfer at 1 a.m. the night before the edit started. We recovered it — barely — and that week changed how we handle footage forever.
Here’s the uncomfortable truth about this business: the camera work is maybe 40% of what a client pays for. The rest is trust that their footage — the CEO interview they can’t reshoot, the product launch that happened once — will still exist next month. Lose a drive and you don’t just lose files. You lose the client, and usually a few referrals with them.
This is the system that’s kept us safe. None of it is exotic, and most of it costs less than one reshoot day.
The 3-2-1 rule, and why most crews only do the “3”
The rule itself is simple: three copies of everything, on two different types of storage, with one copy off-site.
Most shooters get the first number right. Three copies feels responsible — the original cards, a working drive, a backup drive. But if all three live in the same edit bay, you have one copy for insurance purposes. A power surge, a burst pipe, or a break-in takes all of them in the same afternoon. Ransomware does it even faster, because it happily encrypts every drive plugged into the infected machine, backups included.
“Two different types of storage” means don’t put everything on the same brand of drive bought in the same batch. Drives from one production run tend to fail around the same time. Mix an SSD with a spinning NAS, or local drives with cloud archive.
“One off-site” is the part that saves companies. Cloud archive tiers (Backblaze B2, AWS Glacier, Wasabi) now cost a few dollars per terabyte per month. For a shoot that billed five figures, that’s not an expense. That’s the cheapest insurance policy you’ll ever buy.
On set: back up before you wrap
The most dangerous hours in a footage’s life are between “cut” and “ingested.” One card in one pocket is a single point of failure walking through an airport.
Our rule: no card gets formatted, and nobody leaves location, until the footage exists in two places. In practice that means offloading to two drives on set — one for the editor, one that travels home in a different bag, ideally with a different person. Software like Hedge or ShotPut Pro does checksummed copies, which matters more than people think: a checksum verifies the copy is bit-for-bit identical, instead of trusting that a progress bar reaching 100% means the files are actually intact. (It doesn’t. Ask our 1 a.m. card reader.)
If you’re a one-person crew, the two-bag rule still works. Offload at lunch. It costs you fifteen minutes and one extra SSD.
The edit: working storage is not backup storage
A RAID array in the edit suite is a performance tool, not a backup. RAID protects you from one drive failing inside the box. It does nothing against deletion, corruption, theft, ransomware, or the box itself dying. If your NAS is your only copy, you have zero backups with extra steps.
What works: the NAS holds active projects, a scheduled job pushes nightly changes to cloud storage, and finished projects get archived (more on that below) before they’re cleared off working storage. The key word is scheduled. Backups that depend on someone remembering to run them stop happening during crunch weeks — which is exactly when the most valuable footage is on the drives.
This is also the point where a lot of studios realize they’ve outgrown DIY. When you’re juggling a NAS, cloud sync, user accounts for freelancers, and a growing pile of “is this backed up?” questions, it’s worth having a professional set it up once and monitor it continuously. We’ve seen production companies hand this off to managed IT services firms the same way clients hand video off to us — because doing it properly requires attention that’s better spent elsewhere. The good ones will also test your restores, which brings us to the step everyone skips.
Actually test a restore
A backup you’ve never restored from is a hope, not a backup. Twice a year, pick a random finished project and pull it back from your archive completely — cloud tier, LTO tape, wherever it lives. Time it. If restoring one project takes four days, you want to know that on a calm Tuesday, not the morning a client emails asking for their 2023 brand film because their agency lost it.
That email comes more often than you’d expect, and saying “give us two days” instead of “I’m so sorry” is the moment a past client becomes a repeat client.
Client delivery: stop emailing WeTransfer links with no expiry
Delivery is part of security too. A public download link that never expires is footage you no longer control — it gets forwarded, indexed, and occasionally scraped. Use expiring links, password-protect anything with unreleased products or executives on camera, and keep a record of what was delivered where. If a client works under NDA (and if you shoot for tech companies, they all do), being able to answer “who could access this file, and when?” is the difference between a professional operation and an awkward phone call.
Same logic applies to your freelancers. Editors and colorists need access to active projects — they don’t need standing access to your entire archive from their personal laptop forever. Give access per project, take it back when the project wraps. It’s not about trusting people less; it’s about limiting how much damage one stolen laptop can do.
The short version
Copy on set before anyone leaves. Three copies, two media types, one off-site — automated, not manual. RAID is not backup. Test a restore twice a year. Expire your delivery links. And when the storage side of the business starts eating hours you should be spending on shoots, treat it like a client treats video: hire people who do it every day, like the team at EverpineLab, and get back to work.
The footage you protect is the reel you’ll book next year’s clients with. Guard it accordingly.