Skip to main content
Solved

Selected Server Veeam is unavailable


Forum|alt.badge.img+1
  • Influencer
  • 95 comments

We have an issue with backup , getting error Selected Server  Veeam is unavailable while backing up to remote site NAS 

Processing Hyper-V Backup to remote site NAS fails with error Selected Server Veeam  is unavailable.

 

Running Veeam server directly on Hyper-V host ( I know it is not recommended, but its been running with no issues for 10+ years now)

Veeam ver 12.3

Veeam server itself is Backup proxy server ( Configured as Vmware proxy server)

Selected off-host proxy ( Automatic selection)

( erased the original server name)

 

All of our physical servers are Hyper-V Hosts (WinServer2022). I am planning to use another server as off-host proxy .I have another Hyper-V host in environment hosting VM’s .  Is it recommended to use existing hyper-v host as off-host  or please suggest me another solution to resolve this issue.

Best answer by lukas.k

Did you check the load on the server?

I didn’t ever try to install VBR on a bare-metal Hyper-V tbh but I do Hyper-V a lot and I never experienced that selecting off-host methods works without additional configuration.

 

You understanding is basically right: If the off-host method doesn’t work Veeam fails over to on-host.

 

I’d do the following: Switch to on-host and check the load on the server to see if there’s a bottleneck.

 

Please also check if you firewall zones (or your network(s), to be more specific) are set to “private” (or “domain”). By default it could be declared as “public” which could lead to errors on the network stack.

View original
Did this topic help you find an answer to your question?

11 comments

Mohamed Ali
Forum|alt.badge.img+2
  • Experienced User
  • 45 comments
  • March 12, 2025

@Nikks Based on the screenshot, it looks like there is no Hyper-V Proxy configured. I only see VMware Proxy and Agent Proxy. 

 

You should add Hyper-V server for the off-host proxy to backup your VM’s running in Hyper-V infrastruture https://helpcenter.veeam.com/docs/backup/hyperv/hv_proxy_launch.html?ver=120


Forum|alt.badge.img+1
  • Author
  • Influencer
  • 95 comments
  • March 12, 2025

Thanks ​@Mohamed Ali . Do I need to use new hyper-v server for off-host proxy or existing hyper-v servers running on my prod ? 


lukas.k
Forum|alt.badge.img+10
  • Veeam Vanguard
  • 227 comments
  • March 12, 2025

Hi ​@Nikks,

For Hyper-V there is usually no Hyper-V proxy listed in Veeam. This is because Hyper-V works different with Veeam than vSphere.

Usually the proxy role is installed as a service on the Hyper-V nodes (this is called on-host) and only in case you use an off-host proxy it will be listed in Veeam.

For an off-host proxy you usually need a deeper “integration” since a Hyper-V cluster is working with cluster shared volumes and other services. Therefore you should refer the the storage vendors manual (in case of an HCI or S2D there also are article available).

 

Did I get you right that you have the VBR installation on the bare-metal of the Hyper-V server installed? In case yes, you can - in my opinion - simply switch to on-host since there will be no difference (it’s the same host).

Keep in mind that on-host proxies will not specifically be listed in Veeam as proxy.

 

Hope that helps!

 

Best

Lukas


Forum|alt.badge.img+1
  • Author
  • Influencer
  • 95 comments
  • March 12, 2025
lukas.k wrote:

Hi ​@Nikks,

For Hyper-V there is usually no Hyper-V proxy listed in Veeam. This is because Hyper-V works different with Veeam than vSphere.

Usually the proxy role is installed as a service on the Hyper-V nodes (this is called on-host) and only in case you use an off-host proxy it will be listed in Veeam.

For an off-host proxy you usually need a deeper “integration” since a Hyper-V cluster is working with cluster shared volumes and other services. Therefore you should refer the the storage vendors manual (in case of an HCI or S2D there also are article available).

 

Did I get you right that you have the VBR installation on the bare-metal of the Hyper-V server installed? In case yes, you can - in my opinion - simply switch to on-host since there will be no difference (it’s the same host).

Keep in mind that on-host proxies will not specifically be listed in Veeam as proxy.

 

Hope that helps!

 

Best

Lukas

