how optimized scan determined modified items

Last post 10-17-2017, 10:27 AM by Christo. 4 replies.
Sort Posts: Previous Next
  • how optimized scan determined modified items
    Posted: 09-15-2017, 5:30 AM


    there are some (not many) Windows Files on C:\ like boot.wim, *.log and Windows.edb (modified Date 2 months ago in browse and restore) which got backed up often. How is the Modified Data gathert trough the optimized scan and how can i verify those files? I thnk the Windows.edb search Catalog Files updates constantly.

    Also some files of Data on E:\ .mp3, 7.z or .pdf are getting backed up and an 6 year old (Modifid Date) Word or PDF file. Which criateria are used for optimized scan to determine and backup these files. Where can i check this? Other Clients dont have this behaviour.

    Thanks for some information.



  • Re: how optimized scan determined modified items
    Posted: 10-12-2017, 11:00 AM

    You can check the files that are backed up in collect* files in JobResults foilder.

    You can read collect files using gxtail.


    - Optimized scan


  • Re: how optimized scan determined modified items
    Posted: 10-17-2017, 9:38 AM
    • Ali is not online. Last active: 03-05-2018, 11:33 PM Ali
    • Top 10 Contributor
    • Joined on 08-05-2010

    Some files even if they haven't change may be protected by the System State backup, browse or restore the job out of place if you want to test out whats in that job or browse it to confirm.

    Also some files are filtered by default from the OS for backup, Commvault will also exclude it, believe things like page files etc.

    In most cases the File System agent will communicate with Windows Change Journal to get the changes and then keep a track of whats changed on the system to be protected or not.

  • Re: how optimized scan determined modified items
    Posted: 10-17-2017, 10:18 AM
    • Aplynx is not online. Last active: 09-21-2018, 4:49 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,410

    Run this command and you can see what the system writer will backup as system protected files which are backedup by the system state only.


    diskshadow /L c:\metadata.txt
    list writers detailed
  • Re: how optimized scan determined modified items
    Posted: 10-17-2017, 10:27 AM

    Thanks for your information. The issue is currently under investigation with the suppport.

    The effect is visible on most machines with optimized scan. Often CV backing up also his old .dll ore something like this which are not modified. I update the Thread if we got an explanation about 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 © 2018 Commvault | All Rights Reserved. | Legal | Privacy Policy