Kelly,
I assume when the customer says ADSM restores, he is using the
ADSMConnect Agent for Microsoft Exchange:
Two VERY important things when doing such a restore:
1. Make sure you use the "ERASEEXISTING" option on the restore.
The command line client has an option, the GUI has a radio button.
This removes pre-existing transaction logs that confuse
the Exchange server on the transaction log replay after
the restore.
2. After running the restore and BEFORE running ESEUTIL,
you MUST restart the Directory and Information Store services.
It also doesn't hurt to recycle the System Attendant.
The Exchange Server MUST replay the transaction logs before
a valid consistency check can be done.
THIS IS DIFFERENT than an "Offline" restore procedure.
Also, you should NOT run ISINTEG -patch after doing an
online restore.
Thanks,
Del
----------------------------------------------------
Del Hoobler
Del Hoobler
IBM ADSM Agent Development
hoobler AT us.ibm DOT com
> 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
|
