You could copy that current client options set, to a new one and remove
the .dbf and ctl entries from it just for this one node, and then any
that may come around like it. It would be a one off, but that would
work.
Then you could put the
exclude /.../*.dbf
include /db_backup/PRODBKUP/datafiles/*.dbf
Type entries in the dsm.sys file or in a inclexcl.list file as we do.
Just remember TSM reads the list from the bottom up.
See Ya'
Howard Coles Jr., RHCE, CNE, CDE
John 3:16!
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Hughes, Timothy
Sent: Monday, March 21, 2011 12:44 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Solaris Include/exclude .dbf question
Howard,
Still can't find anything on that so what I did was to create another
Solaris system option set (without the excludes for *.CTL, *.ctl, *.DBF,
and *.dbf) but keep everything else in place and I assigned it (meaning
that particular client only) to use that new client option set.
I removed those excludes from the dsm.sys, I think that will work for
the time being until I can find a way to update the option set to value
No and get the correct syntax working.
regards
-----Original Message-----
From: Hughes, Timothy
Sent: Monday, March 21, 2011 12:07 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: RE: Solaris Include/exclude .dbf question
Howard Thanks!
Now I need to find out how to check and possible set the option for
override to "off" if that is possible to do on that specific client node
only.
I think I need to update the option values to >>> Use Option Set Value
(FORCE): No If it is yes
Or I can simply remove *.CTL, *.ctl, *.DBF, and *.dbf from our system
client option set however that would remove those excludes from ALL the
Solaris clients, Not just the one client I am working on.
I put this in the dsm.sys file >>> include /.../*.dbf I think that's
correct? I think that may be more than what I need for just the
following director
/db_backup/PRODBKUP/datafiles.
best regards
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Howard Coles
Sent: Monday, March 21, 2011 11:43 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Solaris Include/exclude .dbf question
They can if the client option set entries don't have the option for
allow override set to no. I have just never tried in a dsm.sys to
override one.
See Ya'
Howard Coles Jr., RHCE, CNE, CDE
John 3:16!
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Hughes, Timothy
Sent: Monday, March 21, 2011 10:04 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Solaris Include/exclude .dbf question
I guess the first question is CAN the client option set include/exclude
parameters be overrided I assume they can..I am still looking
Thanks
From: Hughes, Timothy
Sent: Monday, March 21, 2011 10:42 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Solaris Include/exclude .dbf question
I did a "q inclexcl" and our solaris client option seems to be excluding
important files in a directory called >>>/db_backup/PRODBKUP/datafiles
Exclude All /.../*.DBF
Exclude All /.../*.CTL
If i edit the dsm.sys file to include these files is the following
syntax correct?
Include All /.../*.DBF
Include All /.../*.CTL
Or if I just wanted to include in that specific directory would it be
Include /db_backup/PRODBKUP/datafiles/*.dbf
Or
Include /db_backup/PRODBKUP/datafiles/*.../*.dbf
Also here is a example of one of the files (akd01.dbf)
Thanks
|