Regarding the ADSM for NT client installation, we've seen this problem and,
while we don't know exactly what situations(s) cause it, we've generally
been able to avoid it by doing the following:

(1 Scanning the c:\winnt directory for a copy of "uninst.exe" and renaming
   it, if found, prior to invoking ADSM's \DISK1\SETUP program; I think its
   another version created by Netfinity (another IBM product) but I'm not
   sure.

(2 If Lotus Notes Domino is running, stop it before invoking \DISK1\SETUP

Dennis Schaffer
Mutual of Omaha






lipp AT STORSOL DOT COM on 01/16/98 10:06:05 AM

Please respond to ADSM-L AT VM.MARIST DOT EDU

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Dennis Schaffer)
Subject:  Re: NT Server Setup and other Questions




No idea about your NT problem.  I've seen this myself, but never resolved
it.
The best way to build off-site volumes is by using a copy storage pool
(tape) and the backup stg command.
Yes, you should probably back up ADSM as described in the ADMIN guide.  I
would think it will be easier to recover ADSM using their procedure than
the AS/400 procedure.  I'm not an AS/400 guy though.
On a daily basis you should backup your storage pools, backup your database
and make sure a copy of the volhist.out and devconfig.out files are off of
your server.  You need those two files and a good database backup to
restore and ADSM server.  You need a copy of the client data (backup stg
into a copy storage pool) to finish the restoration job.
Kelly