![veeam careers veeam careers](https://news.itmo.ru/images/news/big/984009.jpg)
Since the proxies were configured with loads of CPU’s and concurrent tasks, just like the repository for that matter. The VM Proxies themselfes were also not the bottleneck in this situation. Since we don’t have as many VM proxies on the environment as hosts, this is not really applicable in my situation, but this is still something to remember. Veeam also has a deep integration in vSAN in which Veeam will automatically, based upon data locality, will choose the most suitable VM proxy to backup the data. Within Veeam however you should also be aware that you need to configure the proxies with the Virtual Appliance Transport Mode. The performance with this SPBM policy is very sufficient, I’ve tried and benchmarked these enough in the past. Within our environment we have the VM proxies configured with a RAID 1 FTT 1 policy, which yields the most performance it can get, next to RAID 0, with still having a copy of the data. With the vSAN environment the configured Storage Policy might affect the performance that a VM proxy can deliver in regards to backup performance. Continue reading the blogpost if you want to find out if this is true! vSAN / Veeam configuration
![veeam careers veeam careers](https://carysun.com/wp-content/uploads/2019/05/053019_2346_ForceStopAV4.png)
If you’ve payed attention to the screenshot above, you might have noticed that the bottleneck is the “Target”, which is the repository. You might find these interesting for your own environment if you want or need to test any specific performance related issues.
![veeam careers veeam careers](https://www.openreality.co.uk/wp-content/uploads/2019/01/veeam_backup_9_5_whats_new_Page_01.jpg)
In the following couple of paragraphs I will walk you through the pieces one by one. The hardware itself and the ReFS configuration.
![veeam careers veeam careers](https://thinfactory.com/wp-content/uploads/shutterstock_1385687756.jpg)