Synthetic Full stops next job

[egroeg]

Quick question.

I am running a chain of 10 jobs mon - fri.

My fri job for all jobs is set to run synthetic.

The problem I have is that the backup server sits there for several hours running the synthetic when it could be getting on with another job - but cause they're scheduled one after the other, then next job doesnt take place until the synthetic merge is glued together.

Is there anyway to trigger the next job after the incremetal has completed and prevent the backup server just sitting there running it's synthetic task?

[foggy]

George, is there any reason why do you use job chaining (not considered as best practice) instead of limiting the number of concurrent tasks per proxy and repository and starting all the jobs at the same time, involving Veeam B&R automatic resource scheduling algorithms?