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: