Cloud Recovery

Thoughts and Topics Around Cloud Backup and Recovery

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 4 other followers

  • Subscribe

  • RSS Cloud Security

    • GoGrid Security Breach
      Bad news for GoGrid customers as today we received the following breach notification by email… Dear Valued Customer: In the normal process of reviewing our system activity, our Security Team discovered that an unauthorized third party may have viewed your account information, including payment card data. We immediately took action to protect our custom […]
  • RSS Cloud Computing Journal

    • Who's Managing Your PaaS Apps?
      PaaS v2.0 should be more open than the current implementations, and cultivate tools communities. But the focus on open development stacks is ignoring the second aspect of PaaS - the management of live applications after they are built. PaaS providers need to allow for communication of SLA and business process requirements by consumers, and cloud management t […]

Lessons Learned from Amazon EC2 outage

Posted by brennels on January 13, 2010

OK I’m back from the holidays and just recently presented a webinar on how to protect entire virtual infrastructure in the cloud and the risks of having your entire datacenter residing on a few virtual servers. Unlike the old days if a server went down the only impact was what ever the application that was running on that server. Now with consolidated virtualized infrastructure if a physical server goes down there could be a dozen virtual machines go offline simultaneously. I believe Amazon still met the SLA but this article should serve as good information for anyone looking to implement a 100% virtualized environement without some sort of loal failover capabilities.

Carl Brooks, Technology Writer | SearchCloudComputing.com wrote a great article on the latest outage impact from an Amazon customer ”Heroku learns the hard way from Amazon EC2 outage
 

Ruby on Rails Platform as a Service startup Heroku started off the new year with a nasty surprise. Without warning on January 2, all of the specialized, high-capacity Amazon EC2 instances that run its popular application and development service disappeared in the blink of an eye. Twenty-two virtual machines, approximately $20,000 per month in hosting fees for high-memory m2.2xlarge instances, suddenly vanished, leaving Heroku’s estimated 44,000 running applications in the lurch.

Amazon blamed a routing device in its Virginia data center, and the service was back up in an hour. But Oren Teich, Heroku’s product developer, said this is one of the many important lessons new ventures and businesses need to learn before they decide to work entirely in the cloud. Traditional contingency planning doesn’t go far enough, he said: expect the unexpected.

Read the full article here on SearchCloudComputing.com

Advertisement

One Response to “Lessons Learned from Amazon EC2 outage”

  1. Lessons Learned from Amazon EC2 outage…

    OK I’m back from the holidays and just recently presented a webinar on how to protect entire virtual infrastructure in the cloud and the risks of having your entire datacenter residing on a few virtual servers. Unlike the old days if a server went down…

Leave a Reply

Fill in your details below or click an icon to log in:

Gravatar
WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Connecting to %s

 
Follow

Get every new post delivered to your Inbox.