Re: [Bacula-users] stuck job blocks all queue
Daniel De Marco wrote: > * Dan Langille [01/13/2010 20:03]: >> I think you need to read up on 'concurrent jobs'. >> "If you want to run concurrent jobs you should keep these points in mind: >> * See Running Concurrent Jobs on how to setup concurrent jobs. >> * Bacula concurrently runs jobs of only one priority at a time. It >> will not simultaneously run a priority 1 and a priority 2 job. " > > I see, I tought that since the first job was stuck it wouldn't block the > queue and the above would not apply, but thinking about it, it makes sense. > > So it is not possible to have a workaround or a different configuration > so that a stuck job would not block the queue?? *cough* I'm pretty sure you answered your own question. -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] stuck job blocks all queue
* Dan Langille [01/13/2010 20:03]: > I think you need to read up on 'concurrent jobs'. > "If you want to run concurrent jobs you should keep these points in mind: > * See Running Concurrent Jobs on how to setup concurrent jobs. > * Bacula concurrently runs jobs of only one priority at a time. It > will not simultaneously run a priority 1 and a priority 2 job. " I see, I tought that since the first job was stuck it wouldn't block the queue and the above would not apply, but thinking about it, it makes sense. So it is not possible to have a workaround or a different configuration so that a stuck job would not block the queue?? Thanks, Daniel. -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] stuck job blocks all queue
Daniel De Marco wrote: > Hi, > > I have a weird configuration problem with bacula (3.0.2). I looked > through the manual, the faq and the mailing list archives, but my > searches couldn't come up with any relevant info. > > If one of the jobs in my queue gets stuck "waiting for an appendable > volume" all the jobs after that one are blocked and do not run until I > label a new volume for the original job. This happens even if the jobs > have different Pools, Storage, Storage devices and Storage Media Type. > I was expecting the original job to get stuck, but for the others to > continue unaffected. > > Here's one example: > 17544 FullBK-wakko.2010-01-13_17.27.09_03 is waiting for an appendable > Volume > 17545 Increme BK-mailserver.2010-01-13_17.28.09_04 is waiting for higher > priority jobs to finish > > BK-mailserver (priority = 8) is waiting for BK-wakko (priority = 10) to > be completed even if it should be possible for it to proceed. > Is there any way to achieve this behaviour? I think you need to read up on 'concurrent jobs'. http://www.bacula.org/en/rel-manual/Configuring_Director.html#SECTION00143 "If you want to run concurrent jobs you should keep these points in mind: * See Running Concurrent Jobs on how to setup concurrent jobs. * Bacula concurrently runs jobs of only one priority at a time. It will not simultaneously run a priority 1 and a priority 2 job. " -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] stuck job blocks all queue
Hi, I have a weird configuration problem with bacula (3.0.2). I looked through the manual, the faq and the mailing list archives, but my searches couldn't come up with any relevant info. If one of the jobs in my queue gets stuck "waiting for an appendable volume" all the jobs after that one are blocked and do not run until I label a new volume for the original job. This happens even if the jobs have different Pools, Storage, Storage devices and Storage Media Type. I was expecting the original job to get stuck, but for the others to continue unaffected. Here's one example: 17544 FullBK-wakko.2010-01-13_17.27.09_03 is waiting for an appendable Volume 17545 Increme BK-mailserver.2010-01-13_17.28.09_04 is waiting for higher priority jobs to finish BK-mailserver (priority = 8) is waiting for BK-wakko (priority = 10) to be completed even if it should be possible for it to proceed. Is there any way to achieve this behaviour? Thank you, Daniel. -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
