Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
Sorry to raise this one again, but I was bitten by this one recently, and found Stephen Thompson's comments hit the nail right on the head. >>... but it goes both >>ways, it also cancels my fulls if an incremental is already running or >>scheduled. It's the scheduled part that causes me problems. I have >>incrementals scheduled to run every day. Yes, the Full got cancelled in favour of an Incremental! >> This might work out if all jobs have static (i.e. >>based on configuration files) schedules, but rather than controlling >>duplicates, it seems better at preventing administrator intervention >>which is frustrating. My schedules are static. Wouldn't it make more sense for 'Allow Higher Duplicates' to refer to a higher Level rather than a higher Priority? Anyway, looks like I have to run a couple of manual Full backups now, and remain vigilant for next time. Ken Barclay >> >>I recognize I might have a unique situation (dynamically scheduling >>fulls based on availability rather than a regular calendar cycle) which >>is fine; I'll probably have to pull my incremental scheduling out of >>bacula and cron the injection of jobs via a script. But to me, there >>is >>still a design issue with considering a scheduled job to be in >>duplicate >>conflict with a running job; it seems like it would make more sense to >>only apply that logic in the running queue (whether actually running or >>waiting for resources). Then "canceled queued duplicates" would cancel >>any job that attempted to enter the running state if another job was >>already running. As it is now, it appears to cancel any job entering >>the running state even if another job is merely scheduled to run at >>some >>point in the future. Cancellations should happen on conflict, not on >>suspicion that conflict might arise in the future. >> >>But perhaps that's being too philosophical. :) >> >>Stephen >> >> >> >> >> >>Silver Salonen wrote: >>> On Tuesday 15 September 2009 17:36:25 Stephen Thompson wrote: Silver Salonen wrote: > Actually, you can do it - "Allow Higher Duplicates" really means >>ANY > duplicate job, not only a higher one. I just tested it and an >>incremental > job is cancelled if either full or incremental instance of the same >>job > is still running. > > So in my case "Allow Higher Duplicates" did the trick :) Really? This is exactly what I want and what I tried for when 3.x was first released, but my experiments showed that nothing was canceled. The >>jobs rather began running concurrently. I'll try this again. Are you saying to set Allow Higher Duplicates >>to Yes or No? Actually, could you possibly list what you have all the relevant values set to? I would most appreciate it. thanks, Stephen >>> >>> Yeah, I was positively surprised today too :) >>> >>> I have just one option in every JobDefs for that: >>> Allow Higher Duplicates = no >>> >> >> >>-- >>Stephen Thompson Berkeley Seismological Laboratory >>step...@seismo.berkeley.edu215 McCone Hall # 4760 >>404.538.7077 (phone) University of California, Berkeley >>510.643.5811 (fax) Berkeley, CA 94720-4760 >> >>--- >>--- >>Come build with us! The BlackBerry® Developer Conference in SF, CA >>is the only developer event you need to attend this year. Jumpstart >>your >>developing skills, take BlackBerry mobile applications to market and >>stay >>ahead of the curve. Join us from November 9-12, 2009. Register >>now! >>http://p.sf.net/sfu/devconf >>___ >>Bacula-users mailing list >>Bacula-users@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/bacula-users -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
I now discovered a downside of this: cancelled duplicate jobs cause the level to be ran again if "Rerun Failed Levels = yes". And we're back where we started. Frustrating, hysterically funny, depressing. Does it seem like a bug to anyone? I guess I'll have to keep using my check-job.sh script. -- Silver On Tuesday 15 September 2009 13:57:07 Silver Salonen wrote: > Actually, you can do it - "Allow Higher Duplicates" really means ANY > duplicate job, not only a higher one. I just tested it and an incremental > job is cancelled if either full or incremental instance of the same job is > still running. > > So in my case "Allow Higher Duplicates" did the trick :) > > > Hello, > > > > This works as reported for me as well, however, what I want to have in > > the first case is for the originally scheduled job to be canceled, not > > the duplicate. The reason being that my incrementals fall into a daily > > schedule, whereas my fulls are scheduled out-of-band, so I want the > > incremental to be canceled on the day that a full is scheduled. > > > > Given what you all say below, this doesn't seem possible with bacula's > > Duplicate Job Control. Correct? > > > > thanks! > > Stephen > > > > Silver Salonen wrote: > > > On Monday 14 September 2009 15:59:24 Bram Vandoren wrote: > > >> Hi All, > > >> > > >> Silver Salonen wrote: > > >>> Hmm, I guess not then. But it has been reported several times in the > > >>> list. So, any volunteers? :) > > >> > > >> This configuration: > > >> Allow Higher Duplicates = no > > >> Cancel Queued Duplicates = yes > > >> > > >> Seems to work fine in my situation (some more testing is needed). It > > >> cancels the newly created duplicate job immediately. > > >> > > >> This configuration: > > >> Allow Higher Duplicates = no > > >> Cancel Running Duplicates = yes > > >> cancels the running job and starts the same one. If you have a job > > >> that takes more than 24h to complete a runs daily, it will never > > >> finish. > > >> > > >> Hope it helps. > > >> > > >> When I find some try I will reopen the bug report. > > >> > > >> Cheers, > > >> Bram. > > > > > > I'll try that on my servers with a few hundred jobs and report about it > > > tomorrow :) > > > > > > But as default options are "Cancel Queued Duplicates = yes" and "Cancel > > > Running Duplicates = no", the only needed option seems to be "Allow > > > Higher Duplicates = no". I myself had set "Allow Duplicate Jobs = no", > > > because I thought it includes "Allow Higher Duplicates = no" too. > > > Whether the one option helps or not, I'll tell tomorrow. -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
Ah, thanks for the info, but this still is not the behavior that I am looking for. This does indeed cancel incrementals if a full is already running (actually even if a full is merely scheduled), but it goes both ways, it also cancels my fulls if an incremental is already running or scheduled. It's the scheduled part that causes me problems. I have incrementals scheduled to run every day. I then interject full jobs each day based on a script that determines which of my hosts are available for a full that day. This configuration immediately cancels my fulls, rather than letting them run and then canceling the corresponding incrementals when they are actually launched. This might work out if all jobs have static (i.e. based on configuration files) schedules, but rather than controlling duplicates, it seems better at preventing administrator intervention which is frustrating. I recognize I might have a unique situation (dynamically scheduling fulls based on availability rather than a regular calendar cycle) which is fine; I'll probably have to pull my incremental scheduling out of bacula and cron the injection of jobs via a script. But to me, there is still a design issue with considering a scheduled job to be in duplicate conflict with a running job; it seems like it would make more sense to only apply that logic in the running queue (whether actually running or waiting for resources). Then "canceled queued duplicates" would cancel any job that attempted to enter the running state if another job was already running. As it is now, it appears to cancel any job entering the running state even if another job is merely scheduled to run at some point in the future. Cancellations should happen on conflict, not on suspicion that conflict might arise in the future. But perhaps that's being too philosophical. :) Stephen Silver Salonen wrote: > On Tuesday 15 September 2009 17:36:25 Stephen Thompson wrote: >> Silver Salonen wrote: >>> Actually, you can do it - "Allow Higher Duplicates" really means ANY >>> duplicate job, not only a higher one. I just tested it and an incremental >>> job is cancelled if either full or incremental instance of the same job >>> is still running. >>> >>> So in my case "Allow Higher Duplicates" did the trick :) >> Really? >> >> This is exactly what I want and what I tried for when 3.x was first >> released, but my experiments showed that nothing was canceled. The jobs >> rather began running concurrently. >> >> I'll try this again. Are you saying to set Allow Higher Duplicates to >> Yes or No? Actually, could you possibly list what you have all the >> relevant values set to? I would most appreciate it. >> >> thanks, >> Stephen > > Yeah, I was positively surprised today too :) > > I have just one option in every JobDefs for that: > Allow Higher Duplicates = no > -- Stephen Thompson Berkeley Seismological Laboratory step...@seismo.berkeley.edu215 McCone Hall # 4760 404.538.7077 (phone) University of California, Berkeley 510.643.5811 (fax) Berkeley, CA 94720-4760 -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
On Tuesday 15 September 2009 17:36:25 Stephen Thompson wrote: > Silver Salonen wrote: > > Actually, you can do it - "Allow Higher Duplicates" really means ANY > > duplicate job, not only a higher one. I just tested it and an incremental > > job is cancelled if either full or incremental instance of the same job > > is still running. > > > > So in my case "Allow Higher Duplicates" did the trick :) > > Really? > > This is exactly what I want and what I tried for when 3.x was first > released, but my experiments showed that nothing was canceled. The jobs > rather began running concurrently. > > I'll try this again. Are you saying to set Allow Higher Duplicates to > Yes or No? Actually, could you possibly list what you have all the > relevant values set to? I would most appreciate it. > > thanks, > Stephen Yeah, I was positively surprised today too :) I have just one option in every JobDefs for that: Allow Higher Duplicates = no -- Silver -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
Silver Salonen wrote: > Actually, you can do it - "Allow Higher Duplicates" really means ANY > duplicate > job, not only a higher one. I just tested it and an incremental job is > cancelled if either full or incremental instance of the same job is still > running. > > So in my case "Allow Higher Duplicates" did the trick :) > Really? This is exactly what I want and what I tried for when 3.x was first released, but my experiments showed that nothing was canceled. The jobs rather began running concurrently. I'll try this again. Are you saying to set Allow Higher Duplicates to Yes or No? Actually, could you possibly list what you have all the relevant values set to? I would most appreciate it. thanks, Stephen -- Stephen Thompson Berkeley Seismological Laboratory step...@seismo.berkeley.edu215 McCone Hall # 4760 404.538.7077 (phone) University of California, Berkeley 510.643.5811 (fax) Berkeley, CA 94720-4760 -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
Actually, you can do it - "Allow Higher Duplicates" really means ANY duplicate job, not only a higher one. I just tested it and an incremental job is cancelled if either full or incremental instance of the same job is still running. So in my case "Allow Higher Duplicates" did the trick :) -- Silver On Tuesday 15 September 2009 00:04:45 Stephen Thompson wrote: > Hello, > > This works as reported for me as well, however, what I want to have in > the first case is for the originally scheduled job to be canceled, not > the duplicate. The reason being that my incrementals fall into a daily > schedule, whereas my fulls are scheduled out-of-band, so I want the > incremental to be canceled on the day that a full is scheduled. > > Given what you all say below, this doesn't seem possible with bacula's > Duplicate Job Control. Correct? > > thanks! > Stephen > > Silver Salonen wrote: > > On Monday 14 September 2009 15:59:24 Bram Vandoren wrote: > >> Hi All, > >> > >> Silver Salonen wrote: > >>> Hmm, I guess not then. But it has been reported several times in the > >>> list. So, any volunteers? :) > >> > >> This configuration: > >> Allow Higher Duplicates = no > >> Cancel Queued Duplicates = yes > >> > >> Seems to work fine in my situation (some more testing is needed). It > >> cancels the newly created duplicate job immediately. > >> > >> This configuration: > >> Allow Higher Duplicates = no > >> Cancel Running Duplicates = yes > >> cancels the running job and starts the same one. If you have a job that > >> takes more than 24h to complete a runs daily, it will never finish. > >> > >> Hope it helps. > >> > >> When I find some try I will reopen the bug report. > >> > >> Cheers, > >> Bram. > > > > I'll try that on my servers with a few hundred jobs and report about it > > tomorrow :) > > > > But as default options are "Cancel Queued Duplicates = yes" and "Cancel > > Running Duplicates = no", the only needed option seems to be "Allow > > Higher Duplicates = no". I myself had set "Allow Duplicate Jobs = no", > > because I thought it includes "Allow Higher Duplicates = no" too. > > Whether the one option helps or not, I'll tell tomorrow. -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
Hi Stephen, Perhaps it's possible with this configuration: >>> Allow Higher Duplicates = no >>> Cancel Running Duplicates = yes You can also try to change the Schedule to avoid incremental backups starting when full backups are running. It costs a more complicated schedule resource but it's much better tested/documented. Cheers, Bram. Stephen Thompson wrote: > > Hello, > > This works as reported for me as well, however, what I want to have in > the first case is for the originally scheduled job to be canceled, not > the duplicate. The reason being that my incrementals fall into a daily > schedule, whereas my fulls are scheduled out-of-band, so I want the > incremental to be canceled on the day that a full is scheduled. > > Given what you all say below, this doesn't seem possible with bacula's > Duplicate Job Control. Correct? > > thanks! > Stephen > > > Silver Salonen wrote: >> On Monday 14 September 2009 15:59:24 Bram Vandoren wrote: >>> Hi All, >>> >>> Silver Salonen wrote: Hmm, I guess not then. But it has been reported several times in the list. So, any volunteers? :) >>> This configuration: >>> Allow Higher Duplicates = no >>> Cancel Queued Duplicates = yes >>> >>> Seems to work fine in my situation (some more testing is needed). It >>> cancels the newly created duplicate job immediately. >>> >>> This configuration: >>> Allow Higher Duplicates = no >>> Cancel Running Duplicates = yes >>> cancels the running job and starts the same one. If you have a job that >>> takes more than 24h to complete a runs daily, it will never finish. >>> >>> Hope it helps. >>> >>> When I find some try I will reopen the bug report. >>> >>> Cheers, >>> Bram. >> >> I'll try that on my servers with a few hundred jobs and report about >> it tomorrow :) >> >> But as default options are "Cancel Queued Duplicates = yes" and >> "Cancel Running Duplicates = no", the only needed option seems to be >> "Allow Higher Duplicates = no". I myself had set "Allow Duplicate Jobs >> = no", because I thought it includes "Allow Higher Duplicates = no" >> too. Whether the one option helps or not, I'll tell tomorrow. >> > > -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
Hello, This works as reported for me as well, however, what I want to have in the first case is for the originally scheduled job to be canceled, not the duplicate. The reason being that my incrementals fall into a daily schedule, whereas my fulls are scheduled out-of-band, so I want the incremental to be canceled on the day that a full is scheduled. Given what you all say below, this doesn't seem possible with bacula's Duplicate Job Control. Correct? thanks! Stephen Silver Salonen wrote: > On Monday 14 September 2009 15:59:24 Bram Vandoren wrote: >> Hi All, >> >> Silver Salonen wrote: >>> Hmm, I guess not then. But it has been reported several times in the >>> list. So, any volunteers? :) >> This configuration: >> Allow Higher Duplicates = no >> Cancel Queued Duplicates = yes >> >> Seems to work fine in my situation (some more testing is needed). It >> cancels the newly created duplicate job immediately. >> >> This configuration: >> Allow Higher Duplicates = no >> Cancel Running Duplicates = yes >> cancels the running job and starts the same one. If you have a job that >> takes more than 24h to complete a runs daily, it will never finish. >> >> Hope it helps. >> >> When I find some try I will reopen the bug report. >> >> Cheers, >> Bram. > > I'll try that on my servers with a few hundred jobs and report about it > tomorrow :) > > But as default options are "Cancel Queued Duplicates = yes" and "Cancel > Running Duplicates = no", the only needed option seems to be "Allow Higher > Duplicates = no". I myself had set "Allow Duplicate Jobs = no", because I > thought it includes "Allow Higher Duplicates = no" too. Whether the one > option helps or not, I'll tell tomorrow. > -- Stephen Thompson Berkeley Seismological Laboratory step...@seismo.berkeley.edu215 McCone Hall # 4760 404.538.7077 (phone) University of California, Berkeley 510.643.5811 (fax) Berkeley, CA 94720-4760 -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
On Monday 14 September 2009 15:59:24 Bram Vandoren wrote: > Hi All, > > Silver Salonen wrote: > > Hmm, I guess not then. But it has been reported several times in the > > list. So, any volunteers? :) > > This configuration: > Allow Higher Duplicates = no > Cancel Queued Duplicates = yes > > Seems to work fine in my situation (some more testing is needed). It > cancels the newly created duplicate job immediately. > > This configuration: > Allow Higher Duplicates = no > Cancel Running Duplicates = yes > cancels the running job and starts the same one. If you have a job that > takes more than 24h to complete a runs daily, it will never finish. > > Hope it helps. > > When I find some try I will reopen the bug report. > > Cheers, > Bram. I'll try that on my servers with a few hundred jobs and report about it tomorrow :) But as default options are "Cancel Queued Duplicates = yes" and "Cancel Running Duplicates = no", the only needed option seems to be "Allow Higher Duplicates = no". I myself had set "Allow Duplicate Jobs = no", because I thought it includes "Allow Higher Duplicates = no" too. Whether the one option helps or not, I'll tell tomorrow. -- Silver -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
Hi All, Silver Salonen wrote: > Hmm, I guess not then. But it has been reported several times in the list. > So, > any volunteers? :) This configuration: Allow Higher Duplicates = no Cancel Queued Duplicates = yes Seems to work fine in my situation (some more testing is needed). It cancels the newly created duplicate job immediately. This configuration: Allow Higher Duplicates = no Cancel Running Duplicates = yes cancels the running job and starts the same one. If you have a job that takes more than 24h to complete a runs daily, it will never finish. Hope it helps. When I find some try I will reopen the bug report. Cheers, Bram. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
Note this tread as well; it's possible the documentation is wrong (the
source code seem to indicate so):
Dear All,
Bacula (3.0.2) is configured to make daily backups of some systems. Full
backups unfortunately take more then one day to complete and I want to
avoid that duplicate jobs start (or are queued) before the full backup
is completed.
No duplicate job control directives are configured. If I understand the
manual correctly (perhaps it's an interpretation error of me)
http://www.bacula.org/en/dev-manual/New_Features.html#SECTION00310
this should not happen.
I had a quick look in the source code and found this code in src/dird/job.c:
bool allow_duplicate_job(JCR *jcr)
{
JOB *job = jcr->job;
JCR *djcr;/* possible duplicate */
if (job->AllowDuplicateJobs) {
return true;
}
if (!job->AllowHigherDuplicates) {
--> code related to "Cancel Queued Duplicates: and "Cancel Running
Duplicates" here
}
return true;
}
Apparently "Cancel Queued Duplicates" and "Cancel Running Duplicates"
are only evaluated when "Allow Higher Duplicates" is set to "no" - not
default. Is this an error in the documentation, code or me not correctly
understanding the manual or code?
Kind regards,
Bram Vandoren.
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and
focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Silver Salonen wrote:
> On Monday 31 August 2009 09:33:22 Ralf Gross wrote:
>> Silver Salonen schrieb:
>>> On Sunday 30 August 2009 13:58:44 Ralf Gross wrote:
Martina Mohrstein schrieb:
> So my question is how could I prevent the schedule of a job when the
> same job is already running?
Maybe the new Duplicate Job Control feature in 3.0.x helps to prevent
this?
http://www.bacula.org/en/dev-manual/New_Features.html#515
- Allow Duplicate Jobs
- Allow Higher Duplicates
- Cancel Queued Duplicates
- Cancel Running Duplicates
>>> I haven't still seen it working as it should (even in 3.0.2), but yes, a
> day
>>> it will, it'll be the most correct and easiest way to achieve this.
>> Did anyone file a bug report about that? I searched the bug database,
>> but couldn't find a report about that. At least no open bug.
>>
>> Ralf
>
> Hmm, I guess not then. But it has been reported several times in the list.
> So,
> any volunteers? :)
>
--
Stephen Thompson Berkeley Seismological Laboratory
step...@seismo.berkeley.edu215 McCone Hall # 4760
404.538.7077 (phone) University of California, Berkeley
510.643.5811 (fax) Berkeley, CA 94720-4760
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
On Monday 31 August 2009 09:33:22 Ralf Gross wrote: > Silver Salonen schrieb: > > On Sunday 30 August 2009 13:58:44 Ralf Gross wrote: > > > Martina Mohrstein schrieb: > > > > So my question is how could I prevent the schedule of a job when the > > > > same job is already running? > > > > > > Maybe the new Duplicate Job Control feature in 3.0.x helps to prevent > > > this? > > > > > > http://www.bacula.org/en/dev-manual/New_Features.html#515 > > > > > > - Allow Duplicate Jobs > > > - Allow Higher Duplicates > > > - Cancel Queued Duplicates > > > - Cancel Running Duplicates > > > > > > > I haven't still seen it working as it should (even in 3.0.2), but yes, a day > > it will, it'll be the most correct and easiest way to achieve this. > > Did anyone file a bug report about that? I searched the bug database, > but couldn't find a report about that. At least no open bug. > > Ralf Hmm, I guess not then. But it has been reported several times in the list. So, any volunteers? :) -- Silver -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
Silver Salonen schrieb: > On Sunday 30 August 2009 13:58:44 Ralf Gross wrote: > > Martina Mohrstein schrieb: > > > So my question is how could I prevent the schedule of a job when the > > > same job is already running? > > > > Maybe the new Duplicate Job Control feature in 3.0.x helps to prevent > > this? > > > > http://www.bacula.org/en/dev-manual/New_Features.html#515 > > > > - Allow Duplicate Jobs > > - Allow Higher Duplicates > > - Cancel Queued Duplicates > > - Cancel Running Duplicates > > > > I haven't still seen it working as it should (even in 3.0.2), but yes, a day > it will, it'll be the most correct and easiest way to achieve this. Did anyone file a bug report about that? I searched the bug database, but couldn't find a report about that. At least no open bug. Ralf -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
Yes I already saw this directives but the default values should lead to no duplicate jobs scheduled but as Silver mentioned this new feature seems not to work in the actual version 3.0.2 so I'm looking for a resolution as the one mentioned by Silver. Thank you Silver I will search for your mentioned Script. Regards Martina > From: sil...@ultrasoft.ee > To: bacula-users@lists.sourceforge.net > Date: Sun, 30 Aug 2009 17:21:55 +0300 > CC: ralf-li...@ralfgross.de > Subject: Re: [Bacula-users] How to prevent to schedule a job if the same job > is still running > > On Sunday 30 August 2009 13:58:44 Ralf Gross wrote: > > Martina Mohrstein schrieb: > > > So my question is how could I prevent the schedule of a job when the > > > same job is already running? > > > > Maybe the new Duplicate Job Control feature in 3.0.x helps to prevent > > this? > > > > http://www.bacula.org/en/dev-manual/New_Features.html#515 > > > > - Allow Duplicate Jobs > > - Allow Higher Duplicates > > - Cancel Queued Duplicates > > - Cancel Running Duplicates > > > > Ralf > > I haven't still seen it working as it should (even in 3.0.2), but yes, a day > it will, it'll be the most correct and easiest way to achieve this. > > -- > Silver > > -- > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users _ http://redirect.gimas.net/?n=M0908axFotos2_WW -> Für Fotos hier abdrücken <--- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
On Sunday 30 August 2009 13:58:44 Ralf Gross wrote: > Martina Mohrstein schrieb: > > So my question is how could I prevent the schedule of a job when the > > same job is already running? > > Maybe the new Duplicate Job Control feature in 3.0.x helps to prevent > this? > > http://www.bacula.org/en/dev-manual/New_Features.html#515 > > - Allow Duplicate Jobs > - Allow Higher Duplicates > - Cancel Queued Duplicates > - Cancel Running Duplicates > > Ralf I haven't still seen it working as it should (even in 3.0.2), but yes, a day it will, it'll be the most correct and easiest way to achieve this. -- Silver -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
Martina Mohrstein schrieb: > So my question is how could I prevent the schedule of a job when the > same job is already running? Maybe the new Duplicate Job Control feature in 3.0.x helps to prevent this? http://www.bacula.org/en/dev-manual/New_Features.html#515 - Allow Duplicate Jobs - Allow Higher Duplicates - Cancel Queued Duplicates - Cancel Running Duplicates Ralf -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
On Sunday 30 August 2009 10:41:34 Martina Mohrstein wrote:
>
> We have the follwing problem:
>
> We hava the following backup job that could run longer than one day while a
"full" backup.
>
> Job {
> Name = Full
> Type = Backup
> Client = pdb000qa-fd
> FileSet = "Full Set"
> Schedule = "MonthlyCycle"
> Storage = File
> Messages = Standard
> Pool = Default
> Full Backup Pool = Full-Pool
> Incremental Backup Pool = Inc-Pool
> Differential Backup Pool = Diff-Pool
> Write Bootstrap = "C:\\Documents and Settings\\All Users\\Application
Data\\Bacula\\Work\\Full.bsr"
> Priority = 30
> Max Start Delay = 23 hours
> Max Wait Time = 1 hour
> Rerun Failed Levels = yes
> }
>
> This job has the follwing schedule:
>
> Schedule {
> Name = "MonthlyCycle"
> Run = Full jan 1st sun at 3:05
> Run = Full jul 1st sun at 3:05
> Run = Differential jan 2nd-5th sun at 3:05
> Run = Differential feb-jun 1st-5th sun at 3:05
> Run = Differential jul 2nd-5th sun at 3:05
> Run = Differential aug-dec 1st-5th sun at 3:05
> Run = Incremental tue-sat at 3:05
> }
>
> After startupof bacula with this definition for the very first time, in the
first night this job is upgrades to full because the doesn't exists a prior
backup. This full backup takes more tha one day but in the second night the
job is scheduled another time as full because there still doesn't exist a
valid backup of this job because the old job is still running.
> With the default job directive "Maximum Concurrent Jobs = 1" only the
concurrent run of the same job is prevented but not the schedule of a job when
the same job is still running.
>
> So my question is how could I prevent the schedule of a job when the same
job is already running?
>
> We hope that somebody out there could help us.
>
> Regards Martin
Hi.
To my mind the only possibility is to cancel the duplicate job to-be-run with
a "run before job script" (I've posted my check-job.sh in this list multiple
times previously) and to avoid these cancelled full jobs causing the next one
being full too, you have to have "rerun failed jobs = no".
--
Silver
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
