Windows Server Backup reports failed consistency for Exchange 2010 databases
Posted on 2013-12-22
Merry Christmas everybody!
I have a weird problem. I am running Windows Server Backup and it is reporting "The consistency check failed for the component 807d7b28-2c65-4dec-ab19-6fb04d845
263 (Microsoft Exchange Server\Microsoft Information Store\LCA-SERVER1\807d7b28-
2c65-4dec-ab19-6fb04d845263).". Now that all sounds like an easy one to sort out, doesn't it?
Here's the problem: Eseutil reports no problems. None at all. Not on that database, not any of the others on that server. And if I move all the mailboxes into a new database, the error stays with that database, but if I delete it, the error just comes up with another GUID number, so I am assuming the problem is either in each and every database or it is a false positive problem with whatever Windows Server Backup uses to check the consistency.
The only hint I have of any problems with Exchange is that sometimes after a reboot I have to manually start the Information Store, and if I run ISINTEG, the Information Store service crashes, but that might just be because it is being phased out. if I run New-PublicFolderDatabaseRepairRequest, it completes successfully (the error above is the Public Folder store), but the backup still fails using it as the excuse.