I know going on with this is going to seem like I have to be write but I think
I've done a poor job of pointing out what I disagree with you on. So here goes
one last time.
She said the following:
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?
To which you said:
Hi Wanda, I would call this a bug.
I believe:
No it is not a bug. Putting a UNC path in the domain statement will not make
it show up in the GUI under backup. It never had. A UNC path is not a mapped
drive. Further she gave another example about when she put a mapped drive in
the dsm.opt's domain statement it showed up in the GUI. To that I say it wasn't
the fact that she put a mapped drive letter in the dsm.opt that caused it to
show up under Network but rather it was simply the fact that the drive was
mapped. You could have just had "ALL-LOCAL" in the domain statement and you
would still see the mapped drive in the GUI.
The thing I want to make sure everyone is clear on is that the domain
statement is not what the GUI uses to build its list of what you can select to
backup. The GUI simply lists all local drives under local and mapped under
Network. And of course mount points and other things were appropriate. But UNC
paths never show up because they are remote things not locally mounted or
mapped. Putting them in the dsm.opt's domain statement will in no way add them
to what you see in the GUI for backup.
Now all this can be confusing because once you do backup a UNC it does show
up under restore but that is only because once backed up it is now a new
filespace that can be restored.
Kyle
PS.
I'm sure you are correct on all your points. Sorry for my poor manor in
conveying what I was asking. I hope this was better.
Andrew Raibeck <storman AT US.IBM DOT COM> wrote:
Hi Kyle,
> From the very first e-mail on this thread Wanda asked if why when
> she added a UNC to the domain stamtement why it didn't show up in
> the GUI. You said yes that looks like a bug.
She was referring to the *preferences editor*, specifically the BACKUP tab
where the domain list is pre-filled with available file systems that you
an add to the list. She was saying that TSM otherwise treats the share as
a valid domain object, so why doesn't it show up as a selectable item from
the Backup tab's list of available file system objects.
And I agreed, saying that the absence of this object seemed like a bug.
And by extension, I would also expect to see such a share show up in the
Network part of the GUI's backup window, but yes, *that* specifically has
nothing at all to do with domain.
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-18
16:41:16:
> No *WAIT*.
>
> I'm not drawing any conclusions to anything.
>
> From the very first e-mail on this thread Wanda asked if why when
> she added a UNC to the domain stamtement why it didn't show up in
> the GUI. You said yes that looks like a bug.
>
> I disagree. I don't think it is a bug. I think that putting
> something in the domain statement *DOES NOT* make it show up in the GUI.
>
> Sorry if my explanation wasn't clear. Now if I'm wrong and it
> should then let me know that.
>
> Kyle
>
>
> Andrew Raibeck wrote:
> 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" 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 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.
>
>
>
>
> ---------------------------------
> Yahoo! FareChase - Search multiple travel sites in one click.
---------------------------------
Yahoo! FareChase - Search multiple travel sites in one click.
|
