Re: [Bacula-users] Running Jobs simultaneously on two streamers of same type - Sorry to come "back up" ;-) with this again

[Christoff Buch]

Mit freundlichem Gruß

i. A. Christoff Buch

=====================================
[EMAIL PROTECTED]
OneVision Software AG
Dr.-Leo-Ritter-Str. 9
93049 Regensburg

John Kodis <[EMAIL PROTECTED]> wrote on 30.03.2006
16:42:43:

> On Thu, Mar 30, 2006 at 04:21:59PM +0200, Christoff Buch wrote:
> 
> > 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????
> 
> The one thing that I use schedules for is taken directly from the
> example configuration: running a catalog backup immediately after
all
> the client backups have completed.  While jobs at the same priority
> seem to normally run in the order in which they get queued up, there's
> no guarantee of this.  There is such a guarantee with priorities.
> 
> -- John Kodis.
> 
Hi John,

Thanks for your reply!
So do you start your client jobs without
any schedules? How?
How can I determine the order jobs get
queued up? Is it the position in the bacula-dir.conf? (I don't wanna believe
I have to go down to this...)
Besides, I'm mainly concerned about
getting simultaneous jobs to run - and concerning this there's a problem
with priorities as you can see in my earlier mails.