David,
I see you have received a number of suggestions methods to handle this
issue, I would like to add one more.

You can use one client configuration attached to any number of groups
provided you want the browse period to equal the longest retention. In your
example add the client to a daily group that writes to a daily pool, add the
same client to the weekly group which writes to its own pool, and do the
same for the monthly. Since you have now isolated your daily, weekly and
monthly backups to their own pool it is fairly simple to run a mminfo query
to identify tapes in you daily and weekly pools which have a last access
date greater that the retention period you really want for them. I.E if you
want to retain your daily backups for 1 week then query the daily pool for
tapes that have a last access date greater than 8 days. Use the output of
the mminfo to recycle the tapes older than a week, one caveat here is that
the last access date gets updated when a tape is opened for a read function
such as restores, If you script the mminfo and recycle then run it daily I
think you will get what your looking for.

Michael Nored
Consultant
Nored Consulting, LLC
 
M: (407) 399-8162
T:  (352) 350-7142
E: mnored AT Netzero DOT net


-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of David Dulek
Sent: Wednesday, March 19, 2008 1:21 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
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