Networker

Re: [Networker] Different pools VS ALL

2008-04-15 11:47:18
Subject: Re: [Networker] Different pools VS ALL
From: "Coty, Edward" <Edward.Coty AT AIG DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Tue, 15 Apr 2008 11:44:13 -0400
 You can run a saveset of ALL and assign the client to two different
groups. Assign each group to the pool that you want to use. If the same
browse and retention policies this will work fine. If you wanted
different retention polices for the different pool(main reason why you
would do this) then create two clients with a saveset of ALL. Assign
each client to the group that is assigned to the pool you want. I have
had better luck creating directives on the backup server and assigning
the directive to the client you want to skip file systems or directories
on. This way you manage from a central location instead of managing .nsr
directives on the client. 


EDWARD COTY
LEAD STORAGE ENGINEER, LCNA, NACP
WORK - 973-533-2098
CELL - 973-296-0918
EDWARD.COTY AT AIG DOT COM

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Matthew C. Aycock
Sent: Tuesday, April 15, 2008 11: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

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

<Prev in Thread] Current Thread [Next in Thread>