A public television station does not have to lose a single file for its backup plan to fail. Nine PBS says it was cut off from more than 50 terabytes of archival material spanning 70 years. The data may still exist inside an Iron Mountain facility. The station has still had to go to court to prevent deletion and regain access.

That distinction matters. This is not a confirmed story of destroyed data. It is a story about losing control of the only practical route to your own files. For a business, a nonprofit, or a person with irreplaceable records, the result can feel exactly the same.

Image note: The featured photo shows the former PBS headquarters in Arlington, Virginia, not Nine PBS or Iron Mountain. Photo by Thomson200 via Wikimedia Commons, dedicated to the public domain under CC0 1.0.

What Happened to Nine PBS’s Archive?

Nine PBS, the public television station in St. Louis, stored decades of programming and local history through a company called Open Source Storage, or OSS. The relationship began in 2019 and renewed annually. When the latest agreement expired in March 2026, the station expected time to retrieve or transfer its material. Instead, it says its access ended immediately and the vendor stopped responding.

The archive is not a pile of replaceable media. It includes the station’s coverage of East St. Louis, the COVID-19 pandemic, and the Great Flood of 1993. A report from Current says Nine PBS is seeking more than 50 terabytes that represent “70 years of our organization’s history.”

OSS had its own relationship with Iron Mountain, which housed the storage infrastructure in a Denver-area data center. That created a difficult chain. Nine PBS owned the material. OSS controlled the service. Iron Mountain held the physical systems. When OSS apparently went defunct, nobody left in the chain had a simple way to hand the station its files.

Tom’s Hardware reported that the station had stored more than 50TB with OSS before suddenly losing access earlier this year. Nine PBS first obtained a default judgment in St. Louis stating that it owned the data and had an immediate right to possess it. The court ordered OSS to return the material or help transfer it to a new vendor.

That did not solve the practical problem. Iron Mountain acknowledged holding the systems, according to the complaint, but said OSS owned the infrastructure that housed the files. Nine PBS then filed a separate lawsuit in Denver on July 28. Current reported the case on August 11. At that point, a judge had granted temporary protection against deletion, modification, or overwriting while the dispute continued.

Has the Archive Actually Been Lost?

No destruction has been confirmed in the reporting available as of August 13. Nine PBS’s problem is blocked access and the risk that the material could be changed or deleted before it can be recovered. That is serious, but it is different from saying 70 years of television history are already gone.

The legal distinction is important too. A court can decide who owns data. That ruling does not instantly produce a working copy. Someone still needs credentials, compatible hardware, a transfer method, enough time, and cooperation from the people who control the system. Ownership on paper and recoverability in practice are not the same thing.

The Real Failure Was One Point of Control

It would be easy to file this under “the cloud failed.” That is too simple. Cloud services can be dependable, geographically distributed, and far safer than one drive sitting under a desk. The problem is assuming that storage with one provider is automatically a complete backup plan.

If the same company controls the live storage, the backup, the account, and the export path, those copies may share one failure point. A billing dispute, lost administrator account, vendor shutdown, contract problem, or security incident can block all of them at once. The files may sit on several machines and still depend on one permission.

That is the uncomfortable lesson in the Nine PBS case. The station’s archive was stored off-site, but the path back to it ran through a vendor that stopped functioning. The data center underneath that vendor was not necessarily in a direct customer relationship with the station. Technical redundancy did not remove the contractual dependency.

What Counts as a Real Backup?

A real backup is an independent copy you can recover without relying on the same event, account, vendor, or device that took the original away. It should be current enough to matter, protected from casual deletion, and tested before an emergency.

The National Institute of Standards and Technology recommends that organizations conduct, maintain, and test backup files to reduce the impact of data-loss events. All three verbs matter. Creating a copy once is not the same as maintaining it, and maintaining it is not proof that it can be restored.

The familiar 3-2-1 rule is still a useful starting point: keep three copies of important data, use two different types of storage, and keep one copy off-site or otherwise isolated. I would add one more question for anything entrusted to a service provider: can you retrieve a usable copy without that provider’s cooperation?

A Backup You Can’t Restore Is Only a Promise

The restore test is where assumptions become evidence. You do not need to simulate a total disaster every week. You do need to prove, on a schedule that fits the value and pace of the data, that the copy opens and that someone knows how to use it.

  • Identify what cannot be replaced. Start with original media, financial records, customer data, contracts, website databases, and the working files that keep the business moving.
  • Put one copy under separate control. Use a different account, provider, device, or location. Separate credentials matter as much as separate hardware.
  • Protect the recovery keys. Document who owns the accounts, where encryption keys are kept, and how access transfers if an employee or vendor disappears.
  • Restore a sample. Open a file, rebuild a folder, or restore a copy of the website somewhere safe. A green “backup complete” message is not a restore test.
  • Plan the exit before you need it. Know the export format, cost, time window, and contract language for retrieving your data when a relationship ends.

For a WordPress site, this is why a maintenance plan should include a tested recovery path, not just plugin updates and a dashboard that says backups ran. The copy should include the database and files, live somewhere independent of the production server, and be restorable without guessing.

This Risk Is Much Smaller Than 50TB

Most people will never manage a television archive. They still face the same design problem at a smaller scale.

Your website host may advertise daily backups, but the copies may live inside the same account as the website. Your company may keep every contract and project in one shared drive. Your phone may sync photos to one cloud account. Sync is convenient, but it can also copy an accidental deletion or bad change everywhere.

A security incident is only one way files become unavailable. That is why layers that reduce the chance of a website hack still need a separate recovery plan behind them. Prevention lowers risk. Backup limits the damage when prevention, equipment, a person, or a vendor fails.

I tell clients this all the time because the size of the archive does not change the principle. Whether the subject is a website, personal information, family photos, company files, or 70 years of television history, you should know where the second copy lives and prove that you can get it back.

Frequently Asked Questions

Is Cloud Storage the Same as a Backup?

Not by itself. Cloud storage can be one part of a backup system, but a single cloud account may still be one point of failure. A backup should give you an independent recovery path if that account, provider, or login becomes unavailable.

Was the Nine PBS Archive Deleted?

There is no confirmed report that the archive was deleted as of August 13. Nine PBS says it lost access and sought a court order to prevent the material from being deleted, changed, or overwritten while it works to recover it.

Does the 3-2-1 Rule Guarantee My Data Is Safe?

No rule is a guarantee. The 3-2-1 approach reduces the chance that one device, location, provider, or mistake takes every copy at once. It only works if the copies are current, protected, and recoverable.

How Often Should I Test a Backup?

Test often enough that a failed restore will not surprise you after months of unusable copies. The right schedule depends on how quickly the data changes and what downtime would cost. Test again after changing providers, backup tools, credentials, or hosting.

What Should I Back Up First?

Start with anything irreplaceable or necessary to resume work: original photos and video, customer and accounting records, contracts, website files and databases, active project files, and the credentials or keys needed to restore them.

The Point Is Independence, Not Panic

The Nine PBS dispute is unusual in scale, but not in principle. Important data should not depend on one company staying in business, one contract staying friendly, or one account staying open. If this story made you question your own setup, review the practical website backup steps and apply the same independence test to the rest of your files.