Thanx for the help.  After some more testing, it
appears that the problem is in the GUI.
When I did a show options, the proper domains were
listed.
The client command-line backups up the proper domains
when tested.
So, it appears that the GUI and the ESS have issues.
Scheduled backups work fine as well...
We will avoid using the GUI for manual backups.

Thanx!

--- James Thompson <mezron AT HOTMAIL DOT COM> wrote:
> From the client command line provide the output of
> From the client command line provide the output of
> 'show options'  it should
> show the domain
> that the client is using.
> Also note that the domain statement is additive
> unlike the include/exclude
> statements.
> So the lines
> domain all-local
> domain h: i:
>
> Is equivalent to
> domain all-local h: i:
>
> James Thompson
>
>
> ----- Original Message -----
> From: "TSM Mail-ID" <tsmmail2000 AT YAHOO DOT CA>
> To: <ADSM-L AT VM.MARIST DOT EDU>
> Sent: Friday, January 26, 2001 5:42 PM
> Subject: Domain option not effective in TSM cluster
> environment
>
>
> > We're running TSM Server 3.7.2 and Client of
> 3.7.x.
> > We've installed 2 small NT 4.0 MSCS cluster
> servers
> > with shared disks (just external RAIDs).
> Installed
> > b/a client and scheduler services with no problem
> and
> > fail-over works.
> >
> > We just installed a big NT 4.0 MSCS server, with
> the
> > shared disks being part of an ESS (IBM Shark
> system).
> > When I install the b/a client on the local nodes
> to
> > back up the local disks, everything is fine.  When
> I
> > configure the b/a client for the virtual nodes, it
> > installs fine.  But, when I edit the dsm.opt file
> to
> > limit the backup to the nodes shared disks only,
> it
> > appears to ignore the DOMAIN line and includes ALL
> the
> > shared disks:
> >
> > NODENAME HYDROGEN
> > CLUSTERNODE YES
> > DOMAIN H: I:
> >
> > Instead of limiting the backup to H: and I:, it
> > includes all shared disks that it knows about,
> such as
> > J: K: R:, etc.
> >
> > In the two small MSCS clusters, TSM is working
> fine
> > with the above.  In the big one, it isn't.  All
> > software is the same version, including OS.  The
> only
> > difference is the that we're using an ESS for the
> big
> > one, so the sub-system drivers may be causing a
> > problem.
> >
> > Has anyone run into this problem?  If so how do we
> fix
> > it?
> >
> > I have tried everything in the DOMAIN statement,
> eg.
> > DOMAIN \\CLUS2\H$; DOMAIN "H:", etc.  Nothing
> appears
> > to work.
> >
> > I've gotten around it, but it's ugly. I put an
> > exclude/exclude.dir of the rest of the shared
> drives
> > in each node's dsm.opt file.  Very annoying since
> I
> > shouldn't have to do this...
> >
> > Any help is appreciated...
> >
> > Thanx in advance!
> >
> >
> >
>
_______________________________________________________
> > Do You Yahoo!?
> > Get your free @yahoo.ca address at
> http://mail.yahoo.ca
> >


_______________________________________________________
Do You Yahoo!?
Get your free @yahoo.ca address at http://mail.yahoo.ca