Avamar Plug-in for Hyper-V VSS: Secondary Proxy Cannot Browse a Hyper-V VM

Summary: The secondary proxy cannot browse a Hyper-V VM.

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

The following is an example of the Hyper-V browse log output:

2017-05-04 13:56:30 avhypervvss Info <17898>: Highly available VM name is: SQLDB[7b0c9857-23f6-4ed9-a67e-22ac31cfca39]
2017/05/04-05:56:30.89000 [hypervvss_ctl_sup] Node is a cluster node. Filter the CSV VMs
2017/05/04-05:56:30.89000 [hypervvss_ctl_sup] The VM 'SQLDB' with GUID '7B0C9857-23F6-4ED9-A67E-22AC31CFCA39' will be excluded from the output list

The proxy host is browsing only the local instance of Hyper-V instead of the full farm.
All cluster HA VMs are excluded from the output list even though the proxy detected all VMs.

 

Cause

This is expected behaviour.

 

Resolution

Browse or backup operations of HA VMs must be performed by either the designated primary proxy or the federated instance.

 

Affected Products

Avamar

Products

Avamar, Avamar Client, Avamar Plug-in for Hyper-V VSS
Article Properties
Article Number: 000065333
Article Type: Solution
Last Modified: 20 Aug 2026
Version:  5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.