On 7/29/25 11:07 AM, Kelly Price wrote:
Hi
     I have a number of servers, some which are quite large (50TB+). I also 
have some servers that are relatively small. I do monthly full backups, weekly 
differential, and daily incremental backups. The problem I’m having is that the 
smaller servers complete their full backup,  then wait until the bigger servers 
have completed their full backups before starting on differential and 
incremental backups. There should be no interdependencies between servers. I 
have Maximum Concurrent Jobs set to 16, Allow Duplicate Jobs = no, Cancel Lower 
Level Duplicates = yes, Cancel Queued Duplicates = yes, and Cancel Running 
Duplicates = no. The jobs all have the same priority set.

Is there a setting change which will allow the smaller servers to continue with 
lower level jobs while the larger servers are still doing full backups?

Thanks,
Kelly
Hello Kelly,

At first glance, and without seeing any configs, logs, or status outputs, and since you stated they all run with the same priority, this sounds like a "MaximumConcurrentJobs" issue to me.

While the smaller server jobs are waiting, what is the `status director` (`s dir` for those of us who type as little as possible :), showing at this time?

MaximumConcurrentJobs is set in a lot of places:

- Director
- File Daemon
- Storage Daemon
- Storage Daemon Device
- Director Client Resource
- Director Storage Resource
- Job Resource

These are off the top of my head, and I may have missed one or two... But any one of these could be the cause and the status director will lead us to the cause, which might lead us to the next cause, and so on, until we open all the gates. :)

Could also be something like a disk Autochanger does not have enough devices available for all the concurrent jobs you are wanting to run concurrently.

Could also be that at some point, a Catalog job (default priority 11) enters the queue and it will wait until the priority 10 jobs finish, and then, any of the jobs for the smaller servers that enter the queue after this priority 11 job enters it, they will wait in line until that job finishes.

There is an "AllowMixedPriority" setting, but I don't like to play with that as it just adds more confusion and complexity to the equation.

Lots of places to look... Let's start with the status director when you enter 
this situation.


Best regards,
Bill

--
Bill Arlofski
w...@protonmail.com

Attachment: signature.asc
Description: OpenPGP digital signature

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

Reply via email to