Hyper-V UrBackup Client

client
1

Dear all,

Apologies if this is the wrong place to insert this query.

I’ve been desperately trying to setup the Hyper V Client on my hyper v host. I seem to be able to install it and it connects to the server, but it is not adding the virtual machines on the web agent. Is there any prerequisites I should know about? Does Windows Server Backup need to be installed etc? The VM’s have version 9 installed and powershell is up to date. I have also restarted the urbackup service several times.

Kind regards in advanced

2

Unfortunately a known issue, more info in this topic:

3

Thank you for the reply. That is a shame… seems I’m using that same version of the server: 2.5.27.

Out of interest, what have you done for the moment to atleast continue to have your backups working for the VMs. Would still like them backed up and wondered what you’ve been doing.

Kind regards in advanced

4

Using a different backup product :frowning:
Waiting for a fix and then I might give it another go.

5

There is a 2.5.x beta hyper-v client available now. Not as trial currently, though.

@stickmanbrad If possible use 2.4.x with the older client.

6

Hiya Uroni,

Thank you for reaching out. Would I be able to participate in this beta at all? It would really mean a lot.

Let me know,
Kind regards

7

Is there a chance to participate in that beta ? We have paid version

8

is there any update ?

9

Could you provide us more info about progress ?
@uroni

10

The 2.5.21 beta is availabe also as trial since last summer?

It is referenced somewhere in the documentations about Hyper-V:
https://cbt.urbackup.com/2bd39cce-d4ab-4555-90f2-cc4b14ff80fc
=> ah trial is also on selling page as reference:
https://www.urbackup.org/commercial.html

The problem with beta is the not working automatisation of incremental backups in our setup.
When getting commercial client it runs automatically but as I now found out it has another but which is still not fixed over half a year with incremental backups using new VHXD format:

And there is somehow an essential bug with it’s authentication plugin somehow which isn’t answered/fixed also over 6 months:

This was/is also a “not anymore supported” problem for Windows 7 clients, but since this is a Hyper-V 2016 solution it has to work on Windows Server 2016 instances …