5 ms·
The joys of IT. Back in the day, to wipe years of records you had to burn or shred tons of paper in multiple locations. Now you just crash one little system...
by toyg 10y ago
The joys of IT. Back in the day, to wipe years of records you had to burn or shred tons of paper in multiple locations. Now you just crash one little system... Despite 20 years of Microsoft-induced crashes, clear best practices and yadda yadda, most organizations will still have a single backup system for any given data repository -- if they have one at all.
And the answer when shit happens is "outsource! Go to the cloud!" -- so that local managers won't be responsible when the snafu happens and data is lost (if it happens to Google, it can and will happen to anyone).
Progress, eh.
- Shivetya 10y agoIt never ceases to amaze me how many teams have the idea that DR is simply buy some new hardware. sadly its not just a government failing.
- pslam 10y ago> The joys of IT. Back in the day, to wipe years of records you had to burn or shred tons of paper in multiple locations. Now you just crash one little system. [...] most organizations will still have a single backup system for any given data repository -- if they have one at all. No, back in the day, you could still wipe years of records because most people only used a single filing cabinet with no duplication or off-site copies. "Destroyed in a fire" was the canonical way to destroy all records, easily. This story has nothing to do with the introduction of IT. Incompetence is still incompetence.
- droopyEyelids 10y agoFire? Why be so bombastic. All it takes is one mis-applied label to permanently destroy records in a large enough filing system.
- icebraining 10y agoBernard: Shall I file it? Hacker: Shall you file it? Shred it! Bernard: Shred it? Hacker: No one must ever be able to find it again! Bernard: In that case, Minister, I think it's best I file it. Yes, Minister - The Death List
- chiph 10y ago16-18 million records destroyed in a fire in 1973: http://www.archives.gov/st-louis/military-personnel/fire-1973.html http://www.archives.gov/st-louis/military-personnel/fire-197...
- deleted 10y ago[deleted]
- thaumasiotes 10y agoBack in the day, in 2300 BC, records caught in fires were preserved forever, while records not so lucky eventually returned to the earth. (Barring the odd formal peace treaty inscribed in metal.) We know a lot more about conquered Mesopotamian kingdoms than we do about successful ones, because step one after taking over a city was apparently burning it down, or at least burning down the palace.
- bsurmanski 10y agoI would consider it progress. The only data loss to Google that I was able to find was [0], where a single datacenter was hit by lightning 4 times in short succession, and 0.000001% of disk space in said datacenter was lost. And only because the lost data consisted of recent writes that had yet to be backed up. And only because the lightning affected the AUX power systems in a way that they have since committed to fixing (or perhaps have fixed). IMO, cloud storage is the most reliable way to store data, and Google the most reliable. I never know if I'm going to drop my laptop and lose all work. Or if the harddrive in my server is going to give up and burst into flames. But the great thing about cloud storage is that it abstracts away hardware components and failures so it's somebody else's problem. And they worry a lot more about data loss than I do. Cloud data storage is designed with the assumption that hardware is faulty. Spread redundant copies of data to geographically isolated datacenters, and you're much safer than some admin of averagejoe.com keeping his data on a single harddrive in his closet. [0] - https://status.cloud.google.com/incident/compute/15056#5719570367119360 https://status.cloud.google.com/incident/compute/15056#57195...
- Johnny555 10y agoIMO, cloud storage is the most reliable way to store data, and Google the most reliable Does Google publish any durability numbers? Amazon claims 99.999999999% (11 9's) for S3 and Glacier (and considerably worse for EBS volumes). How does Google compare?
- eru 10y agoDon't have numbers here, but it's pretty good, and we regularly move the data around and check it. (Ie it's not just rotting on a hard disk somewhere.)
- toyg 10y agoThe problem is not just DR, but anything that can result in data loss. There was the one where they'd delete stuff you didn't mean to [1], the one where they got stuff back by the scruff of the neck [2]... i can't be arsed to look further back, but I'm pretty sure shit happened earlier as well (and I'm just looking at GMail). And of course there are tons of horror stories about accounts disabled or deleted for commercial or other unspecified reasons, because once you put your trust in another entity, that's it, they can do as they please. Their track record might be as good as anyone's, but it still has a few holes and people should prepare for it rather than considering "the cloud" as a magic bucket. (disclaimer: my life would probably be ruined by losing the gmail account I've held since private-beta days, because life is short and I'm shit at sysadmin; but there's a big difference between a lone old geek and large organizations...) [1] http://www.dailymail.co.uk/sciencetech/article-2548010/Has-Gmail-lost-YOUR-emails-Glitch-causes-thousands-users-accidentally-delete-messages-report-spam.html http://www.dailymail.co.uk/sciencetech/article-2548010/Has-G... [2] http://www.datacenterknowledge.com/archives/2011/03/01/google-turns-to-tape-to-rescue-lost-gmail/ http://www.datacenterknowledge.com/archives/2011/03/01/googl...