sarahb1973
asked on
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.
Sarah
(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.
Sarah
Hi,
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,
Shree
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,
Shree
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.
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.
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.
ASKER
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.
Thank you.
Hi,
Try the following symantec article if SP2 installation doesn't fix the issue :-
http://support.veritas.com/docs/292925
http://support.veritas.com/docs/337917
Thanks,
Try the following symantec article if SP2 installation doesn't fix the issue :-
http://support.veritas.com/docs/292925
http://support.veritas.com/docs/337917
Thanks,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Probably not what you want to hear, but ISINTEG is more than likely the fix for this problem.
http://www.msexchange.org/tutorials/Exchange-ISINTEG-ESEUTIL.html
You may need to run it more than once to fix any corruption in the database.