Skip to main content
NetApp Knowledge Base

SnapCenter fails to discover disks after migrating to a new SQL server host

Last Updated:

Applies to

  • SnapCenter Server (SC) all versions
  • SnapCenter Plug-in for Windows
  • SnapCenter Plug-in for SQL Server (SCSQL)
  • SnapCenter Plug-in for Exchange (SCE)


  • After removing the disk(s) from the original host and migrating to a new SQL host, an SC disk refresh fails to pick up the disk(s) on the new host
  • See the following entry in the <installation_path>\NetApp\SnapCenter\App_Data\log\SnapManagerWeb_<id>.log:

DEBUG SnapManagerWeb_408978 PID=[928] TID=[21] Found storage file system [disk_mountpath] resource.
DEBUG SnapManagerWeb_408978 PID=[928] TID=[21] GetNsmObjectByResource - exit
DEBUG SnapManagerWeb_408978 PID=[928] TID=[21] The discovered resource is registered on xx, not on xx

  • The message shows that the disk(s) are still registered on the old host


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.