How One Drunk Driver Sent My Company To the Cloud 290
snydeq writes "Andrew Oliver offers further proof that drunk driving and on-site servers don't mix. Oliver, who had earlier announced a New Year's resolution to go all-in on cloud services, had that business strategy expedited when a drunk driver, fleeing a hit-and-run, drove his SUV directly into the beauty shop next door to his company's main offices. 'Our servers were down for eight hours, and various services were intermittent for at least 12 hours. Had things been worse, we could have lost everything. Like our customers, we needed HA and DR. Moreover, we thought, maybe our critical services like email, our website, and Jira should be in a real data center. This made going all-cloud a top priority for us rather than "when we get to it."' Oliver writes, detailing his company's resultant hurry-up migration plan to 100 percent cloud services."
Re:Oh the irony! does nobody remember (Score:5, Interesting)
I was thinking the same thing. I keenly remember Microsoft Azure going down for eight hours [theregister.co.uk], right after we migrated to their cloud service. With our old datacenter, we were alerted immediately and their tech support had a bang list to alert all our customers for us that the system was down. With Microsoft, we got NOTHING. Our customers alerted us to the fact that they couldn't access their applications, and we had to go to twitter to @WindowsAzure to ask when the servers would be back up. Then, a year later, the East Coast datacenter went down and we learned that Cloud service does not include disaster recovery [microsoft.com] and we were responsible for setting up our own recovery solution on Window's Azure's servers.
Re:For all the drunks out there! (Score:4, Interesting)