|
Re: [Networker] How to implement retention policy (monthly archive)
2008-07-15 10:22:07
Jim Allison wrote:
I'm looking for input on how to implement the following policy: 60 day
retention standard, but monthly backups retain for 7years. We run a weekly
full with incremental backups typically. I know one option is to create two
client definitions for each client and use separate groups/pools. That
method still leaves the problem of how not to run the normal weekly when the
monthly archive needs to run. Any ideas on how to implement this cleanly
without a largely manual process? I played with creating a custom schedule,
but networker keeps trying to anticipate what I am trying to do and moving
the day of the full. I run on windows (unfortunately) and have thought of
using an AT job to disable the normal groups and enable the archive groups
once a month. I have also thought of just cloning the end of month weeklys
and sending those offsite.
We are running 7.4.2 on Windows 2003 server.
Hi Jim,
What you are trying to do is possible, and you don't need to resort to
hacky methods like at jobs to reconfigure your system.
You also don't need to create two client resources for each client, you
can do it with one client in two groups. Use the schedule attribute on
the groups to override the schedule on the client. When I do this, I
usually have a schedule called "using group schedule" and apply this to
the client, just to make it obvious for anyone looking.
The key to the scheduling is a textual override. First create your
schedule for the daily group to be whatever you need, then create a
schedule for your monthly group which skips every day. Now in NMC,
uncheck the option called "Show Schedule as Calendar". Now when you look
at the properties of a schedule you will see a text box called override.
In this box put something like:
skip first Friday every month
for the daily group, and:
full first Friday every month
for the monthly group.
Now, your daily group will be a member of a pool called something like
60days, and your monthly group will be a member of a pool called
something like 7years. Set the retention field on the pool to the
appropriate policy, and this will override what is set in the client
resources. You might want to set up a "using pool policy" policy to
apply to your clients, again to make it obvious what is happening.
The only thing wrong with this strategy is that your browse policy
cannot be longer than 60 days, because browse can never be more than
retention and you can't force the browse policy on the pool in the same
way you can retention. Thus your monthly backups will stop being
browsable after 60 days, this may or may not be a problem for you. There
are ways round this, but these ways usually require a script.
Hope this helps.
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
|
|
|
