|
Re: [Networker] NetWorker Retention Policy Qs?
2008-12-02 08:20:11
On 12/2/08 12:49 AM, Preston de Guise wrote:
The retention values on the clones make sense... just as in my
example. Did you look at the volume expiration after you conducted
your test? I suspect the volume would expire at 12:30... (if that
was the only save-set on the volume).
Volume expiration isn't to be confused with saveset expiration.
The expected expiration date/time of a volume is just that - it's only
what NetWorker expects is going to be the date/time of the volume
expiring based on the longest-lasting saveset on the volume.
Jonathan,
What version of NetWorker are you running? I just upgraded from 7.3.3
to 7.4.3 over the weekend and I'm now working an issue with EMC where
127 tapes are reporting their volretent based on the ssretent instead of
the clretent values of the save set instances contained on them.
In 7.3.3, the volretent was properly being set based on the clretent
values. In my experience (5 days) with 7.4.3, the reported volretent
from mminfo is being controlled by the ssretent value.
--
Frank Swasey | http://www.uvm.edu/~fcs
Sr Systems Administrator | Always remember: You are UNIQUE,
University of Vermont | just like everyone else.
"I am not young enough to know everything." - Oscar Wilde (1854-1900)
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
|
|
|
