The cluster node in question had to 'own' the volume at the time that you
installed the service on that node. You may move the volume later, but the
service only recognizes volumes that were there when it was installed.  This
could be your problem.

Glen Churchfield
============================================================================
==============================
This message may contain confidential, proprietary, or legally privileged
information.  You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message. The views or opinions
expressed in this message are solely those of the individual sender, except
(1) where the message states such views or opinions are on behalf of a
particular entity;  and (2) the sender is authorized by the entity to give
such views or opinions.
============================================================================
==============================
----- Original Message -----
From: "Mahesh Tailor" <MTailor AT CARILION DOT COM>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Thursday, September 04, 2003 2:33 PM
Subject: Re: TSM AND WINDOWS 2000 CLUSTER ISSUE


Just to add to Laura's email:

TSM Server is 5.1.6.4 on AIX 4.3.3.10.
TSM Client code is 5.1.5.9

Just to reiterate, other nodes in the cluster are working fine.

Thanks.

Mahesh

>>> lbooth AT CARILION DOT COM 09/04/03 01:20PM >>>
I have a Windows 2000 SP4 Server and have configured TSM 5.1  for several
cluster nodes.  I have one node that will not recognize one of the physical
drives that is configured within that group.  I have edited the opt file,
reconfigured TSM on the local machine, removed and reinstalled the services
for the cluster node, and removed and recreated the node itself...I have
rights to the drive and don't have an issue accessing the drive. Has anyone
had a similar issue or have a resolution for this problem?

Thanks,
Laura Booth