Skip to main content
NetApp Knowledge Base

SMHV backup fails by service connection failure during Windows maintenance

  1. Last updated
    Dec 3, 2024
  2. Save as PDF
Views:
13
Visibility:
Public
Votes:
0
Category:
snapmanager-for-hyper-v
Specialty:
snapx
Last Updated:
12/3/2024, 9:24:24 AM

Applies to

  • SnapManager for Hyper-V (SMHV) 2.1.4
  • Microsoft Windows Server 2016
  • Maintenance task is performed on Windows host

Issue

  • SMHV backup fails during maintenance task performed on Windows host and the error is automatically resolved after the maintenance
  • SMHV backup report indicates following error:

An error occurred in the backup process.[Host: <CLUSTER>]
Web Service Client channel was unable to connect to the ProtectionService instance on machine <CLUSTER>.
Could not connect to net.tcp://hyperv4/SnapManager/HyperV/HyperVProtectionService/v_10. The connection attempt lasted for a time span of <TIME>. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond <IP>:808. 

  • SnapMgrServiceHostDbg.log indicates OpenCluster returned error 1722

ProcessID= <PID> ThreadID= <TID> OpenCluster returned error 1722
ProcessID= <PID> ThreadID= <TID> Failed to get cluster nodes. Error 1722Source: SnapMgrAdaptor
Stack Trace:    at SnapMgrAdaptor.ClusterAdaptor.IsClusterSystem(String& strClusterName, List`1& lstNodes, Boolean listActiveNodesOnly)

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.