OK, you are running in a clustered environment... that is a clue (this is
why it is usually important to specify your particular environment).

Do you have multiple options files configured, one for cluster resources,
and another for non-clustered (local) disks? If so, are you also using
distinct node names for each? You can not use the same node name to back
up cluster resources as you use for local disks. The TSM client password
encryption uses the local machine name to encrypt the password for the
node that backs up the machine's local disks, while the cluster name is
used to encrypt the password for the node that backs up the cluster
resources. Thus if you use the client to back up local disks, then try to
use the same node name to back up cluster resources, the passwords won't
match.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Weeks, Debbie" <debbie AT ADMIN.USF DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/21/2002 09:22
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: W2000 client passwords



Using this command appeared to start the service, but it never prompted
for
a password for the node.  Of course, it is using the wrong options file,
but
I had the cluster node specified in the default opt file anyway.  The
regular service for this node still won't start though.