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 probl
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.
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
schedule
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
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 High
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 :)
--
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 mu
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
incr
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
>
>
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
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
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
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
>
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
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 Hi
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
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 B
18 matches
Mail list logo
