Pre-Installed Agents Feature in v11 to get around NAT

[rleon]

The documentation on Pre-Installed Agents Protection Groups focuses on how it is now possible to use 3rd party products to manage the installation of Veeam Agents.
This also implies that by using this method, it is now easier to pre-deploy Veeam Agents in VM templates, or Sysprep'd / cloned OS Images.
That's all good (even though Pre-Installed Agents are limited to only Agent Managed jobs).

But the way this new feature is further described, also emphasizes that the VBR server will no longer initiate network connection to these types of Agents.
All network connections will be initiated from the Agents to the VBR server, including backup traffic or just synchronizing for new job policy changes (changed schedules, target storage, etc.)
If this is the case, does that mean Agents behind NAT gateways/firewalls will work? If the above is true, then it should.
But even if it does work, is this "Agents behind NAT" use case officially supported by Veeam?
The reason why I need to ask is because of the suspicious omission of any mentioning of using this new feature to protect "Agents behind NAT", even though this should be an obvious advantage.

[Vitaliy S.]

Hi RLeon,

Yes, you got it right. With the new protection group in which Agents are pre-installed, the connection is done from Agents to the VBR server (not vice versa), so the configuration with NAT is supported.

Thanks!

[rleon]

Thanks for confirming.
Well, what are you waiting for? Directly say so in your docs! It's a GOOD thing to point out!

[Vitaliy S.]

I will share this feedback with our TW team, but also let us know how it works in your case and if you need anything else from us to update in the current implementation.