asked on

Best practices for ESEUTIL and ISINTEG utilities

Hello Experts,

I have an Exchange 2003 server that has numerous errors and that is heavily fragmented. I am planning on performing an offline defrag as well as a repair using the ISINTEG utility. My question is this...is it better to defrag before you repair, or should you repair before you defrag?

Please advise.

Thanks, Barron

ASKER CERTIFIED SOLUTION

mass2612

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Sembee

Exchange databases don't get "heavily fragmented" in the same way that file systems do. If the database is corrupt then you may be better of moving everything to a new or temporary database so that the server can be rebuilt.

Simon.

Barron Fraker

ASKER

Let me offer some clarification.

1) The Event log is reporting a huge amount of white space, to the tune of 19GB on a store that is only 35GB in total size.

2) The additional errors that are showing up in the Event Log are being reported by Backup Exec. It says that "database element is missing or corrupt."

3) I'[ve attached an ESE error in the Event Viewer reported by Exchange. Seems that the only file generating the error is the priv1.stm file. Priv1.edb and the two Public Store files report no errors.

4) So...in light of all this, and to speak more generally, would you run eseutil before isinteg, or vice versa?

Thanks,

Barron

Event Type:	Error
Event Source:	ESE
Event Category:	Logging/Recovery 
Event ID:	478
Date:		11/30/2007
Time:		6:58:55 AM
User:		N/A
Computer:	SERVER
Description:
Information Store (892) The streaming page read from the file "D:\Exchsrvr\mdbdata\priv1.stm" at offset 5171400704 (0x00000001343d5000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch.  The expected checksum was 3471743127 (0x00000000ceee9897) and the actual checksum was 3163017662 (0x00000000bc87d1be).  The read operation will fail with error -613 (0xfffffd9b).  If this condition persists then please restore the database from a previous backup. 
 
For more information, click http://www.microsoft.com/contentredirect.asp.

Open in new window

mass2612

Sorry for the delay. in this situation I would consider running eseutil to reclaim the space. Before doing so I would suggest using NTBackup to backup the Exchange info store and see if you recieve any errors from that.

When you defrag the EDB it should also defrag the STM file so this may fix the STM problem.

Barron Fraker

ASKER

Great, I will try that MASS. Will let you know how it goes.