Networker

Re: [Networker] NetWorker Retention Policy Qs?

2008-11-25 12:24:01
Subject: Re: [Networker] NetWorker Retention Policy Qs?
From: Davina Treiber <Davina.Treiber AT PEEVRO.CO DOT UK>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Tue, 25 Nov 2008 17:20:08 +0000
JGillTech wrote:
It's not the data retention policy I am having a problem with.  Its the 
automatic recycle of media.  My full volumes should recycle (auto media 
management enabled) 2 months after the last write.  However, the expiration on 
my full volumes is that same as my clone volumes... 1 year rather than 2 months.


First of all, it's been said dozens of times on this list (many of them by me), but Auto Media Management is irrelevant to recycling and retention. AMM is only for labelling of new media, nothing else.

Now to the problem in hand:
You haven't said what version you are running, but with very recent versions it IS possible to have a different retention for different clones of the same save set. The retention you specify in the client will be the one that applies to the initial backup. If you specify a different retention when you run the clone, or specify the clone pool with a different retention, this new retention will apply to the clones. This does work.

Perhaps you are making the mistake of looking at the volume expiry rather than the save set expiry? You should always look at individual save sets to work out when they will expire, then the volume will expire soon after all the save sets have expired, regardless of NetWorker's _prediction_ of volume expiry date.

Or perhaps you are not giving them quite long enough to allow them to expire? A save set will not expire until all its dependencies have also expired, often giving the effect that a full does not expire until the next oldest full reaches its expiry date.

The best way to troubleshoot expiry times is to list all the save sets on a volume in date order using mminfo. The command could be something like:

mminfo -q "volume=XY1234" -ot -r client,name,savetime,ssretent,clretent

Then you will be able to see when the volume is likely to expire, bearing in mind any dependencies that may exist. Any client config problems should be pretty obvious at this point.

HTH.

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