Anyway to prevent intermittent indexing, or to back up the index so it doesn't have to be completely rebuilt?

[bruce656]

Every once and a while, I will start up Everything Version 1.5.0.1383a (x64), and it begins to completely rebuild the index, a process which will take QUITE a long time (20+ hours), as I have many file properties selected to be indexed, and this can hold my work flow up.

1) What causes the index to be rebuilt, and what can I do to avoid this, and
2) is there a way I can back up the index so that when this does happen, I could hopefully restore it to a previous point so it doesn't have to be rebuilt from scratch?

[void]

Please check Tools -> Debug -> Statistics -> Build -> Last Rebuild Reason

Everything will automatically save your index to disk daily.
This can be configured under Tools -> Options -> Advanced -> db_auto_save

[bruce656]

it says "Out of date NTFS volume F: is available"

I see the flags for the db_database are set to automatically save on exit, and to save every four hours, as well as to to make a backup of the database. Is it possible to restore the backup as opposed to having to rebuild it? Should I set it to save more frequently? Every 1 hour? 30 minutes?

[void]

Too many changes occurred on your F: while Everything was not running.
(or something deleted the USN Journal on your F: drive)

Please try increasing the USN Journal size on your F: drive:

• In Everything, from the Tools menu, click Options.
• Click the NTFS tab on the left.
• Select your F: drive.
• Change the Maximum Size to: 131072 KB
• Click OK.

Is it possible to restore the backup as opposed to having to rebuild it?

No.
The Everything index would be out of sync.

Should I set it to save more frequently? Every 1 hour? 30 minutes?

I do not recommend saving your index too frequently.
Saving daily should be more than enough.