Neil,

 

The CLUSTERDISKSONLY statement worked, allowed me to use CLUSTERNODE YES
and see all the mountpoints.  Oddly enough, and contrary to the user
guide, I didn't have to add domain statements in order for it to see and
backup the mountpoints.  Now I'm working on putting the right domain
statements in the cluster and non-cluster client option set in order to
"mask" the volumes I don't want each one to deal with.

 

Thanks for the assist, I hate banging my head against a wall!

 

Steve Schaub

Systems Engineer, Windows

Blue Cross Blue Shield of Tennessee

423-535-6574 (desk)

423-785-7347 (mobile)

 

From: neil.schofield AT yorkshirewater.co DOT uk
[mailto:neil.schofield AT yorkshirewater.co DOT uk] 
Sent: Friday, May 30, 2008 10:07 AM
To: adsm-l AT vm.marist DOT edu
Cc: Schaub, Steve
Subject: Re: [ADSM-L] TSM, MS Clustering & Mountpoints

 


Steve 

How did the testing go? 

This is the domain statement from our DSM.OPT for the shared resources: 

Domain \\WSSClus1\f$ \\WSSClus1\f$\User1 \\WSSClus1\f$\User2
\\WSSClus1\f$\User3 \\WSSClus1\f$\User4 \\WSSClus1\f$\User5 

F: is a shared disk resource and User1, User2, etc are junction points
where the other file systems are mounted. WSSClus1 is the name of the
cluster and the name specified with the /CLUSTERNAME parameter when the
services were installed. 

Regards 
Neil Schofield 
Yorkshire Water Services Ltd. 

Please see the following link for the BlueCross BlueShield of Tennessee E-mail 
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm