Managed agent if PC can't accept inbound connections?

[wku]

Hi!
Quick question.

A PC cannot accept any inbound connections (firewall outside of my control).
So the VBR server wouldn't ever be able to connect to it, however the PC could start a connection to the server no problem.

Would it still be possible to have central management in this kind of situation, in some kind of scheduled-pull-mode by the agent?
Or am I limited to the unmanaged/free-edition features?

Thanks!

[Mildur]

Hello wku

May I ask, is the PC behind NAT? NAT wouldn't be supported for our Veeam Agents. The agent must be able to connect directly to the local ip addresses of the backup server and repository machines.

You can try pre-installed agents to minimize port requirements from backup server to agent. With such a group, you have to manually deploy the agent and apply the configuration file. The agent will then be registered with the backup server.
But there will be still ports (port 6184) required to manage such an agent. And for direct file restore, you will need other ports as well.

Veeam Cloud Connect would be an option (if you are a service provider). It supports NAT and "connection agent to VCC only". No incoming ports have to be opened from Veeam Cloud Connect to the agent pc.

Best,
Fabian

[wku]

Hello and thank you for the answer.
No, NAT is not involved. Both the PCs and the server can see each other's native IPs on the LAN.
It's just a matter of local software firewalls on the PCs which have a blanket "no inbound" rule and are outside of my team's control.
Sounds like unmanaged it is, then...