Chapter 37 — Further Reading

Workflow, backup, and archiving are the least glamorous corners of the craft and the best-documented — because the people who lost work went on to write down exactly how not to. The resources below are grouped by purpose. Where a specific figure or date would be a guess, the source is attributed cautiously; nothing here is invented. Start with the foundations, then reach for the practice guides when you build your own system.

Learning-path tags: 📱 phone-first · 🎥 creator · 💼 pro-track · 🎓 student.

Foundational books

• Steven Ascher & Edward Pincus — The Filmmaker's Handbook. The standard single-volume reference for the whole craft, and the one this book points to again and again. Its chapters on post-production workflow, file formats, and long-term storage are the calm, authoritative version of everything in this chapter; keep it on the shelf and read the media-management and archiving sections when you set up your system. (All paths; essential for 💼/🎓.)

• Peter Krogh — The DAM Book: Digital Asset Management for Photographers. The 3-2-1 backup rule is widely credited to this book, and although it is written for photographers, its treatment of copies, verification, cataloging, and long-term storage is the clearest articulation of the discipline anywhere — it maps directly onto video. If you read one thing about why your files survive or don't, read Krogh on backup and verification. (💼/🎓; the single best deep-dive on this chapter's core.)

• Walter Murch — In the Blink of an Eye. Not a workflow book — it is the great short book on editing philosophy — but it belongs here because it captures the professional mindset this chapter is really about: the senior craftsperson's respect for their material and their process. Read it for the disposition that makes a person keep three copies without being told to. (🎥/💼/🎓.)

Practice guides, standards, and reputable sites

• National cybersecurity agencies on the 3-2-1 rule. Public bodies such as the U.S. cybersecurity agency (CISA, formerly US-CERT) have long promoted the 3-2-1 rule in their guidance on protecting data against loss and ransomware. Search for their current backup guidance for a short, authoritative statement of the rule and its reasoning — useful when you need to justify the habit to a client or an employer. (💼/🎓.)

• The Library of Congress — Digital Preservation / "Personal Archiving." The U.S. Library of Congress publishes free, plain-language guidance on preserving personal digital files — photos, video, and documents — including copies, formats, and migration. It is the institutional version of §37.5 written for ordinary people; genuinely the best free primer on keeping files alive across years. (All paths; especially 🎓.)

• Blackmagic Design — the official DaVinci Resolve manual and free training. The Resolve documentation covers media management, relinking, generating proxies (optimized media), and — directly relevant here — exporting a project archive (the self-contained bundle for handoff and archive from §37.5–37.6). Because Resolve is free, this is the most accessible place to learn the exact buttons behind this chapter's principles. (All paths; the free software path.)

• No Film School (nofilmschool.com). A long-running, reputable independent filmmaking site with steady, practical coverage of post workflow, media management, drives, and delivery. Good for real-world "here's how a working editor sets up a project" articles that translate the principles into current tools. (🎥/💼.)

• Frame.io Insider (the Frame.io blog). A well-regarded industry blog covering professional post-production workflow, collaboration, and data management, often written by working editors and colorists. Skew toward higher-end pipelines, but the reasoning about organization, review versions, and handoff generalizes down to any budget. (💼.)

• Backblaze blog and "Drive Stats." Backblaze, a cloud-backup company, publicly publishes large-scale statistics on hard-drive failure rates, along with approachable guides on backup strategy. It is the best free evidence for the blunt claim under §37.3 — drives fail, on a schedule, and you cannot predict which one — and it will make you take the "3" in 3-2-1 seriously. (💼/🎓.)

Standards & storage worth knowing by name

• LTO (Linear Tape-Open). The open tape-storage standard used for deep archiving across the film and television industry because it is cheap per terabyte and stable for long shelf life. You likely will not buy an LTO deck as a solo creator, but knowing it exists — and why serious archives use it (§37.4–37.5) — tells you what "grown-up archiving" looks like and where your own habits are heading. (💼/🎓; conceptual for most readers.)

• Checksums / verified copies (the concept). The idea that a copy should be re-read and confirmed against its source (introduced at ingest in Chapter 27 and revisited for archive integrity in §37.5). Read any plain explanation of file checksums / hashes to understand how a tool "knows" a copy is perfect and how the same check later catches silent decay ("bit rot"). This one concept underlies both safe offloads and trustworthy archives. (💼/🎓; skippable for 📱.)

• The Association of Moving Image Archivists (AMIA). The professional body for people whose entire job is keeping film and video alive over decades. Their public resources are where the amateur "keep three copies" habit grows up into a discipline — file formats for preservation, storage media lifespans, and migration practice. You do not need to become an archivist, but skimming how the professionals think will permanently raise your standards for your own back catalog. (💼/🎓; conceptual.)

Documented cases to read about (cautionary and instructive)

These are real, widely-reported episodes; treat specific figures in press coverage with healthy caution, as reports vary. Read them for the pattern, not the numbers.

• The BBC (and other broadcasters') archive wiping and junking of the 1960s–70s — the subject of this chapter's Case Study 1. There is extensive, well-documented public writing on how television recordings were erased or discarded, and on the decades-long recovery from overseas film prints and fans' off-air recordings. It is the definitive real-world lesson in the value of finished work lives in the future and redundancy is what survives. (All paths; pairs with Case Study 1.)

• The near-loss of Toy Story 2 (Pixar, late 1990s). Recounted publicly by the studio (and referenced in Chapter 27): a deletion command and a failing backup nearly erased the film, which was saved by an unofficial off-site copy. The clearest short parable of "one fragile copy and an unverified backup," told about a studio that should have been immune. (All paths.)

• The 2019 MySpace media loss and the 2008 Universal Studios vault fire. Two widely-reported cases — years of user-uploaded music reportedly lost in a server migration, and master recordings destroyed in a fire — that illustrate, respectively, migration without verification and a single-location archive with no off-site copy. Read them as §37.3 and §37.5 failures at scale. (💼/🎓.)

Tools & apps (as categories, with the free path)

Named as classes of tool per this book's rule — the principle matters more than the product, and every one has a free or built-in path.

• Verified-copy offload tools. Dedicated apps that copy from cards to multiple drives with checksum verification (well-known professional examples include Hedge, ShotPut Pro, and Pomfort's Silverstack). The free path: your editor's own verified clone/copy (Resolve's Clone tool), a verifying file-copier (such as TeraCopy on Windows), or a checksum-capable copy command (rsync). Whatever the tool, insist on verification, not a naked drag. (All paths.)

• The editor's project-archive / consolidate function. For archiving and handoff (§37.5–37.6): DaVinci Resolve's Export Project Archive, or the "collect/consolidate files" command in other suites (mapped in Appendix E). The free path is built into Resolve. (All paths.)

• Cloud backup / storage services. For the off-site "1" in 3-2-1: a backup service (e.g., Backblaze) or a sync/storage service used as a copy, not as your only backup (remember §37.3 — sync propagates deletions). The free path: a free-tier cloud account for your most precious project until you can afford more. (📱/🎥/💼.)

A suggested order

1. Start with the mindset and the rule: the media-management and archiving sections of Ascher & Pincus, then Krogh's DAM Book on backup and verification. Between them you will understand why before you touch a tool.
2. Make it real in free software: the DaVinci Resolve manual on media management, proxies, project archive, and relinking — do it on an actual project as you read.
3. Scare yourself usefully: read the Backblaze drive-failure stats and the BBC/Pixar/MySpace cases. Nothing motivates a backup like watching how ordinary the losses are.
4. Institutionalize it: the Library of Congress personal-archiving guidance, then skim what LTO and checksums are, so your kitchen-table habits are consciously the same cycle a real archive runs.

Read items 1–2 before your next real project; let 3–4 be the reading that turns "I should back up" into "I never don't." None of this reading is urgent the way a shoot is urgent — which is exactly why most people never do it, and why the few who do are the ones still holding their work a decade later. Treat one item a week as maintenance on your career, the same way you'd clean a lens.