Stephan Jennewein schrieb:

>>> thats what happen at the moment.
>>> increasing the 'maximum concurrent jobs' in the bacula-fd.conf would not
>>> fix the problem because the harddrive isn't faster just because i want to
>>> run more jobs parallel. so i only can parallelize if i can dynamically
>>> run jobs of different computers at the same time.
>> so, i don't know why it isn't working like you expect it.
> How do you schedule the jobs? I only have one schedule for each server so all 
> of the jobs of one server starts simultaneously. But I have much more than 3 
> jobs per computer so i don't think the schedule is the right way to go.

This is the schedule:

Schedule {
   Name = "WeeklyCycle"
   Run = Pool=Full Full 1st thu at 23:05
   Run = Pool=Diff Differential 2nd-5th thu at 23:05
   Run = Pool=Inc Incremental fri-wed at 23:05
}

JobDefs {
   ...
   Name = "DefaultJob"
   Schedule = "WeeklyCycle"
   ...
}

Job {
   ...
   JobDefs = "DefaultJob"
   ...
}


Job {
   ...
   JobDefs = "DefaultJob"
   ...
}

and so on.


> 
>> i've got 4 servers and they backup in parallel one job per server.
>>
>> bacula-dir.conf
>>    Director: "Maximum Concurrent Jobs" = 10
>>    Storage: "Maximum Concurrent Jobs" = 4
>>
>> Anyway you have set "Maximum Concurrent Jobs" in bacula-dir for
>> client4,5,7 as you want only start 1 job per computer?
> To what should I set the option for each client?

if you just want to start 1 job  at a time per client, i would not set
any specific value.

- Thomas



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users