Suggestions as to "Best Practice" in multi-PC & NASs setup

Discussion related to "Everything" 1.5.
Post Reply
Michael
Posts: 5
Joined: Tue May 21, 2024 6:20 am

Suggestions as to "Best Practice" in multi-PC & NASs setup

Post by Michael »

Hi all

I'm a bit of a data hoarder, and as such Everything is a godsend. My local network consists of a main PC, spare PC, Windows Hyper-V Core Server and a few NAS boxes. (Well, that's what's getting indexed. Plenty of other PC/devices!) I have many video and audio files (my complete converted CD and DVD collections) and make use of the Properties feature to include info like codecs, height and width in my Everything index.

I naturally started using Everything on just my Main PC, including all the network drives just as UNC folders so that everything, everywhere, got covered. But particularly when I added the Properties to the index things started to slow down a bit on my main PC as it was always busy indexing, plus any time I rebooted I had very big scans occurring, etc.

The Server feature appeared to be my best solution here. Since I can't run Everything on the NAS boxes themselves, I would run it on the Windows Hyper-V Core Server, which almost never gets rebooted. It would be responsible for indexing itself and the NAS boxes, and my main and spare PC would only be responsible to indexing themselves and would link to the Everything Server for all the "network" files.

Is this a correct approach, or am I thinking about this wrong? Because I'm having some issues which makes changing to this difficult.

First issue - it appears that the Properties do not get passed on from the Everything server? So when I start up Everything on the main PC it spends a bucket load of time indexing the properties of the files it added to the index from the Everything server. Is this correct? If so, it would obviously be *wonderful* to have the Everything server expanded to handle passing on Properties as well as basic file data.

Second issue - sometimes the main PC index appears to be out-of-date for NAS file changes, even though if I remote desktop onto the Hyper-V server and do a Everything search there directly all the data is there. The Debug Statistics on the main PC says it things it's up-to-date with the server, so what could I be missing here. Any advice further diagnosing this?

Many thanks,

Michael
Post Reply