Concurrent Jobs

The concurrent job runs can be managed by modifying the Maximum Concurrent Jobs in the Director’s configuration file (bacula-dir.conf) in the Director, Job, Client, and Storage resources.

Additionally the File daemon, and the Storage daemon each have their own Maximum Concurrent Jobs directive that sets the overall maximum number of concurrent jobs the daemon will run.

For example, if you want two different jobs to run simultaneously backing up the same Client to the same Storage device, they will run concurrently only if you have set Maximum Concurrent Jobs greater than one in the Director resource, the Client resource, and the Storage resource in bacula-dir.conf.

Below is a stripped down bacula-dir.conf file showing you the four places where the the file must be modified to allow the same job NightlySave to run up to four times concurrently. The change to the Job resource is not necessary if you want different Jobs to run at the same time, which is the normal case.

#
# Bacula Director Configuration file -- bacula-dir.conf
#
Director {
    Name = rufus-dir
    Maximum Concurrent Jobs = 4
    ...
}
Job {
    Name = "NightlySave"
    Maximum Concurrent Jobs = 4
    Client = rufus-fd
    Storage = File
    ...
}
Client {
    Name = rufus-fd
    Maximum Concurrent Jobs = 4
    ...
}
Storage {
    Name = File
    Maximum Concurrent Jobs = 4
    ...
}