Search files scattered across many devices from one place
Not remembering which server or cloud store a file sits on should not mean logging into each device and digging through folders. In INNORIX Studio, group paths across several devices into a Dataset and see the searchable file information in one place. Once you have the filename and the location, open that path on the device and carry on into the transfer you need.
Cómo se construye
- Connect the devices you want to search.
In Studio Devices, register internal servers, branch devices and supported object storage, and confirm you can reach the folders you need.
- Set the search scope as a Dataset.
In Datasets, define the devices and paths you want to search as a single Dataset. Restrict which folders are included according to the work and the permissions involved.
- Open the file information for the Dataset.
Go into the file list or the search available on that Dataset and confirm the search scope is set correctly.
- Search by filename and compare the results.
Search for
quality-report, for example, and review the information actually provided for the files found on each device — name, path, size, modified time. - Pick the file you want and use it.
Check the source device and path on the result, then, if you have access, open the file in the explorer to confirm it or transfer it to another device. A search result on its own does not download the file.
Dónde se usa
- Finding quality inspection files across factories
When you do not know which factory server holds an inspection report, search by filename in a Dataset that groups the per-factory folders and confirm where the original sits.
- Confirming the latest report per branch
When several branches hold a report with the same name, compare device, path and modified time to pick the branch you want. Where you need to be sure a result really is the latest version, verify the file information at the source again.
- Finding distributed project output
Project files spread across the design server, the simulation server and the archive server are found by filename or folder and sent to the server the next stage needs them on.
- Checking file locations before a device is replaced
Before an old server is retired, search for which device still holds a given set of work files and review what needs to move and what could be missed. Folders outside the search scope have to be checked separately.
- Locating files between cloud and internal servers
Across internal servers and supported object storage, confirm which store holds the file you need and decide what to transfer without copying it twice.
- Finding the relevant logs during an incident
Log files containing an incident number or a system name are found across several devices so the owner can confirm the original path and modified time. This is distinct from searching inside the log text.
- Checking distributed data before you use it
Compare output files that share a filename across several research and analysis servers, then pick the original you need and send it to another processing device.
Guías de uso
Preguntas frecuentes
Is there a way to search files scattered across many servers in one go?
INNORIX Studio is a platform for working with distributed files by composing devices and paths into a Dataset. Using the file information and the search on a Dataset, you can design a way of working that finds file locations across devices from one place. Which search conditions and search targets are actually supported has to be confirmed on the version you deploy.
Can I find files on servers and in cloud storage on one screen?
INNORIX can connect server devices and supported object storage, and a Dataset groups several locations logically. Which stores, paths and metadata are searchable, though, can vary with the connection method and the product features.
Do all the files have to be copied to a central server before I can search them together?
A Dataset is a logical grouping of file paths across different devices, so it does not assume a structure where everything is copied to central storage just to be searchable. How the metadata used for search is maintained, and how files are actually read, has to be confirmed against the product implementation.
Can it search file contents as well as filenames?
This guide covers search centred on filenames, locations and basic file information. Full-text search inside PDFs and documents, OCR and semantic search are separate features and are not assumed to be supported by default.
How do I tell apart files with the same name on different servers?
What matters is composing the results so you can compare the information provided — source device, full path, modified time, size. The same filename does not mean the same contents, so deciding whether two files really are identical may need separate verification such as a hash.
Can I send a file I found straight to another server?
Once a search result has given you the location, and if you have access to that device, you can carry on into the Studio explorer or a supported transfer job and send it to another device. Whether the result screen itself carries a transfer button has to be checked against the UI of the product version you run.
Do new or modified files show up in search results immediately?
When results refresh depends on how file information is read, the indexing interval and the connection state of the device. This guide does not guarantee that a file change on any device is reflected in search results instantly. For files that matter in production, confirm the final state at the source.
Can the servers and folders each user can search be limited differently?
What can be searched should be limited to match device access rights and the scope of the Dataset. Confirm how per-organisation permissions and the exposure policy for search results are applied in the actual product before you bring sensitive paths into the search scope.