Hi all,

I have 2 disk-based bacula servers:

1. bacula-5.2.13 on x64 centos 6 with "single drive" vchanger -- i.e.
writing one volume at a time.

2. bacula-7.0.5 on x64 centos 7 with single filesystem storage.

On both servers job and attribute spooling are on.

On #1 I have max concurrent jobs = 10 in director and storage stanzas,
and 15 in bacula-sd's storage. I've watched it write 5-6 spool files in
parallel while despooling to storage at the same time, works quite fast.

On #2 I added "max job spool size = volume size" and "max spool size =
volume size * max concurrent jobs" because the spool in on the (smaller)
drive.

There's only one job getting spooled at a time on #2.

So I added max concurrent jobs = 2 to each client (I normally have 2
jobs defined /client) and max concurrent jobs = 2 in jobdefs and I still
have only one job spooling. I expect to see at least 2. The problem of
course is that here spool-despool is strictly sequential and I get all
the downsides of writing stuff twice without the main benefit.

Any idea why? Did something change between 5.2 and 7.0? Can it be "Label
media = yes" on #2 vs pre-labeled "slots" on #1? Limiting spool size on
#2 shouldn't cause this. Something else I'm missing?

TIA
-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu

signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users