Hyper-V client discover issue

client
1

I have a similar problem…what was the solution?

I have a backup server (Debian 13, Urbackupsrv 2.5.37). The Hyper-V server is hosted externally and connected via the Internet (Urbackupclient 2.5.26.hyperv). The Hyper-V host appears immediately on the server, but the VMs don’t show up.

In the server log, I see the following entry every minute:
2026-07-27 16:04:16: Authed+capa for client ‘Hyper-V-Server’ (encrypted-v2, compressed-zstd, token auth) - 1 spare connections

On Client:

2026-07-27 16:04:16: rc=0 hasError=true state=0
2026-07-27 16:04:16: SERVICE_COMMANDS finished
2026-07-27 16:04:16: Started connection to SERVICE_COMMANDS
2026-07-27 16:04:16: ClientService cmd: #I2JnGoKxxxxxJtBxxxMsW#1CHANNEL capa=36881&token=YJTXXXFItxxxxxlkgVXb&restore_version=1&startup=1&virtual_client=
2026-07-27 16:04:16: New channel: Number of Channels: 1
2026-07-27 16:04:18: VM list: VM1|VM2|VM3|VM4|VM5
2026-07-27 16:05:17: ClientService cmd: PONG
2026-07-27 16:06:17: ClientService cmd: PONG
2026-07-27 16:06:21: ClientService cmd: FSTATUS#pw=3Piyvhqt3XXXXxxxxxxXXXXXxxxxXZq
2026-07-27 16:06:22: ClientService cmd: STATUS#pw=3Piyvhqt3XXXXxxxxxxXXXXXxxxxXZq
2026-07-27 16:06:34: ClientService cmd: STATUS DETAIL#pw=3Piyvhqt3XXXXxxxxxxXXXXXxxxxXZq
2026-07-27 16:06:35: ClientService cmd: STATUS DETAIL#pw=3Piyvhqt3XXXXxxxxxxXXXXXxxxxXZq
2026-07-27 16:06:36: ClientService cmd: STATUS DETAIL#pw=3Piyvhqt3XXXXxxxxxxXXXXXxxxxXZq
2026-07-27 16:06:37: ClientService cmd: STATUS DETAIL#pw=3Piyvhqt3XXXXxxxxxxXXXXXxxxxXZq
2026-07-27 16:06:45: rc=0 hasError=true state=0
2026-07-27 16:06:50: ClientService cmd: GET LOGPOINTS#pw=3l3oxxxxXXXXXxxxxx5JsBFV
2026-07-27 16:06:50: rc=0 hasError=true state=0
2026-07-27 16:07:13: ClientService cmd: STATUS#pw=3Piyvhqt3XXXXxxxxxxXXXXXxxxxXZq
2026-07-27 16:07:17: ClientService cmd: PONG
2026-07-27 16:07:24: ClientService cmd: GET ACCESS PARAMETERS#pw=3Piyvhqt3XXXXxxxxxxXXXXXxxxxXZq&tokens=
2026-07-27 16:07:24: rc=0 hasError=true state=0
2026-07-27 16:08:05: ClientService cmd: STATUS#pw=3Piyvhqt3XXXXxxxxxxXXXXXxxxxXZq
2026-07-27 16:08:17: ClientService cmd: PONG
2026-07-27 16:08:56: ClientService cmd: STATUS#pw=3Piyvhqt3XXXXxxxxxxXXXXXxxxxXZq
2026-07-27 16:09:17: ClientService cmd: PONG
2026-07-27 16:09:47: ClientService cmd: STATUS#pw=3Piyvhqt3XXXXxxxxxxXXXXXxxxxXZq
2026-07-27 16:10:17: ClientService cmd: PONG
2026-07-27 16:10:38: ClientService cmd: STATUS#pw=3Piyvhqt3XXXXxxxxxxXXXXXxxxxXZq

2

The issue was not resolved.

Yours might be different, though. If possible could you send the client log to bugreports@urbackup.org . The server log might also be helpful to see what is going on.

3

From the logs, might be that the virtual clients of the hyper-v client are configured to group level where they are empty. The VMs are managed as virtual clients. If you don’t specify them manually best would be to configure it to use the client setting there.
(Change Client → Additional virtual sub client names to the highway symbol)

4

That worked! Thanks for the quick help.