> On Thu, 28 May 2020 06:10:36 +0100, Bernie Elbourn said:
>
> On 01/04/2020 16:10, Bernie Elbourn wrote:
> > Oddly, jobs run sequentially as follows rather than duplicates being
> > cancelled:
> >
> > Running Jobs:
> > Console connected at 29-Mar-20 12:36
> > JobId Type Level Files
On 01/04/2020 16:10, Bernie Elbourn wrote:
Oddly, jobs run sequentially as follows rather than duplicates being cancelled:
Running Jobs:
Console connected at 29-Mar-20 12:36
JobId Type Level Files Bytes Name Status
On 19/04/2020 20:49, Pierre Bernhardt wrote:
[SNIP]
For running jobs only that the running job with same level or higher will be
abortet the running.
For queued job it is ok, but for running job it should not start a new at same
level.
Better want to wait or want to cancel.
If there is a way
Am 03.04.20 um 04:58 schrieb Pierre Bernhardt:
> I cannot see an error. By the way here my JobDefs configuration for my daily
> jobs
> which should work nearly as you expect:
>
> 34 JobDefs {
> 35 Name = "RotateJob"
> 36 Type = Backup
> 37 Level = Incremental
> 38 Schedule = "Cycle"
On 03/04/2020 13:19, Gary R. Schmidt wrote:
And the reason it doesn't get cancelled is because they are *not* identical jobs, one is "Differential" and the other
is "Incremental."
You need to run the Differential, Incremental, and Full jobs at different priorities - that reflect how you want
Am 03.04.20 um 14:19 schrieb Gary R. Schmidt:
> You need to run the Differential, Incremental, and Full jobs at different
> priorities - that reflect how you want things done - and set "Cancel Lower
> Level Duplicate = Yes" and "Allow Mixed Priority = Yes" in them all.
Hi,
that could not be
On 03/04/2020 19:38, Bernie Elbourn wrote:
On 03/04/2020 03:58, Pierre Bernhardt wrote:
It is exactly same job configured?
A good thought but yes it is same simple job with no inherited defaults.
Some extra detail this time using sed to reliably obfuscate :-)
Running Jobs:
Console
On 03/04/2020 03:58, Pierre Bernhardt wrote:
It is exactly same job configured?
A good thought but yes it is same simple job with no inherited defaults.
Some extra detail this time using sed to reliably obfuscate :-)
Running Jobs:
Console connected at 29-Mar-20 12:36
JobId Type Level
Am 01.04.20 um 17:41 schrieb Bernie Elbourn:
> Oops...
>
> On 01/04/2020 16:10, Bernie Elbourn wrote:
>> Hi,
>>
>> Oddly, jobs run sequentially as follows rather than duplicates being
>> cancelled:
>>
>> Running Jobs:
>> Console connected at 29-Mar-20 12:36
>> JobId Type Level Files
Oops...
On 01/04/2020 16:10, Bernie Elbourn wrote:
Hi,
Oddly, jobs run sequentially as follows rather than duplicates being cancelled:
Running Jobs:
Console connected at 29-Mar-20 12:36
JobId Type Level Files Bytes Name Status
10 matches
Mail list logo
