Avamar: Plug-in for Hyper-V VSS: avhypervvss Error <0000>: Failed to get the current hyper-v node name

Summary: Avamar: Plug-in for Hyper-V VSS: avhypervvss Error <0000>: Failed to get the current hyper-v node name.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Hyper-V restore between different clusters fails with:

2017-05-08 17:14:09 avhypervvss Info <13827>: Could not get the current owner name for VMNAME. Will try to restore to the node that owned this VM at backup.
2017-05-08 17:14:09 avhypervvss Info <13830>: The cluster node that owned VMNAME at backup is not running.
2017-05-08 17:14:09 avhypervvss Info <13831>: Attempting to restore the VMNAME to the current node.
2017-05-08 17:14:09 avhypervvss Error <0000>: Failed to get the current hyper-v node name.

In this scenario, customer takes a backup on Cluster A and wants restore with manual provisioning on Cluster B.

Cause

The flag  -federated was present in the C:\Program Files\avs\var\avhypervvss.cmd.

Resolution

Remove the --federated from the C:\Program Files\avs\var\avhypervvss.cmd, the --federated flag must only be available in the cluster var folder.

Affected Products

Avamar

Products

Avamar, Avamar Client, Avamar Plug-in for Hyper-V VSS
Article Properties
Article Number: 000064532
Article Type: Solution
Last Modified: 25 Jul 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.