After watching it run now for a few days, it definitely appears to not be 
starting new jobs until all of the jobs running on the sd finish. Is this how 
it is supposed to work?


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Blake Dunlap
Sent: Saturday, December 01, 2007 1:20 AM
To: 'bacula-users@lists.sourceforge.net'
Subject: [Bacula-users] Issue with conncurrent jobs

I seem to be having some scheduling quirks on my director right now. It doesn't 
seem to be correctly queuing new jobs to the store as they drop off. I am 
currently waiting on the last running job on the store to finish to see if it 
even correctly adds more jobs once that does drop.

Example:

Running Jobs:
 JobId Level   Name                       Status
======================================================================
  5574 Full    WeeklyOffsite-filemonster.2007-11-30_19.05.00 has terminated
  5580 Full    WeeklyOffsite-bnawsvmsx04.bna01.isdn.net.2007-11-30_19.05.06 has 
terminated
  5587 Full    WeeklyOffsite-nrepwsvfs01.bna01.isdn.net.2007-11-30_19.05.13 is 
running
  5588 Full    WeeklyOffsite-bnaw2ksql01.bna01.isdn.net.2007-11-30_19.05.14 is 
waiting on max Storage jobs
  5589 Full    WeeklyOffsite-rex2.2007-11-30_19.05.15 is waiting on max Storage 
jobs
  5590 Full    WeeklyOffsite-web05.2007-11-30_19.05.16 is waiting on max 
Storage jobs

Running Jobs:
 JobId Level   Name                       Status
======================================================================
  5587 Full    WeeklyOffsite-nrepwsvfs01.bna01.isdn.net.2007-11-30_19.05.13 is 
running
  5588 Full    WeeklyOffsite-bnaw2ksql01.bna01.isdn.net.2007-11-30_19.05.14 is 
waiting on max Storage jobs
  5589 Full    WeeklyOffsite-rex2.2007-11-30_19.05.15 is waiting on max Storage 
jobs
  5590 Full    WeeklyOffsite-web05.2007-11-30_19.05.16 is waiting on max 
Storage jobs
  5591 Full    WeeklyOffsite-bnaw2ksql02.2007-11-30_19.05.17 is waiting on max 
Storage jobs
  5592 Full    WeeklyOffsite-nashlog01.2007-11-30_19.05.18 is waiting on max 
Storage jobs


But the director correctly sees that there should be 5 concurrent allowed by 
the store, and when it first starts backups, it does indeed start 5, and has 
worked fine in the past. Perhaps something on my end, or a bug introduced 
somewhere around the last two minor releases (I'm running 2.2.6)?

*show storage
Storage: name=nrepbak-sd address=172.30.0.1 SDport=9103 MaxJobs=5
      DeviceName=Autochanger MediaType=LTO2 StorageId=2


-Blake


-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to