So, I have a large volume file server (7+ TB) that I need to search for about 4 key term phrases. Windows Search index has is disabled on this server. What is the best way to search context on this storage for the key term phrases without overwhelming the server?
Thanks for any valuable ideas.
Large Volume Context Search
Re: Large Volume Context Search
Do you search from a client or on the server itself? One client or multiple?
What do you mean by "context search"? Content search (searching in the content of files)?
Is it possible to install Everything on the server?
What do you mean by "context search"? Content search (searching in the content of files)?
Is it possible to install Everything on the server?
Re: Large Volume Content Search
Sorry, yes, CONTENT search - searching the contents of the file.
I already was able to pull a file name search using the app and dump the files to another drive as requested. The speed of the name search and ability to quickly save impressed greatly. But the request is for ALL things related to these terms - named documents or mentions within documents.
Also, I have installed Everything (latest stable build) on the server. The drive is local on the server, not over network.
I already was able to pull a file name search using the app and dump the files to another drive as requested. The speed of the name search and ability to quickly save impressed greatly. But the request is for ALL things related to these terms - named documents or mentions within documents.
Also, I have installed Everything (latest stable build) on the server. The drive is local on the server, not over network.
Re: Large Volume Context Search
Everything 1.4 - the version you installed on the server - is able to do a content search too, but this information is not saved in the database. Meaning that Everything has to read these files on-the-fly from disk.
You can use the content: function for that. For exampe: content:"some text"
Best practice is to minimize the number of files that have to be read. That can be done by date (dm:last2days), size (size:<100kb) and location ("X:\that folder" | "Y:\that folder") . Put your content:... serach at the end of the query.
See Everything Search Syntax for details and more options.
Everything 1.5 has the option to index file content too, so searches will be instant (no more need to read the files from disk).
But is intended for limited number of files as the entire database will be held in memory (RAM). 1 GB of textfiles will consume approximately the same amount of RAM.
Search these forums for "content indexing" and/or read this for more information.
You can use the content: function for that. For exampe: content:"some text"
Best practice is to minimize the number of files that have to be read. That can be done by date (dm:last2days), size (size:<100kb) and location ("X:\that folder" | "Y:\that folder") . Put your content:... serach at the end of the query.
See Everything Search Syntax for details and more options.
Everything 1.5 has the option to index file content too, so searches will be instant (no more need to read the files from disk).
But is intended for limited number of files as the entire database will be held in memory (RAM). 1 GB of textfiles will consume approximately the same amount of RAM.
Search these forums for "content indexing" and/or read this for more information.