Thanks lukas for the information. The reason why I thinking about off-host proxy is , the error message showing selected server veeam is unavailable which is my veeam server with the role onhost proxy by default. The setting configured is ' failover to onhost' when offhost proxy is unavailable. I guess that could be the issue, because it is failover to onhost proxy veeam server and the veeam server is overloaded or any other reason server is unavailable.

I am not sure if my understanding is correct 


lukas.k
Forum|alt.badge.img+10
  • Veeam Vanguard
  • 227 comments
  • Answer
  • March 12, 2025

Did you check the load on the server?

I didn’t ever try to install VBR on a bare-metal Hyper-V tbh but I do Hyper-V a lot and I never experienced that selecting off-host methods works without additional configuration.

 

You understanding is basically right: If the off-host method doesn’t work Veeam fails over to on-host.

 

I’d do the following: Switch to on-host and check the load on the server to see if there’s a bottleneck.

 

Please also check if you firewall zones (or your network(s), to be more specific) are set to “private” (or “domain”). By default it could be declared as “public” which could lead to errors on the network stack.


Forum|alt.badge.img+1
  • Author
  • Influencer
  • 95 comments
  • March 12, 2025

Thanks for the answer. I will check the load on the server and will update.


Mohamed Ali
Forum|alt.badge.img+2
  • Experienced User
  • 45 comments
  • March 12, 2025

I’d also suggest switch to on-host proxy method and try again, Please check the network connectivity between the Repo and Proxy as well. 

If it’s still failed check the logs from C:\ProgramData\Veeam\Backup\JobName and see if there is more information on the error.

 


matheusgiovanini
Forum|alt.badge.img+5

Interesting case! Checking firewall rules and Veeam services might help. Let us know how it goes!


Forum|alt.badge.img+3
  • Comes here often
  • 123 comments
  • March 13, 2025

Hi ​@Nikks 

 

>Running Veeam server directly on Hyper-V host ( I know it is not recommended, but its been running with no issues for 10+ years now)

Not quite correct. It’s not only not recommended, it’s not supported:

https://helpcenter.veeam.com/docs/backup/hyperv/simple.html?ver=120

Important

You must not install Veeam Backup & Replication directly on a Hyper-V host. Such installation may lead to unpredictable system behavior. Instead, install Veeam Backup & Replication and its components on dedicated machines. Backup infrastructure component roles can be co-installed.

 

Spin up a VM with VBR on it and use the Configuration Restore to migrate to the VM.

Basically, while I cannot guess in full what’s causing this, the current configuration can lead to issues like this, so I advise correct the configuration first and see if the behavior persists. If the issue persists, then open a Support Case.


Forum|alt.badge.img+1
  • Author
  • Influencer
  • 95 comments
  • March 18, 2025
lukas.k wrote:

Did you check the load on the server?

I didn’t ever try to install VBR on a bare-metal Hyper-V tbh but I do Hyper-V a lot and I never experienced that selecting off-host methods works without additional configuration.

 

You understanding is basically right: If the off-host method doesn’t work Veeam fails over to on-host.

 

I’d do the following: Switch to on-host and check the load on the server to see if there’s a bottleneck.

 

Please also check if you firewall zones (or your network(s), to be more specific) are set to “private” (or “domain”). By default it could be declared as “public” which could lead to errors on the network stack.

@lukas.k Worked ! Changed to on-host did the trick. Thank you for the solution.


lukas.k
Forum|alt.badge.img+10
  • Veeam Vanguard
  • 227 comments
  • March 18, 2025
Nikks wrote:
lukas.k wrote:

Did you check the load on the server?

I didn’t ever try to install VBR on a bare-metal Hyper-V tbh but I do Hyper-V a lot and I never experienced that selecting off-host methods works without additional configuration.

 

You understanding is basically right: If the off-host method doesn’t work Veeam fails over to on-host.

 

I’d do the following: Switch to on-host and check the load on the server to see if there’s a bottleneck.

 

Please also check if you firewall zones (or your network(s), to be more specific) are set to “private” (or “domain”). By default it could be declared as “public” which could lead to errors on the network stack.

@lukas.k Worked ! Changed to on-host did the trick. Thank you for the solution.

You’re very welcome, glad that this could help!


Comment