As some of you may be aware we were having some issues related to Exchange
restores. The problem we experienced proved to be a procedural problem.
Here is the error we saw:

Eseutil returned '-1206 JET_errDatabaseCorrupted non-db file or corrupted
db'
The old procedure we were using had the eseutil run immediately following
the restore. We revised our procedure, see below, to avoid the error:

*       Restore the Exchange Directory and IS
*       When the restore is completed start all Exchange services.  Once
services have started, the server will join the production site and begin
replicating with other servers.
*       Stop the Microsoft Exchange Information Store service.
*       Open a command prompt, and change directory to c:\exchsrvr\bin.
*       From the command prompt, run ISINTEG -PATCH.
*       Stop the Microsoft Exchange Directory service.
*       From the command prompt, run ESEUTIL /g /ds (which should show no
errors.)
*       Run ESEUTIL /g /ispub (which should show no errors.)
*       Run ESEUTIL /g /ispriv (which should show no errors.)
*       Start all Exchange services.
*       Check the Event Viewer for any problems.
*       Using the Server Install Checklist, perform all the steps for 'Post
Install' except for installing ADSM (which is already done).

This solved our issues with the restore of our Exchange Server.
Special thanks to Del Hoobler who helped us see the forest through the
trees! We really appreciate it!

CR

__________________________________________________
Cris Robinson
Sr. Technical Analyst
Enterprise Storage Management / ADSM
Liberty Mutual Insurance
Portsmouth, New Hampshire
603.431.8400.54837
mailto:cris.robinson AT libertymutual DOT com