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.

Dealing with corrupt Exchange information stores

Here is Microsoft’s official process of dealing with corrupt information stores:
http://technet.microsoft.com/en-us/library/aa996027.aspx

Often, you can just run an eseutil a couple times on the private information store (but you must make sure that there is at least 20 GB free on the partition you’re running the eseutil on). Here is what you normally run in what order:

Eseutil /r e00 /i

Eseutil /p “d:\exchsrvr\mdbdata\priv1.edb”

Eseutil /d “d:\exchsrvr\mdbdata\priv1.edb”

isinteg –fix