well,
I was able to test this further, and noe I'm able to add the hyper-v nodes individually to veeam inventory.
I've realized that veeam disabled NTLM access in V13.
I've created a VMgroup at cluster level, and if I add the group to the JOB (cluster is two nodes, so I've added two VMgroup with the same name) and the job runs.
One thing I've noticed, is, if I migrate the vm from one host to another, veeam is creating a new full job for that vm in a new disk in repository, is this the expected behaviour ?
Is this configuration supported by veeam, couldnt see anything otherway in docs
![Image]()
![Image]()
I was able to test this further, and noe I'm able to add the hyper-v nodes individually to veeam inventory.
I've realized that veeam disabled NTLM access in V13.
I've created a VMgroup at cluster level, and if I add the group to the JOB (cluster is two nodes, so I've added two VMgroup with the same name) and the job runs.
One thing I've noticed, is, if I migrate the vm from one host to another, veeam is creating a new full job for that vm in a new disk in repository, is this the expected behaviour ?
Is this configuration supported by veeam, couldnt see anything otherway in docs


Statistics: Posted by pmfna — Sep 28, 2025 12:15 pm





