I have been approached by a potential customer case where the customer has 2500 physical machines mostly spread out on different locations. Not sure if it's 2500 locations yet, but lets assume it is. This customer has connection to all sites using IPSEC from my understanding, so a hub-spoke kinda setup. On each site they are responsible for a Physical machine running Windows. On these machines they have some config or files they need to backup, it's around 15-20TB today in total for all these sites from what I understand. These machines does not have internet access, but have access to our potential customer over IPSEC vpn as mentioned.
I was thinking of suggesting that they get a Veeam Backup & Replication and a Repo at their HQ and use protection groups and then Files and Folders backup instead of what they're using today. I am not familiar with Protection Groups VBR backup of physical environment except from our VSPC and CC environment. So I need some input on planning and design here. I am under the impression that the customer wants to manage and operate the solution themselves, and ask us for help if they need to.
Any suggestions, input or feedback to my plans so far would be appreciated.
Purely from a logistical standpoint your design approach should work. As long as the the installation at the hub can communicate with all the remote sites over the VPN and the agents can communicate back to the VBR and Repo at the hub, it should work.
With the VSA implementation or Windows VBR at the hub, either should be more than capable of managing that number of Agents just fine. You could then leverage protection groups to deploy agents out to the individual servers at their respective locations. You could likely approach this with a Pre-installed Agent protection group as well to roll out the implementation (https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13). This would allow you to simplify the implementation if they have some kind of platform to automate pushing the package out to the different systems. You would configure the repository at the Hub and then configure that as the target for the agent jobs once configured.
