On 08/23/10 15:53, Proskurin Kirill wrote:
> 23.08.2010 20:05, Phil Stracchino пишет:
>> On 08/23/10 07:05, Proskurin Kirill wrote:
>>> Hello.
>>>
>>> What we have:
>>> FreeBSD-8.0
>>> Bacula-5.0.2
>>>
>>> Backup on HDD. Every Job have they own pool and own storage.
>>>
>>> Most confusing thing in bacula after retention policy is a concurrency.
>>> What I need to do to make jobs not wait for previous to end? Priority is
>>> now work here.
>>
>> I'm sorry, your question is unclear. When you say "make jobs not wait
>> for previous to end", what exactly do you mean? Do you mean that only
>> one job is running at a time?
>
> Sorry for that.
>
> Real example:
> 1) 4 jobs start in one time with priority 10 - all them work at once
> concurent - all ok.
> 2) Then start jobs with priority 11 and it is take long time to end.
OK, that part is easy enough; no priority 11 job will start while a job
of priority 10 or lower is running.
> 3) In the middle of that job started another job with priority 10 and
> this job is wait previous to end.
You need this directive:
--------------
Allow Mixed Priority = yes/no
This directive is only implemented in version 2.5 and later. When
set to yes (default no), this job may run even if lower priority jobs
are already running. This means a high priority job will not have to
wait for other jobs to finish before starting. The scheduler will only
mix priorities when all running jobs have this set to true.
Note that only higher priority jobs will start early. Suppose the
director will allow two concurrent jobs, and that two jobs with priority
10 are running, with two more in the queue. If a job with priority 5 is
added to the queue, it will be run as soon as one of the running jobs
finishes. However, new priority 10 jobs will not be run until the
priority 5 job has finished.
--------------
Under the default behavior (Allow Mixed Priority = no), lower priority
(i.e, larger priority number) jobs cannot start while a higher priority
job is running, but ALSO, NEW higher priority jobs cannot start while a
lower priority job is running. You want to set this to Allow Mixed
Priority = yes, which will allow higher priority jobs to start
immediately, while still not allowing new low priority jobs to start
while a higher priority job is running.
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
ala...@caerllewys.net ala...@metrocast.net p...@co.ordinate.org
Renaissance Man, Unix ronin, Perl hacker, Free Stater
It's not the years, it's the mileage.
------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of special opportunities to increase revenue and
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
