Scenario: I have a client with the following path:
'/0/exports/data/dir001'. I want this to get backed up to pool A
(indexing turned on), and I want everything else under /0 to get backed
up to pool B (also has indexing turned on). I want to use client side
directives. I have two NSR client resources for this client. The first
specifies 'All' for the save sets and uses default 'Unix standard
directives', and the second resource specifies '/0/exports/data/test1'
for the save set list and uses no directive. Each resource is a member
of a different group, and each group is selected for its respective pool
(A or B).
Question: Would either of the following client side directives
accomplish this? Is one preferred over the others, or is there a
different method that would be recommended?
Directive 1 (created as /0/exports/data/.nsr)
<< test1 >>
+null: .?* *
Directive 2 (created as /0/exports/data/.nsr)
<< /0/exports/data/test1 >>
+null: .?* *
Directive 3 (created as /0/exports/data/.nsr)
+null: test1
In each case, I assume that because the directive is not under the
'test1' directory itself that the save set '/0/exports/data/test1' would
not be adversely affected, i.e. would not be nulled, but a backup of
/0/exports/data or any level higher, up to /0, would apply the null to
those index entries, correct?
--
George Sinclair - NOAA/NESDIS/National Oceanographic Data Center
SSMC3 4th Floor Rm 4145 | Voice: (301) 713-3284 x210
1315 East West Highway | Fax: (301) 713-3301
Silver Spring, MD 20910-3282 | Web Site: http://www.nodc.noaa.gov/
- Any opinions expressed in this message are NOT those of the US Govt. -
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the body of the email. Please write to networker-request
AT listserv.temple DOT edu if you have any problems with this list. You can access the
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
