Thanks to everyone *across the globe* who helped me with this setup. :)

Here is what the situation looks like now.

The goal:
Single Networker Server.  The goal is to be able to restore to any M-F in
the previous 28 days or to restore to the first of any previous month.

The solution:
Four groups, Four schedules, two pools, and two client definitions of the
same host.

Monday through Friday
Group Morning(9:00am), Schedule Morning(sfffffs) is a Full backup of the
host definition #1
Group Midday(12:00pm), Schedule Midday(siiiiis) is an Incremental of the
host definition #1
Group Afternoon(5:00pm), Schedule Afternoon(siiiiis) is an Incremental of
the host definition #1

Early the next day tape is ejected via script and taken offsite.
Prior to Group Morning the next of 20 tapes is inserted by operator.

Host #1 client definition has both a custom browse and retention policy of
26 days.  This ensures that by day 28 when the tape rolls around to be used
the savesets on it should be in recyc mode.  The tape drive is set to use
Auto Media Management which will re-label this tape with its existing label
and allow tape to be overwritten.  The problem I was running into here is
that if all savesets were not in recyc mode the new backups would be
appended and a few cycles into the system the tape would fill up creating
problems.

First day of each Month
Group Monthly Full(8:00am), Schedule Monthly is a Full backup of the host
definition #2.  This allows for the tape to be inserted on a Monday morning
if the first happens to be a Saturday or Sunday since there is no operator
on those days.  Once finished, savepnpc:post runs a script to eject and
notify the operator to mount the normal daily tape.

Host #2 client definition is identical to host #1 except that it has a
custom browse and retention policy of 25 years.

Probably more than you all wanted to know, but maybe it will help someone.
Plus it helped me to write it out for my documentation.

--Shawn



-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Shawn Cox
Sent: Thursday, November 30, 2006 10:26 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Browse and Retention planning/question

Good morning Networker's from Snowy West Texas.  If you're in Seattle I'll
shut up now.

One of my Networker installations is a very small single host setup v7.2.2.
It is a single Windows server which is a Domain Controller.  It is the only
host backed up by this Networker installation.  It has a local tape drive to
which all backups are written.  It is not part of my Enterprise installation
backup for policy reasons.

I would like to implement 2 separate browse/retention policies for this
single host.  One is a pool of 20 tapes that rotate with browse/retention of
28 days.  The reason for this is so that I can utilize Auto Media Management
to automatically re-label the tapes once they rotate around and have reached
recyc status.  The other pool is an infinite browse/retention for a backup
that is taken the first of every month.

How can I accomplish different browse/retention policies for a single host
which happens to be the Networker server?

--Shawn

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