Seventy Years of Tape in a Mountain: What the PBS Ruling Says About Data You Cannot Re-Download

The story is easy to misread as a fight over ownership. A court cleared Nine PBS to retrieve 70 years of archival television data - roughly 50TB - from Iron Mountain after the company hosting it went under. The station's ownership of the material was not really the open question. Access was. That distinction is the part worth keeping, for anyone with a library they care about.

Most people will never store broadcast masters in a mountain. Almost everyone now keeps something that cannot be re-downloaded - family video, scanned documents, a decade of messages - in a place they control less than they assume.

Ownership and access are different things

The third row is the one people overrate and the second is the one they underrate. Owning a disk is not the same as having a copy, and renting space is not the same as losing control - until the invoice, the vendor or the hardware changes hands.

An exit plan you can test in an afternoon

1. Step 1 List the irreplaceable set

   Not everything. Family video, scanned documents, messages, the photos with no negative and no second copy. Write the list down, because the set is smaller than the library and it is the only part that justifies effort.

2. Step 2 Copy files out in formats something else can open

   Original files plus a common container. A library that only opens inside one application is a library you have borrowed, not one you own.

3. Step 3 Export the metadata

   Titles, dates, people, tags. This is the part that is genuinely lost when a host fails, because the files can sometimes be copied later while the catalogue that made them searchable usually cannot.

4. Step 4 Open a sample from the copy, on another device

   Three files, picked at random, opened on a machine that was not involved in making the copy. A backup you have never opened is a hypothesis.

5. Step 5 Keep three copies on two kinds of media, one of them off-site

   The old rule still works because it survives the failures that actually happen: a drive dies, a house floods, an account is locked. One copy cannot cover any of those.

6. Step 6 Put the next test in the calendar

   A yearly reminder beats good intentions. Archives fail slowly and then all at once, usually the week after the hardware warranty ends.

Signs an archive is one invoice away from trouble

• The only route to the files is one app and one account, with no export button.
• The catalogue lives in a proprietary database with no readable dump.
• Nobody has opened a file from the backup in the last year.
• The host is a small company whose business model is not obviously funded.
• There is a single copy, and it is in the same building as the thing it protects.
• Restoring is described as "we will deal with it if it happens".

Was the dispute about who owned the archive?

As reported, the station owned the material; the dispute was about retrieving physical media held by a third party after the host went under. That is why the ruling matters outside broadcasting: ownership without retrieval is a filing cabinet you cannot open.

What does this mean for phone photos?

That a copy you can open without the app is worth more than a sync that says everything is backed up. If the only route to your photos is one account and one application, you have access rather than a copy.

How often should a restore be tested?

Once a year is enough for a personal archive, and it takes minutes: choose three files at random, open them on a second device, and check that the dates and metadata travelled with them.

Is a second cloud account enough of a backup?

It covers a deleted file and a lost phone. It does not cover a closed account, a billing failure, or a provider that changes its terms - which is exactly the failure the ruling was about.