Keep your local data backup on different geo-location. 🔥 South Korea’s central government just lost 858TB from its internal data after a lithium-ion battery fire. Permanently wiping a shared document store that covered roughly 8 years of work. South Korea’s government built its own private cloud service called G-Drive, meant for internal use by civil servants. It was hosted entirely inside a government data center G-Drive served about 125,000 officials with default 30GB per user and, unlike 95 other systems at the site, it had no backup, so the racks that burned were the single copy. Restoration across government has been gradual, with reports ranging from about 30% to 33.6% of online services back up as of early October. Disruptions touched everyday services such as childcare payments via the National Happiness Card, mail and finance portals, petitions, and parts of emergency response, because many dependencies sat in the same facility. The fire started on from a battery event during power work, spread across hundreds of packs, and took roughly 22 hours to fully extinguish. This is a classic single-site risk, because core storage and recovery lived on the same campus without off-site redundancy or immutable copies. A safer pattern is 3-2-1 backups, meaning 3 copies on 2 different storage types with 1 off-site, plus tested restores and geo-separated replicas for both file stores and metadata. --- pcgamer .com/hardware/data-center-fire-in-south-korea-sees-858-tb-of-government-agency-files-and-eight-years-worth-of-work-stored-in-the-cloud-go-up-in-smoke/

whats happening here? 🤔