Bacula-users

Re: [Bacula-users] How to prevent two clients to run at the same time

2009-06-26 05:30:06
Subject: Re: [Bacula-users] How to prevent two clients to run at the same time
From: Frank Altpeter <frank.altpeter AT gmail DOT com>
To: bacula-users AT lists.sourceforge DOT net
Date: Fri, 26 Jun 2009 11:24:07 +0200
Hi again,

2009/6/22 Frank Altpeter <frank.altpeter AT gmail DOT com>:
> 2009/6/22  <C.Keschnat AT internet-mit-iq DOT de>:
>> You could just give one server a lower priority. It would then run after all
>> other Jobs. The default is 10 (11 for the catalog), so Priority = 12 in the
>> Job Resource will make it run later.
>
> Hmm, this sounds indeed like a good idea. I just set up an additional
> Schedule definition for only these two clients, with priority set to
> 12 and 13, and will see if it's doing as expected on the next
> scheduled run. Thanks for the suggestion :)

After some testing different settings I'm quite confused with
Schedules and Priority settings. The current setting is defined with
two schedules. The first Schedule is run on 00:23 and contains the two
systems that are to be saved after each other. So they have got their
own schedule and each of them as another priority (as output by status
console):

Scheduled Jobs:
Level          Type     Pri  Scheduled          Name               Volume
===================================================================================
Incremental    Backup    11  27-Jun-09 00:23
hostname.domainname.tld hostname.domainname.tld-Default-0328
Incremental    Backup    12  27-Jun-09 00:23
secondhostname.domainname.tld
secondhostname.domainname.tld-Default-0331

The other 93 jobs are defined with a second schedule at 00:30 and priority 10.

Incremental    Backup    10  27-Jun-09 00:30    thirdhost.domain.tld
thirdhost.host.tld-Default-0806
Incremental    Backup    10  27-Jun-09 00:30    fourthhost.domain.tld
 fourthhost.domain.tld-Default-0081
[...]

I _thought_, that this should work when the low-prio jobs are started
before the default-prio jobs. But the reality is confusing me. My prio
11 job was finished at 00:27, and - as expected - the prio 12 job has
been started at 00:27. But, this job finished on 01:02, and all the
other prio 10 jobs - which should have been started by schedule on
00:30 - have been started at 01:02 ... and I don't have an idea why...



Le deagh dhùraghd,

       Frank Altpeter


There is no way to happiness. Happiness is the way.
   -- Buddha

------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>