NetApp Configuring SnapDrive for Windows with ONTAP

You are here:
< All Topics

The following is an abbreviated procedure for configuring NetApp SnapDrive for Windows with Clustered ONTAP. The full article can be found at How to configure SnapDrive for Windows with clustered Data ONTAP.

Before you begin, check the compatibility matrix and review the alerts and informational notices for the SDW entry in the Interoperability Matrix Tool.

Configure the SVM

  1. Set a password for the vsadmin account and save it for later reference. Run the following command to set the password for the SVM admin user:
    ::> security login password -username vsadmin -vserver <vserver_name>
  2. Run the following command to unlock the vsadmin account:
    ::> security login unlock -username vsadmin -vserver <vserver_name>
  3. In the storage system, create a SVM management LIF with the data protocol set to NONE and the firewall policy set to MGMT.Note: Data LIFs cannot be added to SnapDrive as preferred storage system IP addresses.
    ::> net int create -vserver <vserver_name> -lif <lif_name> -role data -data-protocol none -home-node <node_name> -home-port <port_name> -address xx.xx.xx.xx -netmask xx.xx.xx.xx -status-admin up -firewall-policy mgmt
  4. Ensure that an A record and associated PTR record exist in DNS for the SVM management LIF and that the record is associated uniquely with the management LIF IP address. If necessary, create an A record and an associated PTR record in DNS.Note: If CIFS is enabled on the SVM, the CIFS name registered with DNS must be different from the SVM name, because CIFS traffic cannot use the SVM management LIF you created in Step 3. It is highly recommended that NAS (CIFS/NFS file services) be separated from SAN services in separate SVMs.
  5. From a client machine, validate forward and reverse DNS works for the SVM management LIF.

Configure the Windows Server(s)

  1. Verify that DSM and the Host Utilities Kit is installed, as appropriate, for direct-connected iSCSI or FCP LUNs prior to installing SDW. It is recommended to use the native Microsoft DSM is used. However, you can install the Data ONTAP DSM.Related Links:
  2. Install SnapDrive on the server, or if part of a Windows Failover cluster – all nodes of the Windows Failover cluster.
  3. The SnapDrive service account must be a member of the Local Administrators group. If you install SnapDrive in a Windows Failover Cluster environment, you must use the same DOMAIN USER account as the service account on each node the Windows Failover Cluster.Related Link:  What are the required capabilities for SnapDrive for Windows service account?
  4. Add a preferred storage system IP address for the vServer management LIF in the SnapDrive GUI or from the SnapDrive CLI:
    C:\> sdcli preferredip set –f <hostname> -IP <ip address>
    C:\> sdcli preferredip list

    Note: If SnapDrive is to be used for Management, you cannot use a NetBIOS (clustered Data ONTAP 8.3) to mount the SMBv3 CIFS shares.

  5. Verify that the default transport settings are disabled, and adjust the default transport settings to use HTTPS or HTTP and specify the vsadmin credentials:
    • In the SnapDrive management snap-in, right-click hostname and select Transport Protocol Settings > Default. Verify that the default settings are disabled.
    • In the SnapDrive management snap-in, right-click hostname, select Transport Protocol Settings > Storage Systems, and click Add. Add the vServer name that you configured above with the vsadmin username and password that you configured earlier.
  6. Perform the following steps in SnapDrive in order to fully test SnapDrive function:
    • Create a disk
    • Create a snapshot
    • Delete a snapshot
    • Create a FlexClone
    • Delete a FlexClone
    • Delete the disk
Table of Contents