Stephan Jennewein schrieb:
> Hi Thomas,
> 
>> maybe:
>> a) change the priorities of the jobs. the jobs that should run togheter
>> should get the same priority. Remember: different priorities can't run
>> concurrent.
> This could be a solution, but isn't there anything more automatic because I 
> will get a lot of jobs in the nearer future so I have to choose for each job 
> which priority I want. As I thought priority should reflect the importance of 
> the backup of a computer than to loadbalance.
> 
>> b) change the "Maximum Concurrent Jobs" in the Client section of
>> bacula-dir.conf to 1 (or whatever you like)
> I don't think this would work because the second job is waiting for the first 
> one. That's what happening at the moment.

hmm.. i understood, that you want to have only one job per 
client/machine run at one time. but after rereading i see that isn't 
what you like to achiev. so you want to start at least 2 jobs per pc at 
a time?

post your "Maximum Concurrent Jobs" definitions in bacula-dir.conf (in 
resources director,client,storage and job), bacula-fd.conf  and 
bacula-sd.conf to see if it's correct allover the different places. And 
if you use "Maximum Volume Jobs" also post that.

- 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