Some weeks ago I was going to ask the exact same thing, but what I
settled on was keeping job records as long as I'd need to keep the job,
file records about the same time (since my retention periods are short
-- 2 weeks of data is the SLA that I have), and volumes just long enough
so that they'll expire before I want them re-written. My assumption is
that this warning that you've pointed out is to keep you from having a
year of jobs with files saved for each one, because that could make for
a messy database. What I'm NOT sure of is why you'd want to keep jobs
any longer than the volume, or even why the functionality is there to
keep jobs and volumes for different lengths of time (for the record,
this exists in OmniBack too). I'm guessing it's so the jobs are there
for tapes that may have expired but have not yet been rewritten.
In any case, I think what that part of the manual means is "you might
want to throw away the file data much sooner than the job data," not
that you should artificially pad the job retention period.
Patrick Van der Veken wrote:
Kern Sibbald wrote:
On Tuesday 14 March 2006 22:18, Patrick Van der Veken wrote:
Ryan Novosielski wrote:
Are your JOBS set to expire soon enough to recycle the tape? There are
per-job retention periods to contend with.
Hi Ryan,
I do not think this is relevant as the Bacula manual clearly states that
Bacula will always take the shortest of the all retention periods (Job,
File, Volume) into account? In our case, job retention is a year.
This is probably not a very good idea (having a long job retention and shorter
volume retention). The problem is that your jobs will not be regularly pruned
from your volumes, so when Bacula wants a new volume, none will be purged and
it will need to do volume pruning. At that point, with your setup there will
be be a lot of work to do, which will slow down backups, and Volume pruning
is not guaranteed to completely prune the volume if it exceeds the maximum
pruning size that Bacula permits. So failures like you are seeing might
occur.
Hi Kern,
Now I am getting pretty confused. The Bacula manual states (under
"Catalog Maintenance"):
"As mentioned above, once the File records are removed from the
database, you will no longer be able to restore individual files from
the Job. However, as long as the Job record remains in the database, you
will be able to restore all the files backuped for the Job (on version
1.37 and later). As a consequence, it is generally a good idea to retain
the Job records much longer than the File records."
So what is the recommendation on Job/File/Volume Retention? Keep them
all in sync? What is the "maximum pruning size" you refer to? Does this
for e.g. that Verify jobs are not pruned from the Volume?
Regards,
--
Patrick Van der Veken
Qtris BV
--
---- _ _ _ _ ___ _ _ _
|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
begin:vcard
fn:Ryan Novosielski
n:Novosielski;Ryan
org:UMDNJ;IST/Academic Systems and Technologies
adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103-2757
email;internet:[EMAIL PROTECTED]
title:185 South Orange Avenue
tel;work:(973) 972-0922
tel;fax:(973) 485-2612
x-mozilla-html:FALSE
version:2.1
end:vcard
