On Tue, 2011-07-05 at 09:03 +0200, Uwe Mohn wrote:
> I'd suggest using different prioritys for your virtual fulls since
> bacula won't start a job with a higher bacula priority (means lesser
> importance)
> before a job with a lower bacula priority (means higher importance) has
> terminated. For
Hello,
usually I do not have problem with concurrent jobs, because they
read/write from/to different pools. But when it comes to virtual full
backups I need to stop bacula from doing these jobs concurrently.
Is there a way to tell the bacula to do a certain type of job one at a
time even if the c
