← Back
Creator Hardware, Storage, NAS Archiving & Technical Workflows

A backup policy retains daily versions but no monthly or annual generations, making long-term recovery impossible after a corruption event is discovered weeks later.

Problem

A backup policy retains daily versions but no monthly or annual generations, making long-term recovery impossible after a corruption event is discovered weeks later.

Solution

Root Cause / Diagnostic:
A backup schedule configured exclusively for daily retention (e.g., keep 7 daily backups) automatically overwrites all retained versions within one week. If a file corruption event, missing asset, or subtle NLE bug goes unnoticed for 10 days, all clean historical backups have already been pruned, leaving no recovery point.

Actionable Fix:
1. Grandfather-Father-Son (GFS) Retention Policy: Implement a GFS backup retention schedule: retain 7 daily backups, 4 weekly backups, 12 monthly backups, and 1 annual archive.
2. Immutable Milestone Snapshots: Create permanent, immutable snapshots at major production milestones (e.g., Picture Lock, Color Conformed, Final Delivery).
3. Historical Version Retrieval Audit: Quarterly, test-restore a project file from 60 days prior to ensure intermediate generations remain fully functional and uncorrupted.

Pro Tip:
A 7-day backup rotation won't save you if you discover a corrupted clip two weeks after the shoot; use a Grandfather-Father-Son retention policy so you always have monthly archive restore points.