Exchange database snapshot consistency fails after Info Store service hung

We recently installed Window Server 2008/Exchange Server 2007 onto a new server.
(I am still learning how to use the new software version)

I had to restart the information store service, but it got stuck stopping.  I was able to start it again and have since beeen able to restart the service successfully.

Since then, however, our backups (Backup Exec v12.5) are failing with the following:
e000032c - The consistency check of the snapshot for the Microsoft Exchange database has failed. You should check for possible data corruption in the Exchange Server that is online.

I have not yet run Eseutil and Isinteg as suggested on the Symantec website, as I will need assistance from our IT consultant to do so.
I wondered if there was anything else I can try in the meantime which is less drastic.
Our email is functioning normally.  So far.

Any help would be appreciated.  Thank you.
Who is Participating?
sarahb1973Connect With a Mentor Author Commented:
The problem appears to have fixed itself as our backups are running normally, for now.  I cannot find any entries in the Event Viewer to explain why it has resolved itself.  However, thanks to everyone for their help.  It is much appreciated.
Stewart BeelSenior Technical AnalystCommented:
Hi Sarah,

Probably not what you want to hear, but ISINTEG is more than likely the fix for this problem.

You may need to run it more than once to fix any corruption in the database.
Shreedhar EtteCommented:

What is the Service Pack and Rollup level of the Exchange 2007?

If it is not the Exchange 2007 Service Pack 2 and Updated Rollup 2 for Exchange 2007 SP2. Then apply the updates and then check the backups.

I hope this helps,
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

It is highly recommended run ESEUTIL /r
I will agree with Sreedhar, that you should have the latest service packs and Updates.

If you dont have large number of users in the database, and you dont want to get into the hassels of running ESEUTIL, I did suggest to create a new database, and move all the users to the new database. Drop the old database after you move all users successfully. Pretty easy and hardly any downtime.
32-bit OS can operate only 4Gb RAM. And one separate process can use 3Gb maximum (PAE mode).
64-bit OS can operate 2Tb memory.

If your hardware has 4Gb RAM or more use 64-bit OS.

MS SQL try take memory as it need, but can't break OS limits.
sarahb1973Author Commented:
Hello.  Thank you all for the suggestions so far.  Sorry,  I should've checked the update status before posting.  The server has downloaded ServicePack2, but we will have to delay the install until after Easter.  As suggested, we will see what happens with the backup after that and I will update this posting accordingly.
Thank you.
Try the following symantec article if SP2 installation doesn't fix the issue :-

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.