Skip to main content
  • EN

Hi,

I am kinda new to Veeam Backup. We do have some remote linux hosts without any internal connection to our local infrastructure.

Now, to not use the internet directly, I installed Netbird (just like Tailscale) and connected both, the Veeam Server and the Linux Host. That works, all good.

Now when I add the Host as Managed Server, the initial SSH Connection works and the Netbird IP is being used but then everything else is trying the WAN IPs which, of course, is not wanted and also blocked. So the Setup never finishes. Does anyone know what I could do here?

Thanks
Andreas

For backup traffic you can/should use the Preferred Networks. I’m not sure if this is also works for deploying an agent.

Specifying Preferred Networks - User Guide for VMware vSphere 

 

Otherwise you must configure Managed Servers, that they use VPN connection for communication with VBR

Hey Pete,

thanks for your explanation, much appreciated. The thing is, the Veeam Server already connects to hosts on the local networks. Now if I understand correctly, changing the preferred network would then render the other hosts unavailable, right?

Is there a possibilty to add a linux vm to our infrastructure as some kind of a man in the middle? I “know” that there is some kind of a proxy solution but like I said, pretty new to that whole topic.

Thanks
Andreas

Is the Linux server a repository or something else?  The initial post is not clear on that.  Not sure if the preferred network would work in this case as all components need to talk to each other.  Not sure if adding a static route or hosts entry would help.

The linux host I am trying to setup would be a regular client e.g. agent that needs to be backed up, later on, that was the idea, it should als act as a repository as it has big drives attached we’d like to use as backup storage.

Main idea here anyway was to get the Veeam Server connect to the Linux Host via Netbird. The linux host would be our first one that sits at a Cloud Provider. All other hosts and repositories are sitting in the same private networks as the Veeam Server. Hope that makes sense. 

The linux host I am trying to setup would be a regular client e.g. agent that needs to be backed up, later on, that was the idea, it should als act as a repository as it has big drives attached we’d like to use as backup storage.

Main idea here anyway was to get the Veeam Server connect to the Linux Host via Netbird. The linux host would be our first one that sits at a Cloud Provider. All other hosts and repositories are sitting in the same private networks as the Veeam Server. Hope that makes sense. 

I think you are going to have to look in to Netbird and their support.  I am sure there is ways to set that up so it will always route properly.  For the Agent backup you could do it standalone (install on Linux) and set up the backup from there versus trying to manage it from VBR as a workaround.  Veeam uses the preferred networks as posted and is acting how it should so Netbird is the other avenue to pursue now to get it fully working.

​@andreas.mueller - hmm..not sure on this one. I’m curious as to the solution though. Maybe reach out to Netbird or Veeam Support for assistance. If you can, please provide the solution (if no one else has any ideas).

Best.

So, I’m not sure why it didn’t work last time. Tried today and it just works with the netbird IP/Hostname. Might have been a routing issue last time, I do not know.

In the end, it just works with Netbird as long as you allow all needed ports in the Network Policies.

Cheers

Thanks for the update Andreas 👍🏻

Glad to hear you were able to get things working again.

Comment


Terms & Conditions