Problem
A backup repository reaches its retention threshold and automatically prunes old projects before the creator notices that a long-term archive policy has been violated.
Solution
Root Cause / Diagnostic:
Automated backup retention scripts often operate on strict disk-space triggers (e.g., "delete oldest backups when free space drops below 10%"). If a creator adds massive new raw shoots without expanding the backup pool, the pruning algorithm aggressively purges older finished client projects to free space, silently destroying valuable archives.
Actionable Fix:
1. Explicit Archive vs. Backup Separation: Decouple operational daily scratch backups from permanent project archives by routing completed projects to dedicated cold storage pools (LTO tape or AWS S3 Glacier Deep Archive).
2. Pruning Policy Lockdown & Quotas: Remove automated space-triggered auto-deletion; configure backup software to halt and send alert notifications instead of silently pruning project archives.
3. Retention Policy Audit: Review repository retention policies to ensure an explicit minimum retention guarantee (e.g., 365 days or "Never Delete Marked Masters") is strictly enforced.
Pro Tip:
Don't let your backup software automatically delete old projects when the drive gets full; separate your daily working backups from permanent archives so old client work never gets silently deleted.
Automated backup retention scripts often operate on strict disk-space triggers (e.g., "delete oldest backups when free space drops below 10%"). If a creator adds massive new raw shoots without expanding the backup pool, the pruning algorithm aggressively purges older finished client projects to free space, silently destroying valuable archives.
Actionable Fix:
1. Explicit Archive vs. Backup Separation: Decouple operational daily scratch backups from permanent project archives by routing completed projects to dedicated cold storage pools (LTO tape or AWS S3 Glacier Deep Archive).
2. Pruning Policy Lockdown & Quotas: Remove automated space-triggered auto-deletion; configure backup software to halt and send alert notifications instead of silently pruning project archives.
3. Retention Policy Audit: Review repository retention policies to ensure an explicit minimum retention guarantee (e.g., 365 days or "Never Delete Marked Masters") is strictly enforced.
Pro Tip:
Don't let your backup software automatically delete old projects when the drive gets full; separate your daily working backups from permanent archives so old client work never gets silently deleted.