Skip to main content
NetApp Knowledge Base

SnapCenter Enumeration and backup issue of one SQL failover cluster node

  1. Last updated
  2. Save as PDF
Views:
266
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
SNAPX
Last Updated:

Applies to

  • SnapCenter Plug-in for Microsoft SQL Server (SCSQL)
  • SnapCenter Server (SC)

Issue

Users have encountered issues where only the disks from the primary host of the cluster are visible within SnapCenter.
Additionally, backups cannot be performed from the node where disks are not all visible.

When refreshing the host disk in Snapcenter, the Discovery job is showing errors in the log 

2024-04-09T13:05:26.2158895+02:00 DEBUG SCW_30315 PID=[8820] TID=[32] GetHostFileSystem: -> Sending Scsi inquiry \\?\Disk{<diskid>},\\?\Volume{<volume id>}\
2024-04-09T13:05:26.2158895+02:00 ERROR SCW_30315 PID=[8820] TID=[32] sendSCSI failed. Exception - CreateFile failed. Error: 2
2024-04-09T13:05:26.2158895+02:00 DEBUG SCW_30315 PID=[8820] TID=[32] scsiGetAddress: caught exception '2'
2024-04-09T13:05:26.2158895+02:00 ERROR SCW_30315 PID=[8820] TID=[32]
Message : Object reference not set to an instance of an object.
Source : SnapDrive.Nsf.Core.Host
StackTrace : at SnapDrive.Nsf.Core.Host.HostDiscoveryManager.GetHostFileSystem(String host, Boolean isAlm)

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.