Skip to main content
NetApp Knowledge Base

Cloning fails after changing the vCenter FQDN

  1. Last updated
    Nov 4, 2024
  2. Save as PDF
Views:
61
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:
11/4/2024, 10:14:32 AM

Applies to

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

Issue

  • After changing the vCenter FQDN, verification cloning fails at the file system stage with the error:

VirtualizationAPILog Critical: 1 :    07/09-9:32:08.309  PID:4584  TID:1784 @-1  CVirtualServer::FindAndRescanHBA() - Failed to rescan HBA:Exception message: The remote name could not be resolved: '<old_vCenter_FQDN>'

ERROR SMCore_33245 PID=[5224] TID=[57] ErrorCode (-1), ErrorMessage (An error occurred while cloning RDM based disk. Failed to rescan HBA: The remote name could not be resolved: '<old_vCenter_FQDN>'
Error: Failed to map virtual disk on Esx host after retrying.

  • SCV is showing the correct vCenter FQDN.

 

 

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.