Sunday, February 22, 2009

ESEUTIL AND ISINTEG

ESEUTIL 

It is a life saver tool in maintainng the exchange database ie. , tool that manipulates Exchange's Extensible Storage Engine. This tool is similar to ntdsutil in term it manipulates with the Active directory.

/d - Performs off-line defragmentation/compaction of a database.
/r - soft recovery, bringing all databases to a consistent state or clean shutdown state.
/g - Verifies integrity of a database.It just fix the database tables but not the relation and others database stuff.That 
can be rectified by using the isinteg tool.
/m - Generates formatted output of various database file types. It is used to take the file dump.
/p - Repairs a corrupted or damaged database.
/y - Copies a database, streaming file, or log file.
/cc - Performs a hard recovery after a database restore.It is used to replay the logs after restoring from the backups.
/mh - to check the status/state of the mailbox store. To determine whether the last shutdown was clean or dirty. 
/mk - to check the last committed transastion log file into the database.
/ml - similar to /mh, except this switch performs an integrity check on log files.
/mm - Dumps metadata from the database file.

ISINTEG 

It is used to do some tests on your information store and to fix some detected errors and problems.ISINTEG is the only repair for exchange database engine. ESE is a generic database engine that can be used by different applications (Exchange, ActiveDirectory).
ESEUTIL looks into the database as just another ESE database, and can see their tables and indexes. ESEUTIL just fixes the database tables.Now it is time for ISINTEG. ISINTEG is aware of the relation between database tables and records that turn them into folders and messages.

Isinteg -fix -test alltests

In case of damaged database, the below is the idle steps...

1. Run Eseutil /P.
2. After Eseutil /P completes successfully, run Eseutil /D.
3. After Eseutil /D completes successfully, run Isinteg –fix –test alltests.

Thanks
Logan
91-9841499143

No comments: