Skip to main content
NetApp Knowledge Base

Does ONTAP support CIFS/SMB NDO?

Last Updated:

Applies to



  • NDO is Nondisruptive Operation, which is a fundamental capability of clustered Data ONTAP
  • Due to the fact CIFS/Server Message Block (SMB) being a STATEFUL protocol, it would still prevent continuous data availability in some nondisruptive operations
  • With the introduction of newer versions of SMB & clustered Data ONTAP, some improvements have been implemented
    • SMB1.0 could not survive a network outage due to the inherent limitations of the protocol without durable or persistent file handles
    • SMB2.0 introduces durable handle, an open file handle which is preserved during a short network outage so that the client may reconnect when the network comes up
    • In clustered Data ONTAP 8.2, NDO for SMB 3.0 is introduced for Microsoft HyperV environments with Continuously Available (CA) File Shares to better support NDO, which could provide better continuous data availability

Below is a chart of CIFS/SMB NDO Overview:

                       NDO                        SMB 1.0               SMB 2.x and SMB 3.0         SMB 3.0(Hyper-V only)
               LIF migrate                      Disruptive                   Nondisruptive              Nondisruptive
              Volume move                     Nondisruptive                   Nondisruptive              Nondisruptive
             Aggregate relocate                     Disruptive                   Disruptive              Nondisruptive
            Storage failover                     Disruptive                   Disruptive              Nondisruptive
  • Note: Applications connected to SMB 2.x file shares might still incur a disruption when the application allows multiuser access to the same file or for applications that do not pick up an open file handle within 15 minutes from when the LIF migrate was executed
  • In other words, even with durable handle enabled in SMB 2.0 or later, it could still prevent continuous data availability as durable handle might not be successfully granted
    • For detailed information, see TR-4100.

Additional Information



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.