Re: Strange errors: Warning: Director wanted Volume "foo", Current Volume "bar" not acceptable because...

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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users