Hello there.

I am starting to sketch recovery procedures for an ADSM V2 that we will install
here very soon. I would like a few words of advice (especially from the
IBM-ers) on the next topic.

If the platform on which my ADSM server runs suffers from system crash or power
down or ADSM crash, would it be recommended to perform systematically an
auditdb of the ADSM DB, once the platform becomes available again or when my
ADSM is   restarted on an alternate platform, or can I count on the fact that
ADSM has enough build-in fail-safe mechanism that the DB will not be corrupted
in such a situation?

If my DB becomes corrupted, how/when will I realise that such an event has
occured?

If performing an auditdb is "normally" not required after such an incident, how
can I know whether or not to do it?

The reason of these questions is that we are planning to create a rather big
ADSM configuration here, and that we suspect that the auditdb would be
extremelly costly to run in such an environment.

Thanks for any help.


BTW, is there a FAQ for this group? if yes, where can I find it?

--
Regards
Regards

!!!!!!!  >>>>>>  ECMWF has a new internet address: ecmwf.int   <<<<<<  !!!!!!!

+-------------------+----------------------------------+---------------------+
| Francis Dequenne  | Systems Section                  |      /~~\  /~~\     |
| ECMWF             | e-mail: fdequenne AT ecmwf DOT int      |     /    \/    
\    |
| Shinfield Park    | Tel:    (+44 1734) 499361        |   ECMWF             |
| Reading           | Fax:    (+44 1734) 869450        |   ECMWF             |
| Berkshire RG2 9AX | Telex:  (+44 1734) 847908        |     \    /\    /    |
| United Kingdom    |                                  |      \__/  \__/     |
+-------------------+----------------------------------+---------------------+