Cloning fails after changing the vCenter FQDN
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.