[Bacula-users] Why does Bacula run Disk jobs before previously queued Ta

Dear All,
     I am using Bacula 5.0.3 on Solaris 10_x86. I am currently having an issue where sometimes Tape jobs are hung in queue waiting for Disk jobs to complete. I realize this is a factor of the Concurrent Jobs setting. However, Bacula seems to continue processing Disk jobs that were scheduled AFTER some Tape jobs, causing even further delays in completing tape jobs. During this time, the drive is not in use. Also, I have not modified Job Priorities in any way from defaults.
     Does Bacula assign a higher priority to Disk jobs? The fact that Bacula runs Disk jobs, queued after Tape jobs, before those jobs is troubling to me. Also, the tape drive sitting for hours unused while Disk jobs is causing major delays in my backup scheduling. Any ideas on why this is happening would be very helpful.
     I've considered running a second SD on the host, just to control and queue jobs for the Tape drive. Is this a valid or recommended option?

Sincerely,
Shon

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d

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

[Bacula-users] Why does Bacula run Disk jobs before previously queued Tape Jobs?