topic Is it possible to exclude User from LastAccessDate? in ONTAP Discussions

Is it possible to exclude User from LastAccessDate?

HansMeier — Wed, 04 Jun 2025 10:08:01 GMT

My Company has written a software that scans all files on the Netapp in the background.

Unfortunately as the software reads all the files on Netapp, the LastAccessTime is overwritten.

So my Question is it possible to exclude a specific user from LastAccessTime?

So that specific user doesn't change the LastAccessTime

Thank your for your help

Re: Is it possible to exclude User from LastAccessDate?

paul_stejskal — Thu, 02 Dec 2021 14:16:01 GMT

Mount NFS with noatime mount option?

Re: Is it possible to exclude User from LastAccessDate?

HansMeier — Fri, 03 Dec 2021 13:34:30 GMT

Unfortunately the application runs on a Windows Server.

We tried it with the following command: fsutil behavior set disablelastaccess 1

This works for files on the Server but not for files on the Netapp Share.

Is there any other option?

Re: Is it possible to exclude User from LastAccessDate?

paul_stejskal — Fri, 03 Dec 2021 15:25:56 GMT

No. Why are you scanning all files? Perhaps we can come up with an alternative.

Re: Is it possible to exclude User from LastAccessDate?

HansMeier — Mon, 06 Dec 2021 16:11:42 GMT

Thank you for your help and quick response time.

We are indexing the content of those files and therefore need to read them.

At the moment our application simply mounts those shares and scans them like any normal network drive.

Is there any option to disable Access Time for the Netapp Share for this particular user?

Re: Is it possible to exclude User from LastAccessDate?

paul_stejskal — Mon, 06 Dec 2021 16:23:32 GMT

I got an idea: mount as a FlexClone. How soon do you need the data to be up to date?

I don't think there is an option unfortunately. Maybe use WSL2 and mount over NFS? I know it works (a bit hacky but works).

Re: Is it possible to exclude User from LastAccessDate?

GidonMarcus — Mon, 06 Dec 2021 21:58:13 GMT

Hi.

Did earlier test, seems that if the user only have read access to the share (didn't check/change NTFS), the attribute does not get updated when the file get opened.

cifs share access-control show -share gidi*
Share User/Group User/Group Access
Vserver Name Name Type Permission
-------------- ----------- --------------------------- ----------- -----------
SVM gidi_test$ Gidi windows Read