Ok, it sucks, losing data always sucks, but what ever happened to the 3-2-1 backup rule? even if your off site backup provider goes tits up, your on site backup is still there.
If you don't want on site, a second off site provider, 50TB on backblaze would be an extra ~$350 per month (prob less if they were to commit to capacity instead of using their PAYG service)
> but what ever happened to the 3-2-1 backup rule?
I wasn't 100% sure, but the data backs this up[0]; the "3-2-1 backup rule" is a relatively modern concept, at least by that name. I also remember things like "have one backup in one place, another in another place" since before this mnemonic, but I feel like it's unfair to judge a 70+ years archive on something that just recently actually became a widespread mantra.
- [0] Interestingly, Ngram (https://books.google.com/ngrams/graph?content=%5B3-2-1+backu...) says ~2010 while Trends (https://trends.google.com/explore?q=3-2-1%2520backup%2520rul...) says slow build up from ~2020, guess "everyday" language would sit somewhere around those two different truths.
The concept of multiple copies in multiple locations already existed when backups on CD-R were common, so 20+ years ago. The “2” in the 3-2-1 rule refers to using different physical storage media and predates cloud storage.
I can pretty clearly remember hearing about the "3-2-1 backup rule" by name 10 or 15 years ago on the Security Now podcast with Steve Gibson. So it is _at least_ that old, but probably even older. The concept of having multiple backups is not at all new, however. Since I've been involved with computers (~30 years), I have heard folks say things like "two is one, one is none" in reference to backups and data replication in general.
Also, this TV station has not been sending their show archives to Iron Mountain for the past 70 years. Probably what happened was: In 2019, they had an on-site or nearby archive. Then some enterprising IT director came along and convinced management that they would save a bunch of money and time by outsourcing everything to a third party who said they could do it for cheap. Very confident in their genius, they then scrapped their own archive entirely.
Part of me pities them for ending up in this situation, the other part of me believes they got everything they asked for.
> I also remember things like "have one backup in one place, another in another place" since before this mnemonic
I've heard variations of this all the way back to some 1990s vocational IT courses in the country I live, and it wasn't even technologically advanced at the time. It's hard to have any sympathy for someone who misses this concept in today's age.
> the "3-2-1 backup rule" is a relatively modern concept, at least by that name. I also remember things like "have one backup in one place, another in another place" since before this mnemonic, but I feel like it's unfair to judge a 70+ years archive on something that just recently actually became a widespread mantra.
They signed up with them in 2019. Not long ago.
Even if it is a "new" concept, common sense isn't. Pretty much anyone who cares about their data will do the due diligence, and this is not something that requires technical chops. This has been a concern for well over 20 years!
It really sounds like some senior management trying to be cheap.
This has been a rule for like 30+ years (I have only been in the industry that long). Whether it was called "3-2-1" before that or not, the practice is the same. Have an onsite backup, have an offsite backup. This isn't a new concept at all.
I'm under the impression that "two is one and one is none" is old military slang.
The 3-2-1 rule is ~20years old at this point. But just because an archive is "old" doesn't mean we can't apply modern standards to that archive as time marches on, otherwise the BM_ARC would have never been build and opened a couple of years ago.
I mean, that 70+ year old archive must have been digitised at some point, unless Iron Mountain was storing the reel to reel tapes and/or film from the original recordings. So some "modernation" has been applied to it since its creation.
Wouldn't be surprised if it wasn't digitised. TV was using BetacamXR up until very recently (and still might be). Tape is pretty reliable and lasts awhile.
Now add in tons of other legacy formats and digitising becomes a pretty big cost for a public station.
From the article: It's not clear if the channel has backups of its data, but based on its determination, we suspect not. This is strange, though, especially for a major organization, as one can easily purchase a six-bay NAS on Amazon and populate it with the best HDDs. This also goes against the 3-2-1 backup rule, which says you should keep three copies of your files stored in two different mediums, with one of them running offsite. Hopefully Nine PBS will implement a better backup system once it regains access to its data.
It's worth noting that PBS affiliates are non-profits that have fairly constrained budgets, especially now that the Corporation for Public Broadcasting has been dissolved due to DOGE.
Non-profit IT has always seemed, to me at least, to be a land of compromises. There's rarely enough money, knowledge, or time to do things "the right way", so you have to do the best you can. If I could only choose one backup to have, it'd be remote on a provider like Iron Mountain. It would seem as if they are storing things on Iron Mountain through an intermediary company, who may or may not have actually paid the bill.
So, y'know, fraud's a possibility here.
The guillotine is too nice for the people that dissolved the CPB. That just makes me so mad. How many children learned via the CPB like me? America isn’t even the same without CPB and I guess that’s why these traitors did it.
It's nice to know that even in the end the CPB lived up to its mission and promise and swallowed its poison pill rather than be corrupted by partisan politics, but it's also gross to have seen that forewarned poison pill needed in my lifetime. There's some hope that we can still find the next Mr. Rogers to put a heart on a sleeve in front of some future Congress and build a sequel CPB with similar strong core principles.