Skip to main content
NetApp Knowledge Base

SCSQL restore or clone from secondary storage fails or hangs

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

Applies to

  • SnapCenter Plug-in for Microsoft SQL Server (SCSQL) 4.8P1
  • SnapCenter Plug-in for Windows (SCW) 4.8P1
  • SnapCenter Plug-in for VMware vSphere (SCV) 4.8

Issue

  • Restoring a SCSQL backup located on secondary storage (SnapMirror / SnapVault) fails.
  • Cloning from a SCSQL backup located on secondary storage (SnapMirror / SnapVault) results in the Clone from backup wizard hanging on the Clone Options screen.

 

In both scenarios, the following error messages can be seen:

SMCore_<Job_ID>.log

ERROR SMCore_<Job_ID> PID=[5256] TID=[299] mount snapshot failed Failed to mount storage resource, error is None of the host initiators <Initiator1_WWPN> <Initiator2_WWPN> <iSCSI_Target> are logged into the controller. Resolution: Please make sure the supplied inititators are logged in.

DEBUG SMCore_<Job_ID> PID=[5256] TID=[299] Exception in clone storage Mount operation failed with error Failed to mount storage resource, error is None of the host initiators <Initiator1_WWPN> <Initiator2_WWPN> <iSCSI_Target> are logged into the controller. Resolution: Please make sure the supplied inititators are logged in.

ERROR SMCore_<Job_ID> PID=[5256] TID=[299] ErrorCode (-1), ErrorMessage (Mount operation failed with error Failed to mount storage resource, error is None of the host initiators <Initiator1_WWPN> <Initiator2_WWPN> <iSCSI_Target> are logged into the controller. Resolution: Please make sure the supplied inititators are logged in.

DEBUG SMCore_<Job_ID> PID=[5256] TID=[299] Activity name: Cloning snapshot <Snapshot_Name>: -1 - Mount operation failed with error Failed to mount storage resource, error is None of the host initiators <Initiator1_WWPN> <Initiator2_WWPN> <iSCSI_Target> are logged into the controller. Resolution: Please make sure the supplied inititators are logged in. 

ERROR SMCore_<Job_ID> PID=[5256] TID=[299] Exception in PerformClone Mount operation failed with error Failed to mount storage resource, error is None of the host initiators <Initiator1_WWPN> <Initiator2_WWPN> <iSCSI_Target> are logged into the controller. Resolution: Please make sure the supplied inititators are logged in.

ERROR SMCore_<Job_ID> PID=[5256] TID=[299] Exception in CloneVirtualandStorageResource Failed to clone resources, error isMount operation failed with error Failed to mount storage resource, error is None of the host initiators <Initiator1_WWPN> <Initiator2_WWPN> <iSCSI_Target> are logged into the controller. Resolution: Please make sure the supplied inititators are logged in. 

ERROR SMCore_<Job_ID> PID=[5256] TID=[299] ErrorCode (-1), ErrorMessage (Failed to clone resources, error isMount operation failed with error Failed to mount storage resource, error is None of the host initiators <Initiator1_WWPN> <Initiator2_WWPN> <iSCSI_Target> are logged into the controller. Resolution: Please make sure the supplied inititators are logged in.


SAL_<Job_ID>.log

Error SAL PID=[5256] TID=[12060] None of the host initiators <Initiator1_WWPN> <Initiator2_WWPN1> <iSCSI_Target> are logged into the controller. Resolution: Please make sure the supplied inititators are logged in.

 

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.