Dossier data collector files failed to scan

Frank Wilkinson

• April 07, 2020 19:38

1. In the Scan Summary I see “Total number of paths failed to scan” and “Total number of files failed to scan.”  Can you explain these failures further, or are there some switches I can throw to the application to see more verbose logging?  Would I need to add the “failed to scan” files to the “Total number of files scanned” to derive at the accurate total number of files on the system?
2. In the Scan Summary I also see “Estimated post-compression size” and “Estimated post de-duplication size.”  Is there a way to see what the total size would be after both compressing and de-duping, rather than just individually?  Or would I just calculate that myself using the de-dup percentage against the total post-compression size?
3. Are there switches I can use to tell the application to not follow hard links and junctions?

 

0

• 

  Live Optics Agent

  • April 08, 2020 13:29
  • Edited

  Hi Frank,

  Thank you for your questions. Please check below for answers:

  1. The number of failed paths shows a count of directories that Dossier was unable to open and read. Usually, this indicates that the user running dossier lacks the appropriate permissions to access the directory. In very rare cases, the error could be attributed to an IO error associated with the network or underlying disks. If paths on network file shares contain illegal characters, this can also cause these errors.
     
     The number of failed files indicates errors when a file was opened for the purposes of compression and dedup testing but could not be opened or read for some reason. Usually, this indicates that the user running dossier lacks the appropriate permissions to access the file. It also could be that the file is opened and locked by another process. In very rare cases, the error could be attributed to an IO error associated with the network or underlying disks. In the Windows Dossier collector, retrieving the meta data access times from individual files can also cause errors. If filenames contain illegal filename characters, this can also cause errors.
  2. No, we do not have a tool that will estimate the size after both compressing and de-duping at the moment. 
  3. The Windows collector sees hardlinks and symbolic (soft) links as regular folders files and cannot distinguish them from regular folders or files. 
     The soon to be released Linux collector can identify symbolic links, and it will always ignore them. However, it will treat hard links as regular folders/files and follow them normally.

   

  Hope the above answers your questions. If you have any further questions, please let me know.

  0

Please sign in to leave a comment.