Start Free

MASS FILE DISTRIBUTION & COLLECTION

Even Across Hundreds of Machines,
Distribute and Collect in One Go.

Distribute one file to many servers and machines, or collect the files produced across many sites into the center.
Run the transfer in INNORIX Studio and manage it as a single job, from each target's progress to the final completion result.

Runs5 runs, latest first

All

Flow / RunTransferStatusFilesSize

firmware_rolloutHQ-BUILD-01 → 24 devicesCompleted100%2,4009.7 GB

Log collection12 devices → LOG-COLLECT-01Completed100%3,6304.2 GB

Configuration syncCFG-MASTER-01 → 8 devicesWaiting0%01.1 GB

Dataset transferNAS-BACKUP-01 → 4 devicesTransferring43%6,3691.2 TB

Release distributionSG-CDN-ORIGIN → 3 devicesCompleted100%314.46 GB

FILE DISTRIBUTION

Distribute to Hundreds of Machines,
and Resend Only What Is Unfinished.

Distribute software updates, configuration files, AI models and datasets to many servers and machines at once. Name the files and the Target Group, and the whole distribution is managed as one job while you watch each target’s progress individually.

If a network failure or a transfer error hits some machines, the targets that already finished are kept and only the failed machines and files are sent again. You can confirm every target received the files it needed, so even a large distribution reaches a final completed state with nothing missing.

software-v42.pkgRelease 42, 12 GB

Completed

SOURCE

Production Serversoftware-v42.pkg

TARGETS (3/3)

  • Branch ASeoulCompleted
  • Branch CDaeguCompleted
  • Branch EGwangjuCompleted

300/ 300 Targets completed

100%Completed 300

FILE COLLECTION

Gather Data from Many Machines,
and See What Is Missing.

Collect the files produced by many Sources, from factory equipment to research instruments and branch servers, into central storage. Set a storage path and file selection conditions per machine, and compose data created in different places as a single Collection.

See for each machine whether collection is complete, what data is still waiting, and which files arrived only in part. Identical file names or differing directory structures are no obstacle, because data is kept apart by Source, so beyond simply gathering files you can verify that everything needed was collected.

Daily Collection2024. 10. 15, Production Data

Completed

SOURCES (4)

  • Factory AInspection DataCompleted
  • Factory BMachine LogsCompleted
  • Server DApplication LogsCompleted
  • Device ESensor DataCompleted
Central CollectionProduction Data

24/ 24 Sources collected

100%Completed 24

ENDPOINT MANAGEMENT

Group Countless Machines Into One,
and Manage Distribution and Collection Together.

Organize branches, factories, servers and machines into Groups by the work they do. Check each target's readiness and the version it has been given, and operate the distribution and collection of many machines in one environment.

As the number of target machines grows, the concurrent transfer count and the queue are managed to fit your network and server capacity. Large files and great numbers of files are handled across many machines at once, while the full distribution and collection scope and each machine’s progress stay on one platform.

Global292

  • Headquarters12
  • Branches120
  • Factories80
  • Servers50
  • Devices30

R&D48

QA36

Global InfrastructureEndpoints organized by workload

GroupEndpoints
Headquarters12
Branches120
Factories80
Servers50
Devices30

COMPLETENESS

From the Whole Job Down to a Single File,
Confirm What Has Finished.

Check the result of a distribution or a collection run, and trace it from the state of each target down to the delivery and verification result of an individual file.

RunWhole run

Release 42Distribution, software-v42.pkgCompleted

100%

Started 2024. 10. 15 14:32, 4 targets

EndpointResult by target

  • Branch ACompleted
  • Branch BCompleted
  • Branch CCompleted
  • Branch DCompleted

FileResult by file

  • software-v42.pkgDelivered
  • config.jsonDelivered
  • manual.pdfDelivered
  • readme.txtDelivered

CompletionCompletion checkCompleted

  • File integrity verified
  • Run result and history stored

Faster than an explanation: try it yourself.

Connect the devices and build the distribution flow.

Add flowCancelSave draftSave & active

Flow canvas

Daily · 02:00HQHQ-BUILD-01TOKYO-EDGE-07EdgeTOKYO-EDGE-01OSAKA-EDGE-02NAGOYA-EDGE-03SAPPORO-EDGE-04FUKUOKA-EDGE-05TOKYO-EDGE-06

0 devices · 1 step

Configuration

Start when

NowSchedule

Every day · 02:00

Source

HQ-BUILD-01

Target

Choose target

GET STARTED

Now put it to work in your application.

TECHNICAL FAQ

Frequently asked questions

Can one file be distributed to many devices at the same time?

Yes. You can build a distribution flow that delivers a file from one source to many targets. How many actually run at once depends on the environment and the settings.

Can files created at several sites be collected to a central server?

Yes. You can build a collection flow that brings files from several source devices to a central system.

Can it be used with hundreds or thousands of devices?

Distribution and collection can be built for large numbers of devices. The appropriate device count and the performance have to be verified against the network, the file sizes, the device specifications and the concurrency policy.

If the transfer fails on some devices, does the whole run have to start again?

It can be set up to separate completed targets from failed ones and follow up only on the targets that need it. The specific re-run method follows the Runs features and your policy.

How are devices that are offline or in use handled?

Depending on the target state and the execution policy set, they can be treated as waiting or as failed. Behaviour after reconnection has to be confirmed against the waiting and retry policy.

Can I see the progress of each distribution target?

Yes. Studio shows the transfer state and the completion result for each target.

Can I see which devices or files were missed during collection?

It can be set up to show the collection result per source and whether the files needed were delivered. How far a miss can be identified depends on how the collection targets are defined and on your verification policy.