Earlier quoted context omitted.
If the US government and corporate executives had even half this level of shame, we'd have nobody left in those positions!
Not the same country but another example of a culturally similar attitude towards shame over failure: In Japan in 1985, Flight 123, a massive Boeing 747 carrying 524 people, lost control shortly after takeoff from Tokyo en route to Osaka. The plane's aft pressure bulkhead catastrophically exploded, causing total decompression at the high altitude, severing all four of the massive plane's hydraulic stabilizer systems…
Fire destroys S. Korean government's cloud storage system, no backups available
571–580 of 987 posts
Re: Fire destroys S. Korean government's cloud storage system, no backups available
#572Earlier quoted context omitted.
You can buy a 24Tb drive on sale for $240 or so. Sometimes I wonder why I still try and save disk space :-/
Link? Am both curious and skeptical
Re: Fire destroys S. Korean government's cloud storage system, no backups available
#573Earlier quoted context omitted.
The issue here is not refusing to use a foreign third party. That makes sense. The issue is mandating the use of remote storage and not backing it up. That’s insane. It’s like the most basic amount of preparation you do. It’s recommended to even the smallest of companies specifically because a fire is a risk. That’s gross mismanagement.
> The issue here is not refusing to use a foreign third party. That makes sense. Encrypt before sending to a third party?
Re: Fire destroys S. Korean government's cloud storage system, no backups available
#574> However, due to the system’s large-capacity, low-performance storage structure, no external backups were maintained — meaning all data has been permanently lost. Yikes. You'd think they would at least have one redundant copy of it all. > erasing work files saved individually by some 750,000 civil servants > 30 gigabytes of storage per person That's 22,500 terabytes, about 50 Backblaze storage pods. Or even just mir…
It's even worse. According to other articles [1], the total data of "G drive" was 858 TB. It's almost farcical to calculate, but AWS S3 has pricing of about $0.023/GB/month, which means the South Korean government could have reliable multi-storage backup of the whole data at about $20k/month. Or about $900/month if they opted for "Glacier deep archive" tier ($0.00099/GB/month). They did have backup of the data ... in…
Re: Fire destroys S. Korean government's cloud storage system, no backups available
#575Earlier quoted context omitted.
Ironically many of those documents for procedures probably lived on that drive...
You jest, but I once had a client who's IaC provisioning code was - you guessed it - stored on the very infrastructure which got destroyed.
From what I have seen a lot of time the playbooks to fix these issues are just rawdogging files using rsync manually. Ideally you deploy your infrastructure in cells where rollouts proceed cell by cell so you can catch issues sooner and also implement failover to bootstrap broken cells (in my DNS example, client could talk to DNS servers in the closest non-broken cell using BGP based routing). It is hard to test, and there are some global services (like that big Google outage a few months ago was due to the global auth service being down).
Re: Fire destroys S. Korean government's cloud storage system, no backups available
#576> However, due to the system’s large-capacity, low-performance storage structure, no external backups were maintained — meaning all data has been permanently lost. Yikes. You'd think they would at least have one redundant copy of it all. > erasing work files saved individually by some 750,000 civil servants > 30 gigabytes of storage per person That's 22,500 terabytes, about 50 Backblaze storage pods. Or even just mir…
You're assuming average worker utilized the full 30G of storage. More likely average was at like 0.3G.
Re: Fire destroys S. Korean government's cloud storage system, no backups available
#577Earlier quoted context omitted.
It is much more likely and cheaper, that US marines will desant and capture your backup facility, than someone would break AES-128.
Sending troops would be an act of war, and definitely not cheap. Stealing some encryption keys, just another Wednesday.
Re: Fire destroys S. Korean government's cloud storage system, no backups available
#578And the cost of everything is PAIN to us.
If our building burned down we would lose data, but only the data we are Ok with losing in a fire.
I'd love to know the real reason. It's not some useless tech... it's politics, surely.
Re: Fire destroys S. Korean government's cloud storage system, no backups available
#579Re: Fire destroys S. Korean government's cloud storage system, no backups available
#580Earlier quoted context omitted.
Having just visited South Korea last year, one thing that sort of caught me off guard was the lack of Google Maps or other major direction system. I wasn’t aware but turns out anything considered “detailed mapping” infrastructure has to be ran stored and on South Korean soil, probably lots of other requirements. So you’re stuck with some shotty local mapping systems that are just bad. There may be a point in time it…
Why didn't you use Kakao Maps or Naver Maps? They're not shotty and work just fine, even if you don't read Korean, you can quickly guess the UI based on the icons.