Folks,

One of our customers reports the following.  Any ideas as to what might be
happening?

TIA.

This is what has happened so far.  The data bases for Exs1, Exs2 have been
restored to our test server.  Only the information store is being restored.
After the restore is complete we go into exchange administrator and run the
DS/IS consistency adjustment this rebuilds the directory structure for
exchange.  After this the ESEUTIL is run against the data base and it
reports the 1206 errors.  According to Microsoft 1206 errors are bad to
have.  The ESEUTIL only reports errors it doesn't fix then the utility that
fixes then causes data loss too. It hasn't been run against the data bases.
I talked to my exchange people this morning and he said that as far as he
can tell so far the data base seems ok he can open exchange and see all the
mail boxes and retrieve data even with out repairing the data base.  He is
just concerned that if we had to do a complete rebuild of one of the servers
that it wouldn't work.

Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80949
719-531-5926
www.storsol.com
lipp AT storsol DOT com

Additional information that was not understandable to me!


Off-line copies of priv.edb (as well as pub.edb and dir.edb) on EXS1 and
EXS2 took less than 30 minutes to make.  Making copies of the EXWEB
databases took only about three minutes.  Runs of ESEUTIL /G on priv.edb on
each server with all Exchange services stopped took about 10 minutes (much
less on EXWEB) and showed no errors at all.  And ESEUTIL /MH runs on the
priv.edb files all reported consistent states.  This is in contrast to
similar runs of the ESEUTIL program on ADSM restored copies the priv.edb
files on RAT last week which showed -1206 errors in each of the databases.
Most of those runs were done with only the Information Store service
stopped, but one ESEUTIL /G on EXS1 data late Thursday showed -1206 errors
even with all Exchange services stopped.
The off-line copies of priv.edb on EX1, EX2, and EX3 took much longer, about
an hour and a half for EX1 and about two hours for EX2 and EX3.  The
progress "thermometers" on EX2 and EX3 filled up and restarted two or three
times, with very bizarre "minutes remaining" indications-often reporting
more than 10,000 minutes left.  Runs of  ESEUTIL /MH on the priv.edb files
showed them all in consistent states.  Runs of ESEUTIL /G will have to be
done on copies transferred to RAT later.
********************************