Skip to main content
NetApp Knowledge Base

Can ONTAP CIFS clients survive a LIF migrate?

  1. Last updated
  2. Save as PDF
Views:
2,482
Visibility:
Public
Votes:
3
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • Data ONTAP 8
  • ONTAP 9
  • CIFS/SMB

Answer

Yes, under certain conditions, LIF migration is non-disruptive for SMB 2.0 and later. 

  • SMB 1, client sessions become disconnected during network outages.
  • SMB 2.0 and 2.1, the use of durable file handles allows the session to reconnect without any impact to the application:
    • Durable Handles(enabled by default for SMB2.x):
  • SMB 1 is unable to prevent lock state from being lost during network outages. SMB 2 addresses this need with durable handles: file handles that are preserved by the client and can be used to reestablish disconnected sessions.
  • Note: Although durable handles are nondisruptive for volume moves and LIF migrations, they are not mirrored across nodes, and a failover (or an upgrade) of a node results in the lock state being lost. SMB 3’s persistent handles improve upon SMB 2 durable handles by mirroring lock state across nodes in a cluster.
  • For more information, please read TR-4543 starting page-6

WARNING:

  • Durable/persistent file handles are exclusive to a single-file open.
  • Non-disruptive behavior might be affected when multiple users are accessing the same file. 

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.