nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can't split clone for SQL backup on SnapCenter 4.3

kkeyser1971

Maybe I don’t understand something, but ... Does SnapCenter 4.3 support clone splitting for SQL databases resides on LUN?

When I try to split the clone I got the following error: "Failed to get the SMB server for storage system".
Which SMB server was looking for?

Find more posts tagged with

SnapCenter

Accepted answers

Ontapforrum

Ok...we might be getting closer.

For SAN Protocols (iSCSI/FC) a dedicated SVM management LIF is required because data protocols and management protocols cannot share the same LIF.

1) Please create a SVM Management LIF

cluster::> network interface create -vserver dh-san-02 -lif SVM_mgmt_LIF_name -role data -data-protocol none -address x.x.x.x -netmask x.x.x.x -home-node node_a_or_b -home-port e0M -status-admin up

2) You mentioned SVM are not managed separately in snapcenter ? Please add the SVM directly instead of the Cluster, using the IP created in step 1.

3) I don't have SnapCenter console so I am kind of blind here, but figure out how you need to configure : If you need to re-discover it whatever.

Give this a try. Snapcenter must talk back to Storage via SVM Manamgnet LIF for Management related ZAPI calls.

All comments

Ontapforrum

Hi,

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?

Thanks!

kkeyser1971

Hello,

The "dh-san-02" SVM have one and only the iSCSI service. Therefore, I am very surprised why suddenly SMB:

No, "dh-san-02" does not resolving from SnapCenter. I don't maked any DNS records for it.

The log file for this job was attached.

Thank you for your reply!

SnapCenterJobLogs_519.zip

Ontapforrum

Hi,

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.

Thanks!

kkeyser1971

Well, I have done the following things:

Enabled CIFS services in this SMV
Created same name CIFS server (dh-san-02) on this SVM
Created and applied appropriate export policy
Created separate network interface
Created appropriate DNS records

Now, the \\dh-san-02 is available from the SnapCenter server and SQL server which hosts the SCSQL plugin.

Also, I rediscovered entire cluster in the SnapCenter and restarted SnapCenter service.

No luck (( Same error message...

Went to create the support ticket...

Anyway - thanks for trying to help!