Hyper-V proxy

Limiting the impact of On-Host backup mode on the production infrastructure

While consuming production resources for backup purpose, the On-Host backup mode disadvantages can be mitigated by the following guidelines.

• Spreading load across hypervisors. It should be kept in mind that the backup load, instead of being carried by a limited number of dedicated proxies, will be spread through all the hypervisors. The default Veeam setting is to limit backup to four parallel tasks per hypervisor, which will use a maximum of four cores and 8GB of RAM. This can be modified in the “managed server” section of the Veeam Console, through the “task limit” setting. For instance, if the sizing guidelines results in a total amount of 24 cores and 48GB of RAM needed for Veeam transport services, and the infrastructure comprises 12 Hyper-V servers, each server task limit can be set to two.

Related links

• On-host backup for Hyper-V
• Off-host backup for Hyper-V
• Off-host proxy on Hyper-V

---