We have 3 running jobs.
2 jobs are actually doing something.
1 job is waiting for a proxy and is at 0%.
When i look at the 2 tasks, we see proxy 07 being used. This proxy 07 is active on 4 disks simultaneously.
We are wondering why the waiting job is not kicking off because we have 6 other proxies waiting.
WHen we stop the job and restart it, it again says "waiting for proxy".
By now we were thinking, could it be seriously trying to go through proxy 07 while there are 6 proxies doing nothing?
So we edit the job, deselect proxy 07 and leave the other proxies selected and start the job again.
It kicks into action and starts backing up a VM.
Now maybe i am missing something here, but i assumed that if i have 7 proxies assigned to all jobs, veeam would select the next available proxy if it cannot use one that is busy.
It now feels like some jobs are determined to use a certain proxy and wait for it, even when it takes hours.
We are constantly learning new things, but now we are thinking of splitting up all the jobs and spread them over different proxies manually. But that seems a bit weird as this should go automatically right?
We were amazed at what we discovered.