Brian A. Seklecki wrote:
On Thu, 2006-02-09 at 10:37 +, Russell Howe wrote:
Bacula will do this. Check you don't have Maximum Volume Jobs = 1 in
I do. This is because I'm trying to enforce a specific threshold of a
single-tape-per-day policy.
Ah, but this is a single-tape-per-job
Russell Howe wrote:
I have this comment in the configuration to remind anyone who might
inherit this setup:
# ** VERY IMPORTANT **
# In the database, the media entries have a MaxVolJobs setting. This is
# what determines that a tape is full.
#
# Current values are:
# Cases tapes: 10 (Cases,
On Sun, 12 Feb 2006, Brian A. Seklecki wrote:
Bacula will do this. Check you don't have Maximum Volume Jobs = 1 in
I do. This is because I'm trying to enforce a specific threshold of a
single-tape-per-day policy.
Wrong directive.
Try Volume Use Duration = 23 hours
in the pool definition.
On Mon, 2006-02-13 at 10:42 +, Russell Howe wrote:
When it comes to marking tapes as Used or Full, there seem to be two
ways to do it currently:
* Maximum Volume Jobs
* Volume Use Duration
So, you can either say 23 hours after the first job which wrote to
this
tape
On Thu, 2006-02-09 at 10:37 +, Russell Howe wrote:
Brian A. Seklecki wrote:
But in either configuration, the jobs launch at the same time in the
scheduler and run in series/serial. Thus, if the database is purged,
and each job is configured as incremental, and there is no record of a
