This is a very common issue that must be looked at carefully, this will be a
large post and I apologize for it :P
Priority levels are very hard to manage/maintain since they can cause jobs to
block! Meaning if a job has network (or other) issues and the Bacula server
connection doesn't drop but
You can also set
Allow Mixed Priority = yes
on all your jobs.
From bacula docs:
Allow Mixed Priority = yesno
This directive is only implemented in version 2.5 and later.
When
set to yes (default no), this job may run even if lower priorit
Zitat von Troy Kocher :
> All,
>
> Recently I've made changes to my bacula-dir and bacula-sd to with
> the intent of running simultaneous jobs. After the changes my
> testing seems to indicate I still don't have it right. I launched
> my first job 'Image_Backup' manually with it's default
All,
Recently I've made changes to my bacula-dir and bacula-sd to with the intent of
running simultaneous jobs. After the changes my testing seems to indicate I
still don't have it right. I launched my first job 'Image_Backup' manually
with it's default priority, then launched the retail job
