Question on VBR 7.0 concurrent jobs

[hollow]

I have a few queries on Veeam B & R 7.0 concurrent jobs

Scenario:
1 x ESXi host
1 x v7000 storage
1 x virtual Veeam Master backup server
1 x physical proxy server
Backup mode: SAN

1. I have 10 backup jobs. Each job contains 3 vm. On the Master server, I have configured the proxy to have 12 "Max concurrent tasks"
However, when I did a test by running 5 backup jobs concurrently, only 4 VMs were backing up:

Eg:
Job 1 - Three VMs are backing up
Job 2 - First VM is backing up, the rest of the 2 VM is Pending 0%
Job 3 - All 3 VMs are in pending state
Job 4 - All 3 VMs are in pending state

Why are the 4 jobs not running concurrently?

2. Also, I noticed that the way concurrent backup jobs run in 7.0 has changed from 6.1
Given the same scenario above, it used to be this way (correct me if I am wrong):

Job 1 - 1st VM is backing up, the remaining 2 VMs are in pending state
Job 2 - 1st VM is backing up, the remaining 2 VMs are in pending state
...
...
Job 12 - 1st VM is backing up, the remaining 2 VMs are in pending state

In 7.0, it seems to changed to this (However this is not reflecting in my environment, which I have stated in point 1.):

Job 1 - Backup is running on all 3 VMs
Job 2 - Backup is running on all 3 VMs
Job 3 - Backup is running on all 3 VMs
Job 4 - Backup is running on all 3 VMs
Job 5 onwards - Pending

3. When backing up through a proxy, does it use the resources (eg: CPU/RAM) from the proxy or the Master backup server? I am guessing it is using the resources from the proxy. (Need confirmation)

Apologies if my post is confusing. Anyone can shed some light on how concurrent jobs work in Veeam 7.0 (Patch 1) please?

[chrisdearden]

Have you got parallel processing enabled?

[hollow]

Yes. It is checked by default.

[hollow]

Case close.
Both proxy and repository have the settings for concurrent jobs.

In my case, I have changed the settings only on the proxy side but not on the repository side.

I have now changed both repository and proxy settings to the same number of concurrent jobs.

[nefes]

If you open details for pending VM in any job, you will see which resourse is unavailable. It will help you to understand the cause of the situation.
Also please be aware that setting for proxy is limiting number of concurrent tasks, not jobs.
So if you have say 1 job of 3 VMs with 3 disks each, that job needs 9 concurrent tasks on the proxy, and only one recieving task on repository.

[veremin]

Yep, the number of concurrent tasks is related to maximum number of disks that can be processed simultaneously by backup proxy/repository. So, the questions is – how many disks do the corresponding VMs have?

Thanks.