Could you check the logs - If there is more information that we can work with ?
It says "SMB" so can't be LUN, wher does it resides ?
Logs: Log location comes from Sanpcenter documentation, I don't have snapcenter installed hence can't verify. The log files are located at /var/opt/snapcenter/spl/logs. You can also download the log files from the SnapCenter user interface by clicking Monitor > Logs > Download.
According to this TR: (For SMB shares only) SnapCenter currently does not support backup, restore, or cloning for databases on SMB shares. Best Practices Guide for Microsoft SQL Server with ONTAP https://www.netapp.com/us/media/tr-4590.pdf
SnapCenter Plug-in for Microsoft SQL Server features:https://docs.netapp.com/ocsc-43/index.jsp Supports provisioning SMB shares only. Support is not provided for backing up SQL Server databases on SMB shares.
If it's on LUN : Check if you can resolve SMB server hostname (dh-san-02) from Snapcenter?
I will take a look at the logs later (as soon I get some time).
I remember something from SnapManager days (snapDrive). I don't know if you have used SMSQL product before, but there was a requirement for 'snapdrive' to have access to CIFS/SMB from host (where snapdrive was installed) it was required in order to open a tcp port under RPC hood to talk to storage system (other option was http/https if you remeber).
When it comes to SnapCenter, I think the plug-ins have inbuilt snapdrive capability and it may be what it requires to talk back to storage system. It has nothing to do with LUN, but it may require it to talk to storage system.
Can you try this out, while I have your logs checked.
1) Can you setup CIFS on the SVM (Where iSCSI/LUNs provisioned -dh-san-02) - You can delete it later, so no harm. 2) Ensure the Host (where Plug-ins installed) can resolve to storage hostname (dh-san-02), if not add it in DNS or manually create storage host to IP entry on each host. 3) Try split-clone again
In the mean-time, also talk to NetApp support (Incase you haven't already raised a ticket). We need to understand, how it all works in Snacenter , b'cos there are number of components such as : snapcenter server, sm service, hosts plug-ins etc, unless we know how inter-communication works, we cannot troubleshoot.
I am just trying to find the whole logic of SMB in iSCSI environment.
Reading from the tr-4714 SnapCenter uses SM Service, which is a NetApp SnapManager® web service running on top of Windows Server (IIS) on the SnapCenter Server. SM Service takes all client requests such as backup, restore, clone, and so on. The SnapCenter Server communicates those requests to SMCore, which is a service that runs colocated within the SnapCenter Server
Basically: In order to 'start clone' , SM Service & SMCore are key elements , that means somewhere this communication is not happening.
Could you give me this info: ::> network interface show -vserver <vserver> i.e dh-san-02
How is the NetApp storage (SVM) added in Snapcenter ? What IP/LIF type it is? using SVM Management IP ?