Re: [Bacula-users] Jobs running twice?
On 7/1/10 9:29 AM, Jon Schewe wrote:
On 7/1/10 9:29 AM, John Drescher wrote:
On Thu, Jul 1, 2010 at 9:45 AM, Jon Schewe jpsch...@mtu.net wrote:
On 7/1/10 8:29 AM, John Drescher wrote:
On Thu, Jul 1, 2010 at 9:21 AM, Jon Schewe jpsch...@mtu.net wrote:
So I've got a job that takes over 48 hours to complete (I'm working on
fixing this), but in the meantime I have a second job scheduled to
happen daily writing to a different pool. 2 odd things happened:
1) The second job couldn't run at the same time as a long job. This
might be because bacula can't spool 2 jobs at once, or I've got to
change something for this.
Do you have more than 1 drive? Two different bacula volumes can not be
loaded in a single drive. And this does apply to disk volumes as well.
The log running job was going to disk, the daily job was going to tape.
Have you turned on concurrency? This is off by default. Remember when
turning on concurrency you may have to set Maximum concurrent Jobs
in 5 or more places.
No I haven't tried that. I'll look into that. Thanks.
I looked into the duplicate jobs options and according to the
documentation the default is to not allow duplicate jobs. So why am I
seeing duplicate jobs queued? In this case I have a copy to tape job:
Job {
Name = CopyToTape
Type = Copy
#Schedule = WeeklyCycleAfterBackup
Priority = 40 # after catalog
Pool = Disk-Pool
Maximum Concurrent Jobs = 1
Selection Type = PoolUncopiedJobs
Messages = Standard
Level = Full # ignored
Client = mn-server-fd # ignored
FileSet=Standard Full Set # ignored
}
If one of the copy jobs takes over 24 hours because of something like a
stuck autoloader then the same jobs are queued up again. Why are these
jobs queued up twice?
--
Jon Schewe | http://mtu.net/~jpschewe
If you see an attachment named signature.asc, this is my digital
signature. See http://www.gnupg.org for more information.
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Jobs running twice?
On Tuesday 06 July 2010 18:07:30 Bill Arlofski wrote: My only complaint about the Allow Duplicate Jobs option is that duplicates that are canceled are marked with a job exit status of Fatal Error, which triggers the Xymon Monitor Bacula check script I wrote. In other words, I'd like to see a different Job Exit Status for jobs that are canceled because they were a duplicate so that this additional status could be tested for and ignored or at least dealt with differently in my Xymon script - and also in webacula - which shows a default table of Jobs with errors - last 7 days in RED. Hello. I created a bug report for that, but it seems that there are some issues with changing it, so it seems it won't happen :( http://bugs.bacula.org/view.php?id=1507 -- Silver -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Jobs running twice?
On 07/06/10 08:01, Jon Schewe wrote: On 07/01/2010 10:04 AM, Bill Arlofski wrote: On 07/01/10 10:29, Jon Schewe wrote: Although the more annoying thing is question 2, any takers? 2) So while the long job was running the daily job was paused until the long job finished (as I explained in 1), the really annoying thing was that a second daily job was put in the schedule queue even though there was one already scheduled and waiting, so when the long job finished, each of my clients was backed up twice again inside of 6 hours, rather than the second daily job just being dropped (which I would have expected). Is there a way to change this behavior? Hi Jon... The option you are looking for in this case is Allow Duplicate Jobs = no so that when the second daily job is queued it will be prevented from starting. Thanks, why isn't this the default? Hi Jon Well, I am not the author, so I can't answer that directly, but I can say that from my experience with Bacula it is quite modular, and quite flexible such that it can be molded to fit just about any environment or configuration requirement. But with flexibility comes complexity and sometimes it can be difficult to find a specific option you are looking for - which is why this list is such an excellent resource. :) One person's idea of what should be default can be quite different from another's - but at least with Bacula you can change a variable to quickly suit your need and you're off. In the case of the Allow Duplicate Jobs option, others may actually want duplicate jobs to stack up and run consecutively - I can't imagine why either, but I am sure someone on this list will read this and give you/me a perfect example. :) My only complaint about the Allow Duplicate Jobs option is that duplicates that are canceled are marked with a job exit status of Fatal Error, which triggers the Xymon Monitor Bacula check script I wrote. In other words, I'd like to see a different Job Exit Status for jobs that are canceled because they were a duplicate so that this additional status could be tested for and ignored or at least dealt with differently in my Xymon script - and also in webacula - which shows a default table of Jobs with errors - last 7 days in RED. Cheers! -- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/ -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Jobs running twice?
So I've got a job that takes over 48 hours to complete (I'm working on fixing this), but in the meantime I have a second job scheduled to happen daily writing to a different pool. 2 odd things happened: 1) The second job couldn't run at the same time as a long job. This might be because bacula can't spool 2 jobs at once, or I've got to change something for this. 2) So while the long job was running the daily job was paused until the long job finished (as I explained in 1), the really annoying thing was that a second daily job was put in the schedule queue even though there was one already scheduled and waiting, so when the long job finished, each of my clients was backed up twice again inside of 6 hours, rather than the second daily job just being dropped (which I would have expected). Is there a way to change this behavior? -- Jon Schewe | http://mtu.net/~jpschewe If you see an attachment named signature.asc, this is my digital signature. See http://www.gnupg.org for more information. -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Jobs running twice?
On Thursday 01 July 2010 03:21:23 pm Jon Schewe wrote: So I've got a job that takes over 48 hours to complete (I'm working on fixing this), but in the meantime I have a second job scheduled to happen daily writing to a different pool. 2 odd things happened: 1) The second job couldn't run at the same time as a long job. This might be because bacula can't spool 2 jobs at once, or I've got to change something for this. A device can only handle one volume at a time, even if you write to disk. Maybe the jobs on hold using a different volume have been set to the same device? 2) So while the long job was running the daily job was paused until the long job finished (as I explained in 1), the really annoying thing was that a second daily job was put in the schedule queue even though there was one already scheduled and waiting, so when the long job finished, each of my clients was backed up twice again inside of 6 hours, rather than the second daily job just being dropped (which I would have expected). Is there a way to change this behavior? Machiel. -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Jobs running twice?
On 7/1/10 8:29 AM, John Drescher wrote: On Thu, Jul 1, 2010 at 9:21 AM, Jon Schewe jpsch...@mtu.net wrote: So I've got a job that takes over 48 hours to complete (I'm working on fixing this), but in the meantime I have a second job scheduled to happen daily writing to a different pool. 2 odd things happened: 1) The second job couldn't run at the same time as a long job. This might be because bacula can't spool 2 jobs at once, or I've got to change something for this. Do you have more than 1 drive? Two different bacula volumes can not be loaded in a single drive. And this does apply to disk volumes as well. The log running job was going to disk, the daily job was going to tape. -- Jon Schewe | http://mtu.net/~jpschewe If you see an attachment named signature.asc, this is my digital signature. See http://www.gnupg.org for more information. -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Jobs running twice?
On Thu, Jul 1, 2010 at 9:21 AM, Jon Schewe jpsch...@mtu.net wrote: So I've got a job that takes over 48 hours to complete (I'm working on fixing this), but in the meantime I have a second job scheduled to happen daily writing to a different pool. 2 odd things happened: 1) The second job couldn't run at the same time as a long job. This might be because bacula can't spool 2 jobs at once, or I've got to change something for this. Do you have more than 1 drive? Two different bacula volumes can not be loaded in a single drive. And this does apply to disk volumes as well. I will leave out the other question because I do not know the answer.. John -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Jobs running twice?
On Thu, Jul 1, 2010 at 9:45 AM, Jon Schewe jpsch...@mtu.net wrote: On 7/1/10 8:29 AM, John Drescher wrote: On Thu, Jul 1, 2010 at 9:21 AM, Jon Schewe jpsch...@mtu.net wrote: So I've got a job that takes over 48 hours to complete (I'm working on fixing this), but in the meantime I have a second job scheduled to happen daily writing to a different pool. 2 odd things happened: 1) The second job couldn't run at the same time as a long job. This might be because bacula can't spool 2 jobs at once, or I've got to change something for this. Do you have more than 1 drive? Two different bacula volumes can not be loaded in a single drive. And this does apply to disk volumes as well. The log running job was going to disk, the daily job was going to tape. Have you turned on concurrency? This is off by default. Remember when turning on concurrency you may have to set Maximum concurrent Jobs in 5 or more places. John -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Jobs running twice?
On 7/1/10 9:29 AM, John Drescher wrote: On Thu, Jul 1, 2010 at 9:45 AM, Jon Schewe jpsch...@mtu.net wrote: On 7/1/10 8:29 AM, John Drescher wrote: On Thu, Jul 1, 2010 at 9:21 AM, Jon Schewe jpsch...@mtu.net wrote: So I've got a job that takes over 48 hours to complete (I'm working on fixing this), but in the meantime I have a second job scheduled to happen daily writing to a different pool. 2 odd things happened: 1) The second job couldn't run at the same time as a long job. This might be because bacula can't spool 2 jobs at once, or I've got to change something for this. Do you have more than 1 drive? Two different bacula volumes can not be loaded in a single drive. And this does apply to disk volumes as well. The log running job was going to disk, the daily job was going to tape. Have you turned on concurrency? This is off by default. Remember when turning on concurrency you may have to set Maximum concurrent Jobs in 5 or more places. No I haven't tried that. I'll look into that. Thanks. Although the more annoying thing is question 2, any takers? -- Jon Schewe | http://mtu.net/~jpschewe If you see an attachment named signature.asc, this is my digital signature. See http://www.gnupg.org for more information. -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Jobs running twice?
On Thu, Jul 1, 2010 at 10:29 AM, John Drescher dresche...@gmail.com wrote: On Thu, Jul 1, 2010 at 9:45 AM, Jon Schewe jpsch...@mtu.net wrote: On 7/1/10 8:29 AM, John Drescher wrote: On Thu, Jul 1, 2010 at 9:21 AM, Jon Schewe jpsch...@mtu.net wrote: So I've got a job that takes over 48 hours to complete (I'm working on fixing this), but in the meantime I have a second job scheduled to happen daily writing to a different pool. 2 odd things happened: 1) The second job couldn't run at the same time as a long job. This might be because bacula can't spool 2 jobs at once, or I've got to change something for this. Do you have more than 1 drive? Two different bacula volumes can not be loaded in a single drive. And this does apply to disk volumes as well. The log running job was going to disk, the daily job was going to tape. Have you turned on concurrency? This is off by default. Remember when turning on concurrency you may have to set Maximum concurrent Jobs in 5 or more places. If you have concurrency properly setup. Are your jobs at different priorities. If so then they will not run concurrently. John -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Jobs running twice?
On 07/01/10 10:29, Jon Schewe wrote: Although the more annoying thing is question 2, any takers? 2) So while the long job was running the daily job was paused until the long job finished (as I explained in 1), the really annoying thing was that a second daily job was put in the schedule queue even though there was one already scheduled and waiting, so when the long job finished, each of my clients was backed up twice again inside of 6 hours, rather than the second daily job just being dropped (which I would have expected). Is there a way to change this behavior? Hi Jon... The option you are looking for in this case is Allow Duplicate Jobs = no so that when the second daily job is queued it will be prevented from starting. -- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/ -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
