Skip to main content
  • EN

I’m a newb Veeam user.

I have a WS2022 server with Hyper-V installed on new server.  A vendors app would not function properly on a guest due to USB Pass-through.  In order to get the application working we left HV installed on the server and installed the application on the HV server itself, IE: BareMetal App server.

I have an upcoming project which will hopefully get the application migrated to a guest.  In the mean time, it would be nice to backup the Server. 

I have a guest on server (TEST), and Veeam guest backup works fine.

I try to run an agent based backup job, to copy the entire server:

I get this error on my Veeam Server:  12/18/2024 2:25:04 PM :: Processing Hyperv.XXX.com Error: Failed to connect to Hyperv.XXX.com:11731

Will the Agent work properly if I uninstall HV?  What do I need to do so that it will work?

 

You may need to remove HV to get the agent to work as it detects things during installation which is more than likely causing the issue.

I can give that a try.  Should I also remove the Veeam Agent and have Veeam server install it again too?

Thanks,

Jason

I can give that a try.  Should I also remove the Veeam Agent and have Veeam server install it again too?

Thanks,

Jason

You could do that too to clean things up.

Hi
In my personal experience, ever never install any other role into a Hyper V running server.

What we didi in the past was:
Hyper V Hypervisor, then , vm with Veeam B&R, vm with the Application.
to passthrough the USB, depending on the need, USB over Ethernet solution.

cheers.

Hi,

 

Your error of unable to connect is unrelated to your setup. You’ve got an issue of being unable to connect, check the logs from the VBR server. Did you manually install the agent on the server or did you push the agent from Veeam?

 

You should perform the following troubleshooting steps to rule out multiple things:

 

  • Assuming the agent was pushed out from Veeam Backuo & Replication: Did Veeam target an FQDN or IP address? Can it still resolve the FQDN to the CORRECT IP address? (Your Hyper-V server could be domain joined and returning multiple IP addresses which VBR is querying in a round-robin fashion, or the IP could’ve changed). If necessary, enforce an IP address from the hosts file on the VBR server.
  • Once we know VBR is aiming at the right server, confirm the Veeam Agent is running on the Hyper-V server, so that we have a client endpoint to reach from VBR.
  • Confirm that your firewall rules are in place to allow for communication. Pay attention to the profile currently in place on Hyper-V for the interface that Veeam will reach it on, it’s not uncommon to have a Hyper-V server determine its network as “undefined” when you’re expecting domain/private profile and then your rules don’t work properly
  • Confirm you don’t have any port conflicts by running an elevated command prompt and running the command “netstat -abno”, look for the port that Veeam is struggling to connect to, is Veeam listening on this port? If it’s something else then you have a port conflict (you mentioned another application was deployed on this hyper-v server so there’s a greater than 0% chance of this happening!)
  • Run a packet capture to confirm the Hyper-V server sees the packets entering its network interface.

These steps resolve the problems 99% of the time for me, so give them a try and let us know how you get on and if you need further assistance.

Comment


Terms & Conditions