The hard lesson Nine PBS offers about archival storage
NAS storage archival refers to keeping long‑lived, rarely changed data on a dedicated network‑attached storage device that an organization owns and controls, instead of relying entirely on third‑party cloud vendors whose contracts, business health, and technical practices can abruptly determine whether critical history is preserved or lost. Nine PBS is living proof of how badly that bet on someone else’s infrastructure can go. The station had more than 50TB of archival material spanning roughly 70 years stored with cloud vendor Open Source Storage (OSS) when it suddenly lost access earlier this year after OSS apparently went out of business. The contract, in theory, gave Nine PBS 30 days to retrieve its data, but the vendor cut off access on the day the agreement expired and then disappeared from contact. That is not a freak accident; it is exactly the kind of single point of failure that a sound data preservation strategy is supposed to avoid.
When your history lives on someone else’s balance sheet
Nine PBS had been working with OSS and its predecessor since 2019, renewing the relationship year after year for hardware, software, and cloud‑based archival storage. Things broke when a renewal meeting in February went unanswered and OSS went silent. On March 6, the day the contract was set to expire, the company cut off access without warning even though the station still officially had 30 days to pull its data. According to reporting on the case, the material encompasses over 50TB and represents “70 years of our organization’s history,” as Nine PBS executive Leah Freeman put it. The station later discovered that OSS was delinquent with state authorities and had been housing its servers at an Iron Mountain data center, turning a simple storage contract into a three‑way legal knot over who controls the archive and who is allowed to hand it back.
Why local NAS beats the cloud for preservation
What makes the Nine PBS story infuriating is how preventable the technical side of this disaster was. Commentators have pointed out that it is strange for a major organization not to maintain at least one on‑premises copy of such a critical archive when one can buy a multi‑bay NAS and fill it with large hard drives for long‑term storage. A NAS storage archival setup would have given the station direct control over at least one full copy of the 50TB archive, insulated from cloud vendor reliability and corporate drama. The 3‑2‑1 backup rule exists for exactly this reason: keep three copies of your files, on two different media types, with one copy off‑site. In that model, the cloud is the off‑site extra, not the single source of truth. On‑premises network storage backup means you can keep working and recovering data even if a provider folds overnight.
Cloud contracts are not backup strategies
Nine PBS’s predicament shows how organizations confuse having a cloud bill with having a data preservation strategy. The contract’s 30‑day retrieval window looked reasonable on paper, but as this case shows, that clause is worthless when a vendor stops responding. Outsourcing storage does not outsource responsibility; a vendor’s financial health and behavior now sit squarely inside your risk model. A single provider holding your only copy is not a backup, it is a single point of failure that can vanish when a company collapses or changes hands. For working shooters, small studios, and cultural institutions alike, the practical move is to keep at least one copy on media you physically control, verify restores on a schedule, and ask every storage vendor a blunt question: what happens to our data if your company goes under? If your plan relies on goodwill instead of clear answers, you do not have a plan.
Data sovereignty: owning both the bits and the recovery path
The legal tangle around Nine PBS’s archive exposes the difference between owning data in theory and controlling it in practice. After OSS vanished, the station sued to assert its rights, and a court ruled that Nine PBS had the right to access its data and that OSS should facilitate transfer to a new vendor. Only then did Iron Mountain acknowledge it held the data, before later claiming the servers belonged to OSS and refusing to release anything without further legal clarity. Another judge has since granted temporary relief barring Iron Mountain from deleting, modifying, or overwriting the material while the case proceeds. In short, the archive’s fate now hinges on court orders and third‑party risk tolerance rather than the station’s technical capabilities. On‑premises network storage backup would not eliminate legal issues around ownership, but it would give Nine PBS better data sovereignty and recovery options: the ability to restore from hardware in its own racks, on its own timeline. The lesson is blunt: the cloud is a useful copy, not a safe vault, and a $1,000 NAS under your control beats a perfect SLA that evaporates the moment a vendor disappears.
