On Thu, 2006-02-09 at 10:37 +0000, 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
> > full backup, each job is promoted to Full, so the first job runs
> > completes, then asks for the next tape in the pool.
> 
> Sounds like it marked the tape as 'Used' or 'Full' instead of leaving it
> open for appends...
> 

That's exactly what's happening.  See below.

> > This is not the expected behavior (imho).  I'd expect it to consolidate
> > all jobs that are schedule to run at the same time, with the same
> > storage, same pool, same priority, to the same volume.
> 
> 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. 

I can manage volume capacity myself.  I'd like to override Bacula's
default behavior of auto-picking a tape based on status/capacity/recycle
time.

I'd essentially like to "Micro-Manage" it perhaps.

I want my tapes to be written to by the scheduled jobs for their daily
assignment, by all the jobs scheduled to run at that time, and then be
marked "Used".

The trick is, if all the jobs run at the same time, don't mark the
volume "Used" or "Full" until after they've all run.

Recycling will automatically mark them "Append" after my expected
threshold (hopefully) for re-use some time during the next cycle.

I think the problem here is that Bacula doesn't consider multiple "Jobs
{}"s as defined in *-dir.conf that start at the exact same time per
their shared schedule as a single "Job" in retrospect to on-tape format.

If there was a broader name for any series of jobs on the same schedule,
say "JobSet", "Batch", or "Aggregate", the option I'm looking for would
be called:

Maximum Jobs Batch = 1
Maximum Scheduled Jobset = 1

Thoughts?

~lava

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to