Commvault affect on last accessed time stamp (Windows Server 2016)

Last post 05-06-2019, 1:38 PM by jszutarski. 1 replies.
Sort Posts: Previous Next
  • Commvault affect on last accessed time stamp (Windows Server 2016)
    Posted: 05-03-2019, 4:14 PM

    We currently have the file access time stamp enabled on our file servers. We want to be able to use the last accessed time stamp to find old files that arent being used anymore but it seems like when a backup is performed, it will modify the time stamp. I contacted support, but they seem to think otherwise. I verifyed by looking at a few random files. I can see that when I check the file properties that the last accessed date falls in line with when the last full backup ran. 


    Reading the documentation here:


    It seems like we would have to use recursive scanning to preserve the last accessed time stamp? Currently our file server clients are setup to use Change Journal scans. Does anyone have any insights into this or know what the best aproach would be? We have 4 file servers and they all have millions of files spread accross multiple volumes. Recursive scans are recommended for content that has a small number of files and folders according to avanced subclient properties. 

  • Re: Commvault affect on last accessed time stamp (Windows Server 2016)
    Posted: 05-06-2019, 1:38 PM

    Yes, Recursive scan will allow you to use the "preserve file access time" option. If you find that the recursive scan option is causing backups to run longer, you may want to break down the subclients into smaller sets to try and see if that helps expedite backups.

    Also, A/V may be modifying file access times as well, so you may want to double check that.

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Copyright © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy