Large-Scale File Collection
Automatically collect files from thousands of devices.
Automatically collect inspection results, logs, images and sensor data from industrial equipment and remote servers nationwide into a central server or the cloud. Choose standard, grid, or per-site collection to fit your device scale and network, check collection status and missing files per device, and recover interrupted jobs.
SelectChoose the Factory A group and all 500 devices become collection targets at once.
CollectTransfers run on every device at the same time, gathering inspection results, logs and images into Central Storage.
RecoverInterrupted or missing files are retried automatically on just the affected devices, picking up where they stopped.
CompleteResults from all 500 devices are tallied and the collection job runs to completion.
FLEXIBLE COLLECTION OPERATIONS
Targets, file rules, storage:
one collection job.
Select devices or groups, then set which files to collect and where to store them. Runs start on a schedule or when new files appear, and devices that are offline or interrupted mid-transfer are handled by policy.
- SelectField devices, 100100 devices selected
- Filter*.log, Last 24h18,240 files matched
- CollectTo Central Storage100 / 100 Completed
- RecoveryRetry offline devices3 devices recovered
- AssuranceRequired devicesSatisfied
Select exactly the devices you need
Build the target set from all devices, a group, a region or a device type. However many devices there are, it is one collection job.
Collect only the files that matter
Pick files by extension, path, size and regular expression, and leave everything else out of the collection.
Store in per-device folders
Apply date and device folders and file-name conflict rules so files from different devices never mix or overwrite each other.
Run automatically on schedules and events
Start collection at a set time each day or whenever a new file appears, and retry offline devices according to policy.
USE CASES
Collect the data your devices and
servers produce, in one place.
From inspection results on the factory floor to remote server logs, store terminal operating data and measurement files from research and medical equipment. Gather files scattered across environments into the centre for analysis and operations.
Manufacturing and inspection data
Collect inspection results, measurement data and image files produced by production and inspection equipment into central storage.
Branch and server log collection
Collect logs, operating files and periodic report data from branches and data centres nationwide per site and send them to the centre, with collection schedules and failure recovery managed for each remote network.
Store and remote terminal files
Collect operating files, transaction data and report files stored on stores and remote terminals nationwide into the cloud.
Medical and research equipment files
Send the large images, analysis data and result files produced by inspection and measurement equipment to central storage.
Edge and IoT data collection
Collect sensor data, images and event files produced by many edge systems, with parallel collection or per-site aggregation applied to match data volume and device count.
Remote site backup and evidence
Gather backup files, operational evidence and periodic reports from remote sites and field servers into the centre for retention.
WHY INNORIX
Beyond running
the collection,
verify every result.
Collecting files with FTP, SFTP or per-device scripts means building target management, retries and missing-file checks yourself. INNORIX handles everything from target configuration to per-device runs, recovery and final result verification in one environment.
Central collection instead of per-device scripts
No need to log in to each device and copy files. Create collection jobs for all devices, a group or a single device and run them centrally.
Per-device folders that never mix
Date and device storage rules plus file-name conflict handling mean files with the same name are never overwritten.
One failing device never stops the rest
Offline devices are retried by policy while healthy devices keep collecting. Files already received are never fetched twice.
From completion to final verification
Define required devices, required files and deadlines in an Assurance Contract and judge whether the collection met its conditions.
Daily log collectionRun #1207, 100 devices
Collection results
100/100Completed
- Normal
- 88
- Recovered
- 12
- Failed
- 0
Automatic recovery
12/12Recovered
Only interrupted devices retried
- Interrupted
- Retried
- Recovered
Assurance
Passed
All contract conditions satisfied
- Required devices
- File rules
- Deadline 06:00
- No missing files
EXPLORE THE PRODUCT
Explore every feature fleet-scale file collection needs.
From device registration and groups to collection setup, automatic runs, failure recovery, and result verification: everything for operating hundreds to thousands of devices.
Device registration and groups
See how to bulk-register hundreds of devices and manage collection targets in groups by region, model, and purpose.
Learn moreCollection setup and execution
See how to choose the collection method that fits your device scale and network, from standard to grid and per-site collection, and set up file conditions, schedules, and save rules.
Learn moreLarge and massive file transfer
Learn the transfer technology that reliably collects files over 10TB and huge numbers of small files.
Learn moreLong-distance, high-speed transfer
See how bandwidth is used effectively and transfers accelerated, even from overseas branches and remote devices.
Learn moreFile transfer automation
See how collection runs automatically on schedules, events, and prior-job conditions, and chains follow-up work.
Learn moreMonitoring and file search
See how to track and search run status and missing files, from the whole collection down to each device and file.
Learn moreCollection results and Assurance
Learn how incomplete files and per-device exceptions are handled and the final result verified against success conditions.
Learn moreSecurity and audit
See the available features, from transfer encryption and access control to external security scans, collection history, and audit records.
Learn morePricing and licensing
Compare licenses and terms by device count and deployment, from free testing to enterprise operations across thousands of devices.
Learn moreINTEGRATION & GET STARTED
Run large-scale collection from
your software, devices and AI.
Use the API, SDK, device integration and MCP to bring collection from hundreds to thousands of devices into your existing systems and AI development environment.
Run from software
Integrate the API and SDK into your applications. Pick a device group, create and run a collection job, and query per-device progress and final results.
Start developingRun on hardware
Register industrial equipment and remote terminals in bulk. Specify which files to collect per device model and gather field files into central storage.
Connect devicesRun collection from AI
Connect INNORIX MCP to AI development tools and agents such as Claude Code and Cursor. Run large-scale collection in natural language and check results per device.
Connect AIGET STARTED
Start large-scale file collection today.
FREQUENTLY ASKED QUESTIONS
FAQ: large-scale
file collection
Collection targets and file rules, automatic runs, failure recovery and result verification, integrations and getting started.
Which devices and servers can files be collected from?
Any device connected to INNORIX can be a collection target, from Windows, Linux and macOS servers and PCs to mobile and embedded devices. Whatever the connection method, every device is managed consistently in Studio.
Can files from hundreds or thousands of devices be collected at once?
Yes. You can select connected devices individually or designate a whole group as the collection target. However many devices there are, they are managed as a single collection job rather than many repeated transfers.
Why use INNORIX instead of FTP, SFTP or custom scripts?
Collecting files with scripts means building target device management, retries, missing-file checks and result aggregation yourself. INNORIX creates one collection job for a device group and manages per-device runs and recovery, file-level results and the Assurance verdict in one place.
What environments can be used as the collection destination?
A central server or supported object storage can be designated as the collection destination.
Can only the files I need be collected?
Yes. Select targets by file extension, path, size, regular expression and more, and files that do not match the conditions are excluded from the collection.
Can files be collected from different folders on each device?
Yes. Because targets are selected by extension, path, size, regular expression and more, the paths to collect can be set as conditions and combined into a single collection job.
What happens when files on different devices have the same name?
Rules such as per-device folders, per-date folders and file-name conflict handling can be applied at the destination so files from different devices are never mixed or overwritten.
Can files be collected automatically every day?
Yes. Collection jobs can run immediately or be scheduled hourly, daily, weekly or monthly. Recurring log collection, branch file consolidation, device data backup and more can be automated.
Can collection start automatically when a new file is created?
Yes. Collection can be triggered by events such as a new file being created or a previous job completing.
Can I check collection progress per device?
Yes. See how many devices are collecting and how many are done, plus total volume transferred, and search a specific device for its collection progress and the completed, failed and unfinished status of each file.
What happens if some devices are offline?
Those devices are shown as unfinished or failed in the collection results, and collection on the other devices continues. Per-device results are available in Runs, and whether the job succeeded is judged by the conditions defined in the Assurance Contract.
If collection is interrupted, are already collected files transferred again?
No. When collection is interrupted you can see how far it got; completed files are kept and only missing or interrupted files are transferred again.
Can only the missing files be collected again?
Yes. Even if collection stops on some devices, completed files never need collecting again. According to the configured recovery policy, missing files or the remaining part of interrupted files are transferred again, and the recovery result is reflected in each device’s collection history.
What is an Assurance Contract?
It defines the success conditions of a collection job: required devices, required files, storage location, integrity, deadline and more. INNORIX judges whether the job succeeded by whether the collection result meets these conditions.
Can Assurance fail even if every file was collected?
Yes. Even if collection is technically complete, the Contract is judged failed if the agreed conditions were not met. For example, if a collection with a 06:00 deadline finishes at 06:12, the collection result is Completed but the Assurance Contract is Failed.
Can I find devices that repeatedly cause problems?
Yes. When collection delays or failures keep recurring on a particular device, the run history and device status records can be analyzed together.
Do devices have to be registered one by one?
No. Bulk provisioning applies a prepared installation package and connection settings to devices so many can be connected automatically, and per-device identity and group membership are managed consistently.
Can a device group be used directly as the collection target?
Yes. Groups organized by region, department, device type or purpose can be designated as the collection target instead of individual devices. Devices and groups connected once never need reconnecting for later collection jobs.
Can it integrate with existing systems or external services?
With the API and SDK, existing systems can create and run collection jobs and query per-device status and results. Run status and results can be sent to external services such as Slack and Datadog, and external AI can request collection runs through INNORIX MCP.
Can I switch to production after a free test?
Yes. Start for free, connect real servers and devices, configure and verify collection jobs yourself, then move to the license your enterprise operation needs. See the terms on the pricing and licensing page.