2017-08-24 08:14 AM
Recently I moved a shared folder from a Microsoft File Server over to Netapp. I created an NTFS volume on the Netapp and then Created a Share on the Netapp. Since moving the folder over I've had users complaining that an excel spreadsheet that is accessed by multiple people is not acting the same. When the excel file was on the microsoft file server multiple people could have the spreadsheet open but only the first person could make changes. It would notify anyone who opened the file after the first person that the file was in use and was read only. Since moving the spreadsheet to the netapp, users no longer get the notification if someone else has it open already. Only when they go to save the spreadsheet, it does tell them that someone else has made changes since the last time it was saved. It then asks them if they want to overwrite the other persons changes or if they want to save it as a new document. Neither of these options work. Is it possible to make it work the same way it did on the microsoft server?
Solved! SEE THE SOLUTION
2017-08-24 08:36 AM
The feature you are looking for is called "oplocks". When enabled the client will be able to lock the file to prevent other users to open it.
Unfortunately you didn't specify the mode of operation the system is running (7mode or cDOT) nor the ONTAP version.
Here are links to two guides explaining how to check/set the oplocks parameter depending on mode of operation and version. I hop you find the one that's right for your system.
7-mode - ONTAP 8.2.x:
Enabling or disabling oplocks and lease oplocks on the storage system
Enabling or disabling oplocks on existing SMB shares
If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO or both.
2017-08-24 08:41 AM
Thank you so much for your response. I apologize, we are running 7-mode ONTap 8.2. If I enable this does this mean that users after the first one won't even be able to open the file in read only mode?
2017-08-24 11:25 AM
Enabling oplocks would yield the same behavior as the Windows fileserver.
The first person opens the file and the application sets the lock.
Subsequent users trying to open the file would get a warning that the file is already opened by another user as the application would honor the lock.
So opening the file for reading is still possible, but the file could not be overwritten.