The way I have set this up is to use the CLUSTER name in TSM for the shared 
storage, and the two local computer names for the local drives.
 
nodename
Cluster       - controls the F,G,H,I,J drives (CLUSTERNODE YES option)
Server1      - controls c and d drive (Domain C, Domain D...)
Server2      - controls c and d drive (Domain C, Domain D...)
 
I have 2 schedules on each node - one for local backps and one for cluster 
backups. I created a group in the cluster admin to control backups service for 
the shared drives and keep the local node backups to automatic
 
Joe 

        -----Original Message----- 
        From: Zlatko Krastev [mailto:acit AT ATTGLOBAL DOT NET] 
        Sent: Fri 24/05/2002 4:55 PM 
        To: ADSM-L AT VM.MARIST DOT EDU 
        Cc: 
        Subject: Re: NT Cluster & TSM
        
        

        The only explanation is that server1 somehow is getting DOMAIN 
ALL-LOCAL.
        Check carefully which dsm.opt is used when cluster instance goes to
        server1 and are there any DOMAIN options in a optionset associated to 
that
        node.
        If domain all-local gets somehow into "local" node then is have two
        current copies of shared files. But if cluster resources are backed up 
as
        "server1" instead of "cluster" the only way to distinguish which version
        is the current is checking the date or very-very carefully follow
        failovers.
        
        Zlatko Krastev
        IT Consultant
        
        
        
        
        Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT 
EDU>
        Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        
        Subject:        NT Cluster & TSM
        
        Hello,
        I'd like to ask a question about NT cluster with TSM..
        I have got an NT Cluster and the backup is made with TSM. On the TSM
        server
        side I've got defined 2 server, each one for each real server: server1 
and
        server2. There are another two server defined for shared disks: 
disk1(disk
        f:) and disk2 (disk g:).
        There are four file spaces:
        FileSpace Name  Node Name
        \\server1\c$            server1
        \\server2\c$            server2
        \\cluster\f$            disk1
        \\cluster\g$            disk2
        The DOMAIN option in the opt files are
        Server1         DOMAIN C:
        Server2         DOMAIN C:
        disk1           DOMAIN F:
        disk2           DOMAIN G:
        From the backup point of view it works fine, the problem arises when the
        shared disks are moved from one real server to the other.
        In this situation the shared disks are considered as local disks for the
        real servers and a full backup of those disks are made, and the file
        spaces
        are as follows
        FileSpace Name  Node Name
        \\server1\c$            server1
        \\server1\f$            server1
        \\server1\g$            server1
        \\server2\c$            server2
        \\cluster\f$            disk1
        \\cluster\g$            disk2
        
        The creation of the two new file spaces is normal? Is this situation ok?
        
        Another problem arises when there is a need of restoring a file: where 
is
        the backup of one file residing in disk f:? in \\server1\f$ or in
        \\cluster\f$ or in both? Which one is the most recent? and other than 
the
        last one?
        
        Can anyone help me in clarifing those questions?
        
        Angel Antsn
        E-Mail : aantonh AT gipuzkoa DOT net