I still think we are having two different discussions, so I will try to
summarize them here. I apologize in advance if this doesn't clarify
things, and in that case, will concede defeat in my ability to write
effectively on the matter.
1) ORIGINAL discussion: The preferences editor displays the available file
systems that you can add to, or remove from, the domain. To see what we
are talking about, start dsm, then select the "Edit/Preferences" menu
item. This brings up the preferences editor, a multi-tabbed dialog. From
there, click on the "Backup" tab. You should see the "Domain for Backup"
section about midway down. This is the area that was in question. The
question was, in so many words, why does the connected network resource
not appear therein. My answer was that it is a bug (more like an
oversight). A network resource does not need a drive letter in order to be
accessed by TSM or other applications, so there is no real reason for the
preferences editor to limit what is displayed just because there is no
drive letter. In fact, if you define a local share, you will see that
share appear in the list of available file systems, even if it is not
currently mapped to a drive letter. Again, this is all with regard to the
preferences editor, not the backup function of the GUI.
2) YOUR point re: "Network", which was not a part of the original post or
my original response: This is not in the preferences editor, but I assume
you are talking about what you see when you start dsm and click the big
"Backup" button. For the same reasons cited above, there is no reason that
a connected network resource shouldn't appear under "Network". If you can
choose to back it up from the command line interface, then there is not
reason you shouldn't be able to choose to back it up from the GUI as well.
We are in agreement that this has absolutely nothing at all to do with
domain settings.
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-18
22:59:37:
> 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.
|
