Hello,
meanwhile I really tried to get it on my own, but looking at page 135 of Bacula Manual Version 1.38.5 just knocks me out.
On line one and two it says:
"...... all queued jobs of priority 1 will run before queued jobs of priority 2 and so on, regardless of the original scheduling order."
While in the last paragraph it says:
"If you have several jobs of different priority, it may not best to start
them at exactly the same time, because Bacula must examine them
one at a time. If by Bacula starts a lower priority job first, then it will
run before your high priority jobs. If you experience this problem, you
may avoid it by starting any higher priority jobs a few seconds before
lower priority ones. This insures that Bacula will examine the jobs in
the correct order, and that your priority scheme will be respected."
I assume the last paragraph applies regardless of jobs running concurrent or not. Is that right?
If yes:
For me, it sounds like the whole concept of priorities is obsolete and job order has to be managed all by schedules.
Right?
I mean if priorities are only respected correctly as long as jobs are started (by schedules) in the according order (because bacula needs to examine them in just this order to be able to respect those priorities correctly) - what do I need priorities for????
It all depends on the schedules then.
Or did I miss it completely?
Coming back to my original concern:
As a pro user I have, as mentioned before, backup-servers each controlling several streamers of the same type.
The amount of data per day is relatively high.
So I want to be finished with backups in the morning to service my users with restores if need be.
In other words I want the respective jobs go parallel on the streamers, not sequentially.
I think I understand why concurrent jobs are not recommended if going on only one streamer.
But this should be not a problem with two or more jobs each going on an extra streamer. Right?
Basically, can bacula manage that at all?
If yes, how should I enable it?
Has this, in my case, to do with "Maximum Concurrent Jobs" at all?
Can I leave "Maximum Concurrent Jobs = 1" in the Storage Resource of the director's conf? (see my configuration in original mail, please)
Take out priorities completely?
Give each job an own schedule and giving them intervals of, say, a minute?
Kind Regards,
i. A. Christoff Buch
=====================================
[EMAIL PROTECTED]
OneVision Software AG
Dr.-Leo-Ritter-Str. 9
93049 Regensburg
- Re: [Bacula-users] Running Jobs simultaneously on two strea... Christoff Buch
