Hi,
I'm a sysadmin looking to implement Azure File Sync Cloud Tiering for an on-prem server, hoping to reduce local storage needs by having less frequently used files reside only in the cloud storage until needed by a user on-prem at which point it downloads ... basically turning a giant file server into just a local cache for 'warm' files.
However - apparently some depts in my organization are using Everything to index and search content on this server, so I'm concerned that the indexing activity will continuously update the access dates on files and prevent them from ever ageing-out of local storage, even if nobody as truly accessed the file interactively for 5 years ... thus defeating the purpose of the exercise.
I was wondering if anybody has tried this, or knows if Everything indexing causes files to appear recently accessed?
Does indexing alter 'date accessed'?
Re: Does indexing alter 'date accessed'?
Everything uses the FindFirstFile API to scan folders.
FindFirstFile does not modify date accessed.
Everything may update date accessed when loading icons for visible results.
(Typically, loading icons will not update date accessed)
To disable icon extensions:
Everything uses the Master File Table to index NTFS volumes.
Indexing NTFS volumes will not modify date accessed.
FindFirstFile does not modify date accessed.
Everything may update date accessed when loading icons for visible results.
(Typically, loading icons will not update date accessed)
To disable icon extensions:
- Copy and paste the following into your Everything search box:
/icon_shell_extensions=0 - Press ENTER in your Everything search box.
- If successful, icon_shell_extensions=0 is shown in the status bar for a few seconds.
Everything uses the Master File Table to index NTFS volumes.
Indexing NTFS volumes will not modify date accessed.