Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We've been running a large RDS instance in production for over year without a single moment of downtime. Recently, with a bigger budget and higher stakes, we decided to convert it to a multi-AZ instance, to improve reliability and redundancy of our data.

Since then (about two weeks ago), we've had two serious failures of our instance which required rebooting. There is nothing in the 'recent DB events'. There were two DB connection spikes recorded in cloudwatch that occurred at the same time as the failures.

What's going on?

share|improve this question
Have you tried opening up a ticket with Amazon? A lot more detail will be necessary to figure out what is going on. – Aaron Aug 19 '11 at 21:30
up vote 1 down vote accepted

It appears that the problems were related to AWS and not to the instance. When this was posted, it turned out to be one of the most serious outages of AWS europe so far.

There are a number of problems with RDS Multi-AZ that mean that it is still possible for automatic failover to not occur, leaving you without a server. Implementers should be aware and build sufficient redundancy into their applications that can mitigate problems in multiple availability zones.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.