Question regarding ESEUTIL

[icsamis]

It has been awhile since I have had to use this command, and that was with Exchange 2003, not 2007. I am just wondering if I can run eseutil /g without taking the store offline? I don't want to actual run it in repair mode at this time.

My backup exec exchange job is saying that there might be corruption in the transaction logs, but when I run the database troubleshooter in the EMC toolbox it says everything is fine. I would like to verify that a problem actually exists before I schedule downtime to take the store offline and repair it. Suggestions? Is it safe and non-disruptive to users to do what I am thinking?

 

[people3]

HI,

Have you tried backing up the information store on a seperate job. (without AOFO)

http://seer.support.veritas.com/docs/285294.htm

 

[icsamis]

Yes. I tried running the job after un-checking the Advanced Open File option and it produced the same error.

 

[icsamis]

Also, my Exchange job has always been it's own separate job so there was no need to change anything in that regard.

 

[people3]

Hi

Microsoft certainly recommend that the store if offline or dismounted to run to run the ESUTIL command with \G

Also make sure you have enough free space.

http://technet.microsoft.com/en-us/library/aa998361(EXCHG.80).aspx

Have you installed any service packs to your exchange recently - Has this just started?

 

[people3]

I'm not convinced that the problem will not be with Backup exec.

This issues was common after exchange 2007 Rollup 4, but i think that was sorted now.

Again the database would need to be taken off line but you could try the

ESEUTIL /ML command

http://technet.microsoft.com/en-us/library/bb125171(EXCHG.80).aspx

 

[icsamis]

Thanks for the feedback, to answer your questions, this only started happening with Monday night's backup. Prior to that I have never observed an error with the Exchange backup but that said, I have also only been with this organization for about a year now.

Last time the server was patched was a few months ago, nothing since. We are on Exchange 2007 Rollup 9, so I too would suspect any issues with Rollup 4 would be resolved by now.

Do you (or anyone else for that matter) have any additional suggestions? Things I could check? I agree, that I am also not entirely convinced that the problem won't end up being with BE but that may just be wishful thinking on my part hehe. In any event, I would really like to say with some certainty where the issue lies before scheduling several hours of downtime to do an integrity check/repair. Thanks for the advice so far, I really do appreciate it!