Our internal mail team runs the utility to validate the integrity of the
database.
Is it necessary??? They seem to think so.

C

__________________________________________________
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

        -----Original Message-----
        From:   Remeta, Mark [SMTP:MRemeta AT SELIGMANDATA DOT COM]
        Sent:   Wednesday, September 22, 1999 2:02 PM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Re: Important Exchange restore procedure
information!

        Cris,

        why do you run the eseutil after you restore the database?
        Is this necessary???

        Thanks,
        Mark

        -----Original Message-----
        From: Robinson, Cris [mailto:Cris.Robinson AT LIBERTYMUTUAL DOT COM]
        Sent: Wednesday, September 22, 1999 1:41 PM
        To: ADSM-L AT VM.MARIST DOT EDU
        Subject: Important Exchange restore procedure information!


        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