The other question I had regarding this issue is how to reconcile job
retention vs. volume retention. With an appendable volume, if jobs are
held for 30 days, they will expire at all different times. I'm not sure
how this can relate to media retention, which obviously can only be
around until one point. When does the media retention counter start,
basically, is the question. First write? Last write?
---- _ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | | Ryan Novosielski - User Support Spec. III
|$&| |__| | | |__/ | \| _| | [EMAIL PROTECTED] - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.| IST/AST - NJMS Medical Science Bldg - C630
Harondel J. Sibble wrote:
On 1 Dec 2005 at 10:37, Kern Sibbald wrote:
Yes, a shorter Volume retention period will "force" pruning of job and file
data, but as the manual and a recent email point out, after changing the .conf
volume retention period, you must update the catalog data for volumes that
already exist.
Okay, now I am even more confused. My volume retention period is 6 days and
has always been 6 days, while the job retention period was set for 30 days.
On day 7, the volumes does NOT auto recycle unless I purge it. Pruning it
only removes 2 files normally of the 25 or so on the tape.
Now that I've adjusted the job retention period to 6 days, do you I still
need to update the volumes? Or is the job retention period a red herring? Or
is there something else I need to do?
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
