Limit maximum concurrent task for single job (set priority?)

[KeiichiKun]

Hi all,
I've a repository with Limit Maximum Concurrent Task set to 5 (windows server, drive Z:), and two backup copy job writing on that repository; for example, Job1 needs to backup 5 vms and Job2 3 vms.
I need to set something like a priority between these two jobs, for example job2 takes its slots before job1, so during copy I've Job2 (3 vms running) and Job1 (2 vms running). At the end of first vm backup from job2, Job1 will take the free slot and so on.
I've searched for a parameter that can handle this, but with no luck.
I don't want to create a new repository, Z:\backups\job1\ and Z:\backups\job2\, it will be too dedicated to a specific job and it cannot be the best solution for 3, 4 or 5 jobs running.
Obviously, in current configuration, job1 takes 5 slots and job2 is stuck in waiting for backup infrastructure resources availability
Any ideas?
Thanks!

[Shestakov]

Hi KeiichiKun,
The possible solution here is to start backup copy 2 earlier that backup copy 1, so it can take slots first. Indeed there is no way to set up priorities manually.
Thanks!

[KeiichiKun]

That's obviously a good idea, but in my case
- Job1 and Job2 are two backup copy jobs running continuously
- Job1 depends on 4 different jobs with 30 vms (3+1+15+11)
- Job2 depends on 2 different jobs with 3 vms (2+1)
It's not so easy synchronize everything

Thanks!

[Shestakov]

You are right, scheduling is going to be a tricky part.
By the way, have you tried to raise the number of parallel tasks on the repository?
Thanks

[KeiichiKun]

Yes, I've increased to 6-7-8 task limit, but I'm not sure that repository can handle this. I hope so
Anyway sometimes It could work but when I'll add a new backup job to backup copy with 3-4-5 vms inside it, I'll be back in the same situation.
Clearly, after first full, slots will be free in a short time so the problem is not so serious
Maybe 9.6 could introduce priority feature
Thanks again!

[Shestakov]

Such an option will not be presented in v9.5, however your feature request is taken into account.
There is no rule for max. number of parallel tasks on repository, it`s better to find it out empirically.
Thanks!

[KeiichiKun]

I'll add a new feature request for veeam >9.5
Network bandwith limitation job-oriented?
Now that I've stopped job1 and started job2 (and then again job1), job2 has taken his 2 slots, but job1 with 3 slot takes 60% bandwith, I need for example 80% for job2 (I'm in a hurry to finish it) and 20% to job2.

Thanks!

[Shestakov]

VBR v9.5 is to be released in a week or so. Feature requests are will not be implemented earlier than in v10.
You can configure traffic throttling rules for the involved source and target repositories.

[KeiichiKun]

Obviously I've talked about greater than 9.5, like 10.0 or 11.0

[Shestakov]

Your request is taken into account. Thank you!