Avamar: Plug-in for Hyper-V VSS Error 0000 Failed to Get Current Hyper-V Node Name
Summary: The Avamar Hyper‑V VSS plug‑in logs Error 0000 because it cannot obtain the current Hyper‑V node name. The cause is the –federated flag present in avhypervvss.cmd.
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.
Symptoms
During a restore of a Hyper‑V VM from one cluster to another, the plug‑in logs the following messages:
2017-05-08 17:14:09 avhypervvss Info : 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 : The cluster node that owned VMNAME at backup is not running. 2017-05-08 17:14:09 avhypervvss Info : Attempting to restore the VMNAME to the current node. 2017-05-08 17:14:09 avhypervvss Error : Failed to get the current hyper‑v node name.
The restore operation fails because the plug‑in cannot determine the current Hyper‑V node.
Cause
The --federated flag was present in the C:\Program Files\avs\var\avhypervvss.cmd file. This flag causes the plug‑in to attempt to retrieve the node name from a federated configuration, which fails when the command starts on a non‑federated cluster, leading to the “Failed to get the current hyper‑v node name” error.
Resolution
- Open the file
C:\Program Files\avs\var\avhypervvss.cmdin a text editor. - Locate the --federated flag in the command line.
- Remove the --federated flag so that it is not present in this file.
- Save the file and retry the restore operation. The --federated flag should only exist in the cluster‑specific var folder.
Affected Products
Avamar, Avamar Plug-in, Avamar Plug-in for Hyper-V VSSArticle Properties
Article Number: 000064532
Article Type: Solution
Last Modified: 24 سبتمبر 2026
Version: 5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.