Here's the contents of a note on the list a while back.  Thanks to Joe
Schilling from whom I stole this!

------
If anyone is interested, we had a problem with running the ADSM backup on
If anyone is interested, we had a problem with running the ADSM backup on
our cluster server.  Our two physical servers backed up fine, but when we
would try to backup the clustered drive, we ran into problems relating to a
password error of ANR0444W, also when we would fail over from one server to
the other, the Schedule Service for the Cluster would be deleted from both
of the physical servers in the cluster.

What we found was that there is a variable in the NT environment that sets
the following:

     DSMG_DIR=c:\winnt\system32

This variable is looking for the following file:  dscameng.txt


Unfortuneatly the file does not exist in C:\winnt\system32, but does exist
in the baclient directory of ADSM.

The installation of ADSM ver 3.1.0.7 sets this variable automatically, to
resolve our problem, we changed the variable to point to the location of
the file:

     DSMG_DIR=c:\program files\IBM\adsm\baclient

you could just copy the file to c:\winnt\system32 as well.

Once this variable was set, all of our problems went away.

Hope this will help anyone having problems with the NT Clustering.

------
End my pilfering!
End my pilfering!

Thanks,

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