Another related scenario that caught me by surprise...

With RMAN manual backups, no group is necessary for those backups as
they are controlled and scheduled at the client side. The retention is
determined by the media pool they write to.

There is also a client definition (for the RMAN client/server), in a
group, but it is for the file system backups. The retention for these
savesets is the same as the RMAN media pool retention - 91 days. If the
retention set in this client definition is greater than the media pool
retention for the RMAN backups, NW will use the larger of the two.

So, if you were expecting to control the retention via the media pool
for manual RMAN backups, think again. I found that another client
instance was created for this rman server, in another group, for a
special backup having a 1 year retention. The RMAN media pool was set
for 91 day retention, but mminfo showed that the actual ssretent and
clretent were getting set to the 1 year value.

When I deleted that second client instance, the rman retentions went
back to the desired retention.

Probably old news to most, but hopefully helpful to some.

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Hodges, Bruce
Sent: Thursday, September 11, 2008 11:19 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Schedules and browse/retention policies

At least up to 7.3.3.build.510, Preston is correct that applying a
schedule OR level in the group will override the client settings.

However concerning the retention policies, while you can set different
periods at the client and at the media pool, Networker will always
enforce the greater of those two settings (err on the side of caution).
As long as that is what you want, no problem.  We have done quite a bit
of testing and came to the conclusion not to use pool retention, but
instead created multiple client definitions, each with the desired
retention period (monthly, annual, etc.).

Please let me know if anyone has found a different method.

Sorry for the late response. 

Bruce


-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Preston de Guise
Sent: Sunday, August 10, 2008 11:17 PM

> Is there a way to use the group's schedules and policy settings take
> precedence over individual clients' settings?  If I need to change  
> such
> settings, is there a way to avoid changing them on every client?

If you apply a schedule or a level to a group, then whenever the group  
is automatically run it will override any client schedule settings.

In relation to retention policies, as of 7.3, you can set an override  
retention policy per pool.

Preston de Guise.

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