Wired reports: The failure appears to be catastrophic. The company can't say to what extent it will be able to restore any of its users' data. It also says the data failure was so extensive, repairing the loss will take "days, not hours."
You've got to wonder how they screwed up this badly. Why didn't they have a delayed replica of their database to fall back on so they only lost an hour of data, for example? It should be noted that I managed to run rm -r in /var/db/mysql earlier this week so maybe I can't talk – but then my system only had five users. And I was back up in 9 hours (gotta love those frantic 2am recovery sessions!)
This entry was posted
on Friday, January 30th, 2009 at 6:42 pm and is filed under Comment.
You can follow any responses to this entry through the RSS 2.0 feed.
You can skip to the end and leave a response. Pinging is currently not allowed.
Ma.gnolia Suffers Major Data Loss
Wired reports: The failure appears to be catastrophic. The company can't say to what extent it will be able to restore any of its users' data. It also says the data failure was so extensive, repairing the loss will take "days, not hours."
You've got to wonder how they screwed up this badly. Why didn't they have a delayed replica of their database to fall back on so they only lost an hour of data, for example? It should be noted that I managed to run rm -r in /var/db/mysql earlier this week so maybe I can't talk – but then my system only had five users. And I was back up in 9 hours (gotta love those frantic 2am recovery sessions!)
Tags: Blog, Data Loss, Extent, Failure, Magnolia, Sessions
This entry was posted on Friday, January 30th, 2009 at 6:42 pm and is filed under Comment. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.