On 2012-11-29 08:18, Silver Salonen wrote:
> On Thursday 29 November 2012 07:58:23 Dan Langille wrote:
>> On 2012-11-29 07:02, Silver Salonen wrote:
>> > Hi.
>> > I'm backing up some servers with multiple Bacula directors.
>> > Although I've set "Maximum Concurrent Jobs = 10" in FD's
>> > configuration,
>> You also have to look at the SD and Dir 'maximum concurrent jobs'
>> settings as well.
> I have this kind of setup:
> sd1<--dir1 -------> client1 <------- dir2-->sd2
> At 23:05 dir1 contacts client1 and starts some job, backing up to
> At 23:05 dir2 contacts client1 and starts some job, backing up to
> As both directors and storages are separate, SD and DIR 'maximum
> concurrent jobs' settings don't matter here.
> Anyhow, this setting on all these components is set to 99 :)
OK, so both jobs are running on the FD. Concurrently.
Thus, the problem, must be the SD. Let's look below..
>> > it seems that these multiple directors cannot run jobs
>> > concurrently - when one is waiting for a new volume or something,
>> > other just keeps waiting.
NOTE: You mention DIR, but 'waiting for a volume' is an SD thing, not a
That is, the SD is waiting for a new volume.
Let's assume you are backing up to disk.
Is the SD set to automatically create/label Volumes?
The output from status storage would be useful here. As would the
of Bacula you are using (SD, DIR, FD).
>> It is not clear what you are doing. Let's try a simple explanation.
>> You have an FD. You have N Bacula Directors. You want that FD to
>> N jobs concurrently, each backing up to a different SD.
>> Is that description accurate?
>> > Anyone has a clue why is that?
>> Not yet.
Dan Langille - http://langille.org/