I've had this happen in a Windows 2000 cluster and TSM clients 5.1.7.1.
and TSM server 5.3.2.1 on AIX

It happens fairly consistently after moving a cluster group (containing
disks and TSM scheduler for the cluster group) from one node to another.
 The solution for me has been to restart the TSM Scheduler service on
the cluster node (which only backs up the local disks) AFTER moving a
cluster group.

It seems that the scheduler for local node/disks somehow picks up the
disks belonging to the cluster group when the failover occurs.
Restarting the scheduler resets it back to just the local disks.

In my case, it's just another step to perform when doing cluster
maintenance/management.  Can be a bit of a pain, though when the node
starts backing up hundreds of gigs of data unnecessarily.





Tim Brown wrote:

Have Windows 2003 Server cluster with 2 nodes
PServer1  PServer2, Cluster is call PCLUSTER

The TSM clients on PServer1 and PServer2 backup their
respective c: drives and system information.

The TSM Cluster service for noe PCLUSTER backs up drives  q: d:

Occassionally one of these two TSM Nodes will backup the cluster
which I dont want to happen

The DSM.OPT on these 2 servers has this coded

Domain ALL-LOCAL -d: -q:

Tim Brown
Systems Specialist
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Email: tbrown AT cenhud DOT com
Phone: 845-486-5643
Fax: 845-486-5921

--
Graham Stewart
Network and Storage Services Manager, Information Technology Services
University of Toronto Library
130 St. George Street
Toronto, Ontario                graham.stewart AT utoronto DOT ca
Canada   M5S 1A5                Phone: 416-978-6337 | Fax: 416-978-1668