> UseVolumeOnce definition in the manual which points to the warning in the
MaximumVolumeJobs docs. The manual actually warns against using this in the
specific case of multiple simultaneous jobs.

Aha! I'm doing it wrong. ;)

I think I'll switch to either more conventional volume configurations (size
limited, not job count or duration limited), or set up staggered job
priorities. It occurs to me that maybe I could limit 'maximum concurrent
jobs' to 1. I don't think I'd like that, entirely, though I don't really
understand if my jobs are actually running concurrently as it stands.
Varied priorities with one job per priority level would (probably) have the
same effect as 'maximum concurrent jobs = 1', since only jobs with that
priority level would be allowed to run. I guess I'll think on it, and
assume that staggered job priorities would be the safest.

I'll go read the manual for each of these options more thoroughly later.
Thank you for your help!

Regards,
Robert Gerber
402-237-8692
r...@craeon.net


On Thu, Mar 27, 2025 at 5:14 AM Josh Fisher <jfis...@jaybus.com> wrote:

>
>
> On 3/26/25 17:58, Rob Gerber wrote:
>
> Josh,
>
> Good catch! I didn't notice that jobs 662 and 663 started at exactly the
> same time.
>
> Your theory sounds very persuasive. I have one doubt, though: *why did
> job 662 write files to both volumes 250 and 251? *bls shows that 662
> wrote most of its data to volume 250, and then wrote a bunch of smaller
> files to volume 251. Volume 250 didn't have an 'End Job Session' record
> from job 662. That record was in the first part of volume 251, after around
> 1000 small files. Why might job 662 have written to two volumes?
>
>
> I don't know why job 662 would have written to volume 251. That part makes
> no sense to me, and job 662 made no log entry regarding switching to volume
> 251. Note the last paragraph of the UseVolumeOnce definition in the manual
> which points to the warning in the MaximumVolumeJobs docs. The manual
> actually warns against using this in the specific case of multiple
> simultaneous jobs.
>
>
>
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to