The fact that the files flooding the indexing logs are not meant to be used directly by end users but are part of Hyper Backup's processes suggests to me that it isn't necessary to be indexing these directories. If you don't have a specific need to index the backup directories, then the system will be spending a lot of time and resources indexing directories that don't need this. To this end, my recommendation would be to omit the backup directories from the indexing. If you are running regular backups to this particular directory - and if the other device experiencing this behavior also has a similar backup directory that is likewise updated frequently/regularly - then the indexing process may be running but is spending a lot of time on these backup files. One thing that can make the indexing process take a long time to complete or seem to never complete is directories that change a lot or that change on a very regular basis. However, I can see that the indexing logs are flooded with indexing messages related to files that appear to be associated with Hyper Backup tasks in the "Complete Image Mirror" directory on that NAS. Here's the pertinent exerpt from the trouble ticket: My bad-I have two that seem to be having this issue-and the directories are both connected to the Hyper Backup application.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |