← Back to Blog
Infrastructure6 min readJanuary 30, 2025

The 3-2-1 Backup Strategy Every Post-Production Team Needs

Drive failures, ransomware, and accidental deletion destroy projects every day. The 3-2-1 backup rule is the industry standard for protecting your work. Here's how to implement it.

The Rule That Saves Careers

The 3-2-1 backup rule is simple:

  • ◆3 copies of your data
  • ◆2 different storage media types
  • ◆1 offsite copy

    • It sounds obvious. Most studios don't follow it. Then a RAID fails, a drive is stolen, a freelancer accidentally deletes a project folder, or ransomware encrypts the NAS, and the phone calls start.

    This guide explains how to implement 3-2-1 for a post-production environment.

    Why RAID Is Not a Backup

    This misconception costs studios dearly. A RAID array protects against drive failure. It does not protect against:

  • ◆Ransomware (encrypts all files including the RAID array)
  • ◆Accidental deletion (deleted files are gone from all drives in the RAID)
  • ◆Theft (someone takes the NAS)
  • ◆Fire/flood (destroys the physical array)

    • RAID is for availability. Backups are for recovery. You need both.

    Copy 1: Working Storage (Primary NAS)

    Your primary NAS is where active project files live. This should be:

  • ◆RAID 6 for arrays with 6+ drives (tolerates two simultaneous failures)
  • ◆Regular S.M.A.R.T. monitoring (QNAP, Synology, and TrueNAS all support this natively)
  • ◆Automated alerts for drive health warnings

    • Think of this as your first copy.

    Copy 2: Local Backup (Separate Device)

    Your second copy should be on different physical hardware from your primary NAS, either a separate NAS unit or a dedicated backup server. This protects against:

  • ◆Primary NAS failure (hardware fault, firmware bug)
  • ◆Accidental deletion (as long as you don't back up immediately)

    • Implementation options:

  • ◆Second NAS: Synology Active Backup and QNAP Hybrid Backup support scheduled replication to a secondary unit on the same network
  • ◆Direct-attached storage: A large external drive array connected to a workstation or server, running backup software (Veeam, Arq, Carbon Copy Cloner)
  • ◆LTO Tape: An LTO-8 or LTO-9 tape drive connected to a server provides 12 to 18 TB native per tape at very low cost per TB. Ideal for archiving completed projects.

    • Version retention: Configure your backup software to keep multiple restore points (daily snapshots for 30 days, weekly snapshots for 6 months). This allows you to roll back to a clean copy if ransomware or accidental deletion isn't discovered immediately.

    Copy 3: Offsite Backup

    Your third copy must be physically separate from your studio. This protects against:

  • ◆Fire, flood, earthquake
  • ◆Theft
  • ◆Any physical disaster that affects your studio location

    • Options by scale:

    Cloud backup (S3/Glacier). AWS S3 Glacier Deep Archive costs approximately $1/TB/month for archival storage. Tools like Arq Backup, Veeam, and Synology Hybrid Backup Manager support S3-compatible targets. For a 50TB archive, that's $50/month.

    Backblaze B2. S3-compatible with a better price point ($6/TB/month for hot storage, free egress to Cloudflare). Strong choice for studios needing frequent access to offsite backups.

    Second physical location. If your agency has multiple offices, or you have a trusted facility nearby, replicating to a second physical NAS over a site-to-site VPN provides fast restoration speeds and no ongoing cloud costs.

    Automating the Backup

    A backup strategy that depends on humans remembering to run backups will eventually fail. Automate everything:

  • ◆Primary to local backup: Nightly automated replication job (2:00 AM, after rendering is done)
  • ◆Local backup to cloud: Daily or weekly incremental sync (verify with monthly restore test)
  • ◆Archive to LTO tape: Monthly or upon project completion

    • Schedule a quarterly restore test. Actually pull a file back from each backup tier. Untested backups are not backups.

    Special Considerations for Pre-Release Content

    Studios handling pre-release content for major studios or streaming platforms have additional requirements:

  • ◆Offsite backups of pre-release content must use encrypted storage (AES-256 minimum)
  • ◆Cloud backup destinations must be contracted vendors with appropriate DPA (Data Processing Agreements)
  • ◆Backup access logs may be required by content owners

    • For TPN-certified studios, backup and recovery procedures are part of the assessment framework.

    Clouds Agency designs and implements backup and storage infrastructure for post-production studios in Los Angeles. Contact us to design a backup system that fits your workflow.

    Written by the team at Clouds Agency, a Los Angeles creative and production consulting agency.

    ← All PostsContact Us →