> However, I need to backup data to two different pools. I have a couple 
> of project spaces that get backed up directly to tape and bypass our ADD 
> devices. My first thought was to place a .nsr directive at a level 
> /global/proj level to skip evertying below it. Then, I would list only 
> those project file systems at /global/proj/proj1 .. /global/proj/projN 
> into the backup client. However it appears that this causes the data to 
> be skipped as it seems that all .nsr files are processed starting at the 
> root which is not what I expected. It does make sense though.

Not easy to find, but this is documented in the NSR(5) man page.

> My next thought is to use pre/post processing to remove and put back the 
> .nsr directive file. I have not tested this, but it seems like a pretty 
> big hammer for a small problem.

I haven't tried it, but perhaps using the "ignore" directive will work
here to ignore the .nsr files in the subdirectories.

-- 
Darren Dunham                                           ddunham AT taos DOT com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

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