Hello,
You should be able to accomplish lot of flexibility once the Groups and 
Pools are though out thoroughly, i.e use a external scheduler and run the 
same Group with different pool attributes on a schedule based on external 
scheduler.
i.e
GROUPA---Run weekday with "Pool incremental daily" Run this savegrp script 
on all days except Monthend weekend  ( Pool retention policy of 28 days )
GROUPA---Run Weekend with "Pool MonthEnd"  Run this Group script on 
MonthEnd only, pools retention policy should be 12 months.
GROUPA-Schedule can be customized as you like
Pools will control your tape retention, schedules will control your backup 
level and start time.
Alternatively, you can just script a savegrp to do the retention also, 
this was thought out prior to pool retention feature came out, so you can 
choose any method you like.
The examples below highlights using external scheduler capabilities to use 
the same group and achieve different results, this solution will require 
minimal scripting, this are purely examples only and you should think out 
your strategy and implementation, testing before applying them.
savegrp -r2 -v -l incr -e "month" -G PROD
savegrp -r2 -v -l FULL -e "year" -G PROD
HTH



David Dulek <ddulek AT FASTENAL DOT COM> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
03/19/2008 12:21 PM
Please respond to
David Dulek <ddulek AT FASTENAL DOT COM>


To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc

Subject
Re: [Networker] index default browse and retention






But as Michael Nored pointed out, NetWorker will use the longest period of 
the 
2, per the field help in the pool configuration screen.

How do I configure a long enough browse policy on my monthly group and get 
the 
daily and weekly to use the shorter retention policy of the pool?

If I am missing something, let me know because having a daily, weekly, 
monthly, and module(s) client definitions seems like a lot of work up 
front 
but I do not see anyway around it to accomplish this task.

On Wednesday 19 March 2008, Davina Treiber wrote:
> Teresa Biehler wrote:
> > We have at least 3 client definitions for each client.  In fact, in 
some
> > cases (Exchange, MS SQL), we have more than 3.  We do this to get the
> > data retention and pool separation that we need for our daily, weekly
> > and monthly backups.  Initial set-up was not fun, but it is not too
> > difficult to manage. You do, however, need good processes including
> > scripting common tasks (creating clients, updating groups, etc.).
>
> If you are doing Exchange, MS SQL, and filesystem backups for the same
> client, you will need multiple client resources as each of them will
> have different save set lists and backup commands.
>
> However if you are backing up the same save sets with the same backup
> command and all that changes is the pool and/or retention you can
> achieve the same effect without as many client resources. All you need
> to do is make the client a member of multiple groups. Each of these
> groups can have different schedules (which overrides the schedule set on
> the client) and each group can be assigned to a different pool, allowing
> the data to be have a different retention (specified on the pool).
>
> One slight snag may occur if the browse period is longer than any of the
> retention periods set on the pool - as pointed out by another poster
> earlier today. There is no easy solution to this - other than for the
> developers to have done the job properly.
>
> 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



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