ADSM-L

Re: TSM Win client DOMAIN statement and unc names

2005-11-18 00:41:20
Subject: Re: TSM Win client DOMAIN statement and unc names
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 17 Nov 2005 22:42:56 -0700
Hi Kyle,

> Now if you think it is a bug then I'd be happy to see things in
> the GUI based on the domain statement. So I could put  -C: to make
> sure the C:\ doesn't show up in the GUI and web client ....

I think that you are attempting to establish a functional relationship,
between DOMAIN and the Backup portion of the GUI interface, that just does
not exist.

It *is* the purpose of the DOMAIN option to establish a *default* list of
file systems to be processed by an *incremental* backup operation.

It is *not* the purpose of DOMAIN to prevent you from backing up files on
file systems that are not part of the domain.

To draw a parallel to the commandline, the scenario you describe is akin
to setting up your DOMAIN option like this:

   domain all-local -d:

and then *disallowing* the following (for example):

   dsmc incremental d:
or
   dsmc selective d:\mydir\ -subdir=yes

This is just not how TSM works, or was ever intended to work. In other
words, DOMAIN was never intended to prevent you from backing up files on
non-DOMAIN file systems. Rather, DOMAIN is used to specify which file
systems are processed by default when you perform an incremental
operation.

Having said that, if you want domain behavior from the GUI for incremental
backup operations, then do the following:

   1) start dsm
   2) Select the "Action/Backup Domain" menu option

The backup part of the GUI allows you to pick and choose objects to back
up, just as you can use the "dsmc incremental" or "dsmc selective"
commands to pick and choose objects for backup. Whether from command line
or GUI, there is no relationship between DOMAIN and the objects on which
you can operate by explicitly picking and choosing from the GUI or from
listing the objects in a SELECTIVE or INCREMENTAL operation.

I think what you are thinking of is the EXCLUDE.FS option available on
Unix clients, which prevents backup of excluded file systems.

I hope this clarifies things.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-11-17
19:03:52:

> Andy, Sorry my point was that while the domain statment in the dsm.
> opt file does effect what is backed up from a command line and
> scheduler standpoint it does not effect what you see in the GUI and
> where you see it in the GUI.
>
>   I ran a number of tests.  Every time a mapped drive shows up in
> the GUI under Network even when it is not in the dsm.opt file.
> Every time a UNC never shows up under the GUI when it is in the dsm.
> opt file. I think it has always been this way.
>
>   Now if you think it is a bug then I'd be happy to see things in
> the GUI based on the domain statement. So I could put  -C: to make
> sure the C:\ doesn't show up in the GUI and web client or
> \\Server\SHARE so that it does show up in the GUI and web client.
>
>   Again, where the mapped drives show up isn't an issue at all to
> me. It makes complete sense that they would show up under Network.
>
> Andrew Raibeck <storman AT US.IBM DOT COM> wrote:
>   Hi Kyle,
>
> If the drive letter maps to a network resource, then it makes sense to
> have it show up under network, whether it's in the domain or not.
>
> I think if it is a valid resource to back up at the domain level, it
> should appear in the GUI. The command line client and the scheduler
> certainly recognize it when it's in the DOMAIN list.
>
> Regards,
>
> Andy
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Development
> Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
> Internet e-mail: storman AT us.ibm DOT com
>
> IBM Tivoli Storage Manager support web page:
> http://www-306.ibm.
> com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
>
>
> TSM_User
> Sent by: "ADSM: Dist Stor Manager"
> 2005-11-15 16:16
> Please respond to
> "ADSM: Dist Stor Manager"
>
>
> To
> ADSM-L AT VM.MARIST DOT EDU
> cc
>
> Subject
> Re: TSM Win client DOMAIN statement and unc names
>
>
>
>
>
>
> Andy are you sure? I don't remember seeing UNC paths that have been
added
> to a dsm.opt show up in the GUI ever. I'm wondering if the F: drive
shows
> up in Wanda's case because it is mapped and all mapped drives show up
> under Network in the GUI. I just mapped a drive without ever putting
> anything in the dsm.opt and I see it under Network. Further I added it
to
> the dsm.opt and that didn't change the fact that it only showed up under
> Network.
>
> What I'm asking is do you really think adding something to the domain
> statement, drive letter or UNC, will really have an effect on the GUI?
>
> I'm running the V5.2.3 client on WinXP
>
> Kyle
>
> Andrew Raibeck wrote:
> Hi Wanda, I would call this a bug.
>
> Regards,
>
> Andy
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Development
> Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
> Internet e-mail: storman AT us.ibm DOT com
>
> IBM Tivoli Storage Manager support web page:
> http://www-306.ibm.
> com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
>
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
> "ADSM: Dist Stor Manager" wrote on 2005-11-15
> 15:03:08:
>
> > I'm confused:
> > TSM client 5.3.x on Win2K:
> >
> > If I map a network drive as drive F: and add it to my dsm.opt file
this
> way:
> >
> > DOMAIN ALL-LOCAL F:
> >
> > Assuming I have the right permissions, the scheduler will back up
F:just
> fine.
> > When I open the GUI client and do edit-> preferences -> Backup, I
> > can see F: is in the domain list, and I can select it for backup.
> >
> >
> > If I DON"T map a drive letter, but I add that same drive to my dsm.
> > opt file this way:
> >
> > DOMAIN ALL-LOCAL \\host\d$
> >
> > Assuming I have the right permissions, the scheduler will back up
> > this drive just fine.
> > But when I open the GUI client and do edit -> preferences -> backup,
> > it isn't in the domain list, and I can't select it from the GUI.
> >
> > Is this WAD? I found in the doc where the unc name is allowed in
> > dsm.opt, but can't find an explanation of the difference in the
> > scheduler and GUI behavior?
> >
> >
> > Thanks
> > Wanda Prather
> > "* I/O, I/O, It's all about I/O *" -(me)
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>
>
>
> ---------------------------------
>  Yahoo! FareChase - Search multiple travel sites in one click.