Skip to main content
NetApp Knowledge Base

SQL verification fails where the verification host has no contact with the new vCenter environment

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

Applies to

  • SnapCenter Server (SC)
  • SnapCenter Plug-in for Microsoft SQL Server (SCSQL)
  • SnapCenter Plug-in for VMware vSphere (SCV)
  • RDM/VMDK disks

Issue

  • After moving to a new vCenter instance, the verification host has no contact with vCenter and the verification part of the job fails.
  • Backup is successful
  • Error in <installation_path>\Program Files\NetApp\SnapCenter\SMCore\log\SMCore_<id>.log:

INFO SMCore_312817 PID=[5704] TID=[8] Activity - Query Host Information, Starting
INFO SMCore_312817 PID=[5704] TID=[8] ContainsVirtualSanFileSystem:False, ContainsPhysicalSanFileSystem:True
INFO SMCore_312817 PID=[5704] TID=[8] Could not get initiator information from host, to mount physical SAN file system(s).
ERROR SMCore_312817 PID=[5704] TID=[8] Exception in method: Execute

 

 

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.