Re: [Networker] Different pools VS ALL

.nsr files are out of control here now. Too many developers and
sysadmins are using them, then forgetting them, then complaining when
they cant restore a file later on.

One rather blunt tool to solve that problem is the 'ignore' keyword,
which I urge everyone with large numbers of clients to stick in their
global directives. 

> -----Original Message-----
> From: EMC NetWorker discussion 
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Curtis Preston
> Sent: Wednesday, 16 April 2008 5:49 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Different pools VS ALL
> 
> FWIW, I think .nsr files are evil.  Directives of that sort 
> should be in
> the directives accessible and viewable from the NetWorker server.
> Putting them in a file in a filesystem somewhere is just asking for
> future trouble.  Here's a blog post I did a while back on the topic:
> 
> http://www.backupcentral.com/content/view/38/47/
> 
> 
> ---
> W. Curtis Preston
> Backup Blog @ www.backupcentral.com
> VP Data Protection, GlassHouse Technologies 
> 
> > -----Original Message-----
> > From: EMC NetWorker discussion 
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
> On
> > Behalf Of Matthew C. Aycock
> > Sent: Tuesday, April 15, 2008 8:33 AM
> > To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > Subject: [Networker] Different pools VS ALL
> > 
> > I am in the process of migrating from 7.2.2 to 7.4.1 on 
> Solaris 10. As
> > part of this upgrade I want to get rid of our old and archaic backup
> > schedule. I want to get rid of listing our filesystems one 
> by one and
> > use the ALL saveset.
> > 
> > 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.
> > 
> > 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.
> > 
> > So, I guess the question is "How are you handling the backup of the
> same
> > client going to multiple backup pools?"
> > 
> > --
> > Thanks,
> > 
> > Matthew
> > ----------
> > Matthew C. Aycock
> > Operating Systems Analyst/Developer, Lead
> > Dept Math/CS
> > Emory University, Atlanta, GA
> > Internet:  matt AT mathcs.emory DOT edu
> > 
> > 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
> > 
> > 
> > 
> > 
> > 
> > This email and any files transmitted with it are confidential and
> intended
> > solely for the use of the individual or entity to whom they are
> addressed.
> > If you have received this email in error please notify the system
> manager.
> > This message contains confidential information and is intended only
> for
> > the individual named. If you are not the named addressee you should
> not
> > disseminate, distribute or copy this e-mail.
> 
> 
> 
> 
> 
> This email and any files transmitted with it are confidential 
> and intended solely for the use of the individual or entity 
> to whom they are addressed. If you have received this email 
> in error please notify the system manager. This message 
> contains confidential information and is intended only for 
> the individual named. If you are not the named addressee you 
> should not disseminate, distribute or copy this e-mail.
> 
> 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
> 

NOTICE
This e-mail and any attachments are confidential and may contain copyright 
material of Macquarie Group Limited or third parties. If you are not the 
intended recipient of this email you should not read, print, re-transmit, store 
or act in reliance on this e-mail or any attachments, and should destroy all 
copies of them. Macquarie Group Limited does not guarantee the integrity of any 
emails or any attached files. The views or opinions expressed are the author's 
own and may not reflect the views or opinions of Macquarie Group Limited.

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