Avamar Plug-in for Hyper-V VSS: Secondary proxy cannot browse Hyper-V VM
Summary: Secondary proxy cannot browse 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.
Symptoms
Hyper-V browse log:
The proxy host is browsing the local instance of the Hyper-V, instead of full farm.
All cluster HA VMs are excluded from the output list even the proxy detected all VMs.
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 the local instance of the Hyper-V, instead of full farm.
All cluster HA VMs are excluded from the output list even the proxy detected all VMs.
Cause
Expected behavior.
Resolution
Browse/Backup of HA VMs should be done by either the designated primary proxy, or the federated instance.
Affected Products
AvamarProducts
Avamar, Avamar Client, Avamar Plug-in for Hyper-V VSSArticle Properties
Article Number: 000065333
Article Type: Solution
Last Modified: 14 Dec 2022
Version: 4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.