Hi, as far as I understand from the manual, bacula does not run any high priority job while a job with a different priority is running. So if bacula is running a prio 10 job it will not start a prio 1 job in any circumstance.
I have many short jobs (ca. 10 Minutes up to 1 Hour) and 2 or 3 very long jobs (up to 3 days). This is because we have to transfer a big database to an archive location over small bandwidth. In this situation it is impossible to build jobs with different priorities because when the long term job is running no other job will start beside jobs with the same priority. So using different priorities is useless in this situation. Is there any reason why bacula does not start any higher prioritized job or s there a workaround? Regards, Michael ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
