Linking jobs and disabled ones running after enabling

[blackforce]

I find that veeam has an annoying feature when you link jobs.

Lets say you have 6 jobs all linked to start after one another. Job number 1 fails over night so you want to re-run it in the morning.

You disable job 2 so that it doesn't run after. Then you run job 1. It completes fine. However then you reenable job 2. It then kicks off unless you leave it for ages before enabling it.

Anyone else find this annoying? How do you overcome it? Can it be removed?

[veremin]

Therefore, in case of 6.5 version, it’s always recommended to use 1 as number of maximum concurrent tasks that proxy/repository can handle and staging the job (scheduling them to run with 5 minutes interval). This way, the repository/proxy is limited to one task at a time, and the other jobs will just queue up and, then, be processed once the first one is finished. Thanks.

[blackforce]

Ah so your saying that Job 1 should start at 9pm, then then next 9:05pm, next 9:10pm etc rather than linking the jobs to be run after the 1st is complete?

[veremin]

Yep, in case of 6.5 version, it’s advisable to use number of concurrent tasks and staging schedule, instead of linking. In this case, you will avoid problems related to linking, such as inability to run just one job, etc. Thanks.

[blackforce]

What about in version 7?

[foggy]

General recommendations of limiting the number of maximum concurrent tasks are still valid for v7. However, you should keep in mind that setting it to 1 will literally disable parallel processing functionality that was introduced in this version. So everything depends on why do you actually need to link jobs at all.

[blackforce]

We dont necessarily need to link them. I thought it was introduced to stop having gaps in between jobs of no activity. I didn't realise that 5 min gaps was an option.

However I will trial setting all the jobs 5 mins apart and see what happens.

Thanks