High-Speed File Transfer

Collection and distribution, long-distance and sequential transfer, web upload and download. Every transfer on the INNORIX Platform runs on the same high-speed transfer engine. However it is started and wherever it is headed, the technology that moves data fast works across the whole platform.

It handles multiple sessions and data segments at once, and tunes the transfer to the performance the network and the storage have available. You set up the transfers your work needs; the engine turns the performance each environment can give into actual data movement.

Data moves directly between the source and the target, without passing through an intermediate server. There is no separate work to split or compress a large file before sending it, or to merge and decompress it after it arrives.

Recurring transfers run automatically on a schedule or an event, and an interrupted one recovers from the remaining segments or the failed files. On top of high-speed transfer, the savings in preparation, relays, waiting and rework bring forward the moment the data arrives and the work is done.

The INNORIX high-speed transfer engine reads the state of the network together with the capacity the source and target storage have to spare. It allows for the latency and loss of a long route and for bandwidth shared with other work, adjusts the transfer sessions and the concurrency, and turns the performance available in the current environment into actual data movement.

Operators are spared retuning the settings for every environment, and transfers carry on as conditions change. It works over the connections already allowed, with no extra UDP ports to open, so there are no new security exceptions to manage for a new transfer route.

You point at the large original file, and that is all. The INNORIX high-speed transfer engine splits it into data segments for transfer and joins the received data back together, so there is no separate work to split or compress the file beforehand, or to merge and decompress it after it arrives.

If the network connection drops or a server or storage has a temporary problem, the data already received correctly stays as it is. The transfer resumes automatically from the interrupted segment, and the result is verified through to a clean completion. A long-running large transfer finishes reliably without the whole file being sent again.