Avamar: Unable to browse using Hyper-V GLR

• During a Hyper-V GLR browse operation, the Restore window in Avamar Administrator displays "Err" in the tree view, and no further action occurs.

• The following errors appear in avagent.log on the Hyper-V GLR client 

avagent Warning <5464>: Invalid browse request  (6)No PID to executable association
avagent Warning <6690>: CTL workorder "Browse" non-zero exit status 'code 536870925: externally cancelled'
...
avagent Error <5365>: Cannot connect to 192.168.1.1:28001.
avagent Error <5449>: No executable associated with PID 3033-Hyper-V GLR.
avagent Error <5365>: Cannot connect to 192.168.1.1:28001.

• The avhyperv_plugin.log file shows messages similar to: 

avhypervglr Info <9528>: Cancel request received - no assistant or aborted assistant

Network connectivity issues between the Avamar grid and the Hyper-V client prevent GLR browse operations, even if backups complete successfully.

• From the Avamar grid, test connectivity to the Hyper-V client using telnet: 

  telnet hyperv.avamar.com 28002
  telnet hyperv.avamar.com 30002

• If session security is enabled, the Avamar agent listens on port 30002 instead of 28002.
• GLR requires successful connectivity on one of these ports.

• Temporarily disable the Windows Firewall on the Hyper-V client for testing purposes.

• Run iPerf tests between the Avamar server and the Hyper-V client to identify bandwidth or latency issues.
• Pay attention to packet flow from the grid to the client.
• Refer to the following knowledge article for guidance and examples: Avamar: Troubleshoot network issues causing Windows backup performance to be very slow

• Redirect the Hyper-V GLR browse operation to another Windows client with the Hyper-V GLR plug-in installed.