Proxy
Proxies and Proxy Pools are tightly coupled with Repositories. While a standalone Proxy server or a Proxy Pool can host multiple Repositories, each Repository is uniquely coupled with only one Proxy Pool or as single Proxy (1:N relationship).
Please also refer to the Repository section for more details.
Operating Systems
Since version 8 of Veeam Backup for Microsoft 365, proxy servers can be deployed on Windows and Linux servers. Please take the supported versions into account as documented in the System Requirements.
During Veeam QA lab testing, Linux-based proxy servers proved to be up to 20% more resource-efficient than Windows-based proxy servers.
Proxy Pools
Proxy pools are introduced since v8 and offer a logical grouping of multiple Proxies. The focus is on horizontal scaling to disctribute processing over multiple Proxies.
Proxy Pools only work with Object Storage used for Repositories and each Proxy Pool can be associated with multiple Repositories, but keep in mind that a Repository can only be coupled with one Proxy Pool or as single Proxy.
As a best practice it is adviced to use Proxy Pools whenever possible, they provide the ability to operate in a more flexible backup infrastructure for scaling and maintenance.
Bandwith Throttling
Throttle the used bandwidth per proxy on a shared network connection to not block other applications
By default the proxy servers will take all available bandwidth to run the backups as fast as possible. As normally there is no dedicated internet connection available just for Veeam Backup for Microsoft 365, it’s reasonable to throttle the maximum usable bandwidth (which is done per proxy) so that other applications do not suffer (too much). Depending on the backup schedule the limit should be set to a reasonable value. It might be okay to take 90% of the bandwidth at night but if the backup runs during working hours only 40% can be consumed without affecting operations.