What is the health monitor, and how does it work?

The Drive Bender health monitor performs a number of checks against the pool to ensure all is as it should be.

The following details what checks are performed, and what actions are taken if an issue is found.

• Primary and duplicate file audit. The count and byte size usage are determined for both file types.
• Folder check: For each folder in the pool, a check is made on each other drive to ensure the same folder exists. If not a warning is generated and the folder is created.
• File primary check, multiple primaries. For each primary file in the pool, a check is made to ensure this same file does not exist on the other drives in the pool (this excludes the duplicate file). If more than one primary is found, the following action is taken depending on the registry setting "HM Action Multiple Primarys" (DWORD). Note if the registry value is missing, the default is enforced.
  * 0: Reserved.
  * 1: A warning is generated.
  * 2: (default) The file is renamed to filename(X), where X is a numerical value starting at 1.
  * 3: The file is deleted (not recommend).
  * 4: The pool switches to read-only mode.
• File duplication check, duplicate missing: For each file flagged for duplication, the duplicate file is checked to make sure it exists. If the file is missing, validation is scheduled on that file (the validation action will re-duplicate the file).
• File duplication check, attribute check. For each file in the pool flagged for duplication, the duplicate file's attributes are checked against the primary file to ensure they are the same. If not, validation is scheduled on that file (the validation action will re-duplicate the file).
• File duplication check, orphaned duplicate: For each duplicate file, a check is made for the corresponding primary file. If not found, the following action is taken depending on the registry setting "HM Action Orphaned Duplicate" (DWORD). Note if the registry value is missing, the default is enforced.
  * 0 (default): No action taken
  * 1: A warning is generated.
  * 2: The orphaned file is deleted (not recommend).

For versions v2.3.8.0 and v2.3.9.0, the file system health check is run once straight after startup then every 7 days thereafter.
For v2.4.0.0, it runs every 7 days only regardless of restarts.

If you wish to manually start the health check, see - http://divisionm.zendesk.com/entries/32766459-How-do-I-manually-start-the-file-system-health-monitor-