Hi Greg,
The answer to you "side note" question is in my prior reply on this thread
(see below) starting with the line "As to why it works this way...".
Restating the answer differently:
If you omit DOMAIN from dsm.opt, then the it defaults to DOMAIN ALL-LOCAL.
Let's call this the "base" domain (this is not official TSM terminology,
just a term I'm using here to help facilitate the explanation).
If you specify one or more DOMAIN statements in dsm.opt, then those become
the base domain.
DOMAIN statements are cumulative. So the following statement in dsm.opt"
DOMAIN C: D: E:
is equivalent to:
DOMAIN C:
DOMAIN D:
DOMAIN E:
or
DOMAIN C: D:
DOMAIN E:
etc.
Any DOMAIN statements specified outside of dsm.opt (i.e. from the command
line, or from the OPTIONS parameter in a schedule definition, or from a
client options set) are added to the base domain. They do not replace the
base domain.
In your case, you do not have any DOMAIN statement in dsm.opt. Therefore
the base domain is ALL-LOCAL. Specifying DOMAIN D: via the client options
set is equivalent to coding this in dsm.opt:
DOMAIN ALL-LOCAL
DOMAIN D:
which on your system effectively amounts to:
DOMAIN C: D: SYSTEMOBJECT
Note that SYSTEMOBJECT is included in ALL-LOCAL, and the DOMAIN D: is
redundant since it is already part of ALL-LOCAL.
Specifying DOMAIN -C: D: via the client options set is equivalent to
coding this in dsm.opt:
DOMAIN ALL-LOCAL
DOMAIN -C: D:
which effectively amounts to this:
DOMAIN SYSTEMOBJECT D:
This is why you were seeing D: and the system objects getting backed up.
Adding DOMAIN -SYSTEMOBJECT to your client options set (along with the -C:
and D: is the same as coding this in dsm.opt:
DOMAIN ALL-LOCAL
DOMAIN -C: D: -SYSTEMOBJECT
which effectively amounts to this:
DOMAIN D:
Hope this helps.
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.eyebm DOT com (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Greg Redell <GRedell AT GWL DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/22/2003 13:28
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: AW: Client Options Sets
My original statement of the question was very vague, and I think that I
was working too close to the problem. The system only has two local disk
drives C: and D: . I did not state this in the original post. Andy was
correct in his assumption of my core issue. I will post another email
tomorrow after the system backs up tonight, confirming that he was correct
in his statement of a solution.
Though as a side note, what I am trying to replace in the local option
file is "domain d:" so I assumed that specifying in the option value
"d:" would give me the equivalent of the previously mentioned domain
statement. So why do I have to format the option value as "-c: d:
-systemobject"? Does the client option set domain parameter assume
ALL-LOCAL to begin with?
Greg Redell
Great-West Life & Annuity Insurance Co.
Phone: 314-525-5877
Email: Gredell AT GWL DOT com
Andrew Raibeck <storman AT US.IBM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/22/2003 01:18 PM
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: AW: Client Options Sets
What question? Do you mean:
"Is anyone out there using the domain parameter in a client option
set?"
The trivial answer to that is "yes", but I didnt' really think that was
the "question" (though I could be wrong). My perception was that the
poster wanted a way to avoid backing up the system objects, implemented
through client options sets rather than local options files. I think my
answer works for that.
As to why it works that way (Juraj, is this what you are asking for?):
If DOMAIN is not coded in the options file, then DOMAIN ALL-LOCAL is the
default. So coupled with the current client options set (remember, DOMAIN
statements are cumulative), the domain effectively looks like this:
DOMAIN ALL-LOCAL -C: D:
My suggestion make the domain look like this:
DOMAIN ALL-LOCAL -C: D: -SYSTEMOBJECT
So all domains except for C: and SYSTEMOBJECT will be backed up. If all
Greg has is C:, D:, and SYSTEMOBJECT, then this resolves the issue.
Another alternative that doesn't involve the client options sets: modify
the client schedule so that D: is specified in the OBJECTS setting, i.e.:
upd sch standard mysched objects="d:"
Other ideas are welcome, and if I've missed the point, perhaps Greg can
restate the question.
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.eyebm DOT com (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Salak Juraj <j.salak AT ASAMER DOT AT>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/22/2003 10:32
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: AW: Client Options Sets
Hmm ;) Andy,
while this is a good point this does not answer the question, does it?
Regards,
Juraj
P.S. "Good enough" is the enemy of excellence.
-----Ursprüngliche Nachricht-----
Von: Andrew Raibeck [mailto:storman AT US.IBM DOT COM]
Gesendet: Dienstag, 22. April 2003 19:10
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Re: Client Options Sets
Why not add "-systemobject" to the domain setting in your client options
set?
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.eyebm DOT com (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Greg Redell <GRedell AT GWL DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/22/2003 09:36
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Client Options Sets
Is anyone out there using the domain parameter in a client option set?
I am trying to just back up the D drive on a machine, in the option set I
have domain option value set to "-c: d:".
There is no domain option in the local options file, and the issue is that
the system objects keep getting backed up!
Given that this is a field office with a 128 K connection, this is an
issue. I would like to use the option sets and yes I could just use the
local option file, but I would like to keep as little settings in the
local option file as possible.
Client: 5.1.5.15
Server: 5.1.6.2
Thanks for any input!
Greg Redell
Great-West Life & Annuity Insurance Co.
Phone: 314-525-5877
Email: Gredell AT GWL DOT com
|
