Also, remember that the number of concurrently running backup jobs should not exceed 100. Veeam can handle more, but a “sweet spot” for database load, load ...
02.07.2014 · This host will only have one VM running Veeam Backup and Replication. Host A and B are connected via 1Gb ethernet link. It was suggested that I have a Veeam Proxy running on a dedicated VM on Host A where all of the production VMs are at. The recommendation is that this VM is given "4x4" cpu setup (4 sockets and 4 cores).
For virtual proxy servers, it is recommended to configure multiple proxies with maximum 8 vCPUs to avoid co-stop scheduling issues. If you need to achieve a 2x smaller backup window (4 hours), then you may double the resources for a total of 32 CPU cores and 64 GB RAM - 2x the amount of compute power (possibly split across multiple servers).
01.06.2021 · In this case, Veeam Backup & Replication will distribute the backup workload between available backup proxies. You can deploy backup proxies both in the primary site and in remote sites. To deploy a proxy, you need to add a Windows-based or Linux-based server to Veeam Backup & Replication and assign the role of the backup proxy to the added server.
You can have as many proxies as you have resources to assign as them. But you really only need as many as makes sense. Such as handling x amount of vm backups at once or having a proxy in site a and also one in site b so that backups are processed efficiently by the proxy local to the vms you are backing up etc.
22.07.2011 · I believe with Veeam 9.5 which has Nimble integration that I can do restores using Direct SAN mode from snapshots. I still might need a proxy in the DR site to do these restores if my Production proxy is not available. I know additional proxies can be used to distribute load and speed up backups. In my case, with just 45 VMs and 6TB of data ...