+9Hello,
i would like to ask, if anybody has experience, if there is different between selection of proxy server per job or per repository.
Is there different between priority or some deep thing?
i am just thinking, if its better to use selection of proxy per job A (same proxies for all jobs on side A) or only select proxies in affinity per repo/extent for side A?
thank you
Best answer by matheusgiovanini
Yes, there is a difference depending on how you configure proxy selection.
In Veeam, the number of simultaneous tasks a proxy can handle is based on the number of CPU cores of the server where the proxy is deployed. Typically, the default setting is one task per CPU core.
Each disk from a VM or volume from an agent is considered one task. So, if a VM has multiple disks, each disk may consume one task simultaneously. This is important when considering proxy load.
If you select proxies per job, all jobs will try to use the same proxies even if they are already busy, which may cause bottlenecks. If you configure proxies by repository affinity, Veeam can better balance the load across proxies during operations, optimizing task usage and performance.
In larger environments, using repository proxy affinity is generally recommended for better scalability and automatic load balancing.
+21There is no special selection process unless you specify the proxies in the job. This might help to explain how backup flow works - https://bp.veeam.com/vbr/Support/S_Vmware/backup.html
+12Basically a proxy can handle multiple tasks at once. If you use multiple backup jobs you don’t need to have multiple proxies as long as you pay attention to the scheduling.
Example:
A proxy can handle 16 tasks (1 task = 1 virtual disk to back up). If you have multiple jobs with 50 VMs each the proxy will handle the VMs within a job one after the other. If a second job would run at the same time, there might be objects in a queue and you don’t want that since this might cause your backup windows to exceed certain windows.
On my example: Make sure (by scheduling) that the jobs don’t run at the same time and Veeam takes care of the rest.
Same is for the repo, by the way. The repo can also handle a certain amount of tasks.
+5Configuring proxy affinities is largely based on bandwidth considerations. If your Veeam server manages backups on a remote site with a remote proxy and repository, it would be beneficially to configure an affinity between the remote components so your local proxy doesn’t get selected during a backup run.
Configuring it at the repository level keeps you from having to configure it on each and every job.
+6Yes, there is a difference depending on how you configure proxy selection.
In Veeam, the number of simultaneous tasks a proxy can handle is based on the number of CPU cores of the server where the proxy is deployed. Typically, the default setting is one task per CPU core.
Each disk from a VM or volume from an agent is considered one task. So, if a VM has multiple disks, each disk may consume one task simultaneously. This is important when considering proxy load.
If you select proxies per job, all jobs will try to use the same proxies even if they are already busy, which may cause bottlenecks. If you configure proxies by repository affinity, Veeam can better balance the load across proxies during operations, optimizing task usage and performance.
In larger environments, using repository proxy affinity is generally recommended for better scalability and automatic load balancing.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
