I did a little noodling on the boards, and couldn't find a good answer to this question, so I figured I'd throw this out there.
What are the best practices for sizing a Veeam server? System in question :
Virtual Machine - Windows 2008 R2 Standard
Locally attached R60 storage on LSI 9280 RAID controller (48 1TB drives, 10+2 RAID60 stripe configuration)
Remote SQL 2008 Cluster
4 Proxies, 1vCPU, 4GB RAM, Hot-Add backup mode.
Reverse Incremental backup
Currently backing up ~130 VM's, 17.76TB utilized on storage.
The storage is slow, and is the current bottleneck, but that is being solved with a second deployment of Veeam, and using 48 drives in RAID10, rather than RAID60.
Question is - how large can I theoretically grow 1 Veeam master server, and what are the recommendations around Storage Repositories? Right now there are two storage repositories that are configured in the master server that reside on the local RAID array. Memory utilization during the backup window is high, along with CPU utilization (95% spike at beginning of backup window, and flattening to 60% until the end of the backup window).
I'm worried that continuing to add backup jobs will continue to add load to the primary Veeam server. I've considered simply adding a second physical server just as a windows CIFS share, and adding it as a second repository, but I worry that adding more jobs will continue to compound the CPU utilization on the primary Veeam server. Is it typical to see that type of CPU utilization on the primary Veeam server, even when using proxies?
How are people that are backing up a large amount of VM's handling these questions, and how are you sizing your systems?