Monday, October 4, 2010

Windows Server Backup - Exchange backup fails at consistency check

I have a single server setup where the server runs Windows Server 2008 R2 and Exchange 2010. The backup kept completing with warnings saying that the consistency check failed for Exchange.

EDIT - the steps from my original post below also work. But a much easier solution is to enable circular logging on the Exchange database that is failing. Then mount and dismount then Exchange database. All the logs will disappear. Get a good backup and then disable circular logging.

Original post below:

I'd also get event log errors saying that certain log files were missing. There was a point where I had deleted some log files to address space issues. And since the backup wasn't finishing, the log files kept failing to get flushed.

I doubt this is the advisable way to handle this, but this is what I did:

a) delete all log files

b) Backup all edb's.

c) Check shutdown status of your .EDB
eseutil /mh "Full Path to your EDB"

d) eseutil /p "Full Path to your EDB"
/p is hard-repair

e) eseutil /d "Full Path to your EDB"
/d is desfragment

f) isinteg -s servername -fix -test alltests **

** my isinteg would not run, but I was able to mount and run the databases without running isinteg. Not best practice, but it kept giving me references to a log file for isinteg that didn't seem to exist.

After running the eseutil commands, my database mounted and I was able to get a good backup.

1 comment:

Alex said...
This comment has been removed by a blog administrator.