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

Some of our Exchange databases regularly end up with a status of FailedAndSuspended. I think this is probably because the databases were set up with Circular Logging and the backup copy of the database misses some transactions from the circular log.

Once a database is in the FailedAndSuspended state with a circular log, is there any way to resume replication or do I have to reseed from scratch?

share|improve this question
up vote 1 down vote accepted

per microsoft's documentation, once you go past the end of the circular log, the only way to recover is to restore the database from a backup and replay the backed up log. but this only works if your backup of the database and log plus the current log contain all of the transactions up to the current point with no gaps.

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.