When Drive Bender performs a file system health scan, each file and its location is logged. The log files are a CSV file (i.e. comma delimited text file) and are called HealthMonitorAudit-{POOL_GUID_VALUE}-TIMESTAMP where POOL_GUID_VALUE is a GUID, and TIMESTAMP is a DateTime value expressed as YYMMDDHHMMSS. The file contains the following fields
[24/01/2018 8:11:02 PM] - Messages: Any message associated with the scan.
FilePath: File path of the file, excluding the parent volume.
Timestamp: The timestamp of the file.
Size: The size of the file.
MountPath: The mount path folder.
RootPath: The parent volume.
VolumeName: The volume's volume label.
IsDup: Is the file a duplicate (0 false, -1 true).
FYI - The rootpath is generally expressed as a volume GUID, you can determine the mapping between a given drive letter and volume GUID by running the command "mountvol" from the command line.
What if I cannot find a file (or files) in this log? Drive Bender scans ALL folders at the time of the file system health check, if there are files that are not listed in this log, there were not on the system at the time of the scan. Drive Bender retains 10 versions of this log file, which at the default scan time (approximately once a week), there should be logs going back some 10 weeks.
Comments
0 comments
Article is closed for comments.