File Transfer
Large File Transfer
Introducing INNORIX Large File Transfer, which transfers files as-is regardless of size and continues from the point of interruption.
File Transfer
Transfer Large Files to Completion with the Same Workflow.
There is no single file size that defines a large file. Even a 500 MB file can become a significant transfer burden when it must be sent repeatedly or across an unstable network. With videos measuring tens of gigabytes, research data in the hundreds of gigabytes, and terabyte-scale datasets, transfer time and the cost of retransmission after a failure become much greater.
- 500MB
- 50GB
- 1TB
- 10TB+
- INNORIX Large File Transfer
- Target
INNORIX Large File Transfer transfers original files as they are, resumes after interruptions, and operates everything from hundreds of megabytes to terabyte-scale datasets with the same Transfer and Operation Model, rather than adding a separate workflow for each file size.
File Transfer
Large File Transfer Starts with Transfer Burden, Not a Specific File Size.
A 500 MB file may be ordinary in one environment, but repeatedly sending the same file to a remote site or transferring it across an unstable network can turn the transfer itself into an operational burden. As files grow from tens or hundreds of gigabytes into the terabyte range, transfer time, progress visibility, retransmission after failure, long-distance network utilization, and final completion verification all become increasingly important.
Large File Transfer is therefore less about switching to a different product above a particular size threshold and more about extending the required Transfer Capabilities within the same architecture as file size and operational demands increase. INNORIX operates large-scale data movement based not only on file size, but also on actual transfer duration, recovery cost, network conditions, and transfer frequency.
File Size, What Becomes Important in Transfer
- Transfer Time
- Recovery Cost
- Network Dependency
- Operational Visibility
- Large File Transfer Capability
File Transfer
Transfer the Original File Directly from Source to Target.
Manually splitting or compressing a large file before transfer and then reassembling or extracting it at the target creates preparation and restoration work beyond the transfer itself. As files become larger, these manual steps add complexity not only to transfer time but also to operational procedures and result verification.
INNORIX lets you select the original file at the source and transfer it directly to the target. Where the transfer path allows, Control and Monitoring are handled by the Platform while actual Data Movement is established between the required Source and Target, reducing architectures that repeatedly move the same large data through an Intermediate Server or Shared Storage.
No Manual Splitting, No Pre-Compression, No Reassembly Work
Manual Workflow
- Large File
- Split / Compress
- Intermediate Transfer
- Reassemble / Extract
- Verify
INNORIX
- INNORIX Platform — Control Plane
- Source
- Target — Original File, Data Path
File Transfer
Recover Interruptions and Repeated Failures Within the Same Transfer.
The larger the file, the longer a transfer can run and the greater the cost of starting over when something goes wrong. Across long-distance WANs, remote sites, and unstable networks, connection changes or packet loss may occur multiple times during a single transfer. Preventing one interruption from becoming a complete retransmission is critical to reducing actual completion time.
INNORIX maintains Transfer State and uses Resume, Partial Transfer, Retry, and Recovery so the transfer can continue from the required point based on data that has already been completed. Multiple interruptions are managed as part of the completion process of one large-file transfer rather than as separate new transfers.
1TB Transfer
- 0% – 78%
- Interrupted
- Resume
- Recover
- Interruption
- Recover
- 100%
File Transfer
Turn Network and Storage Capacity into Actual Large File Throughput.
Even with high network bandwidth, a large-file transfer may not fully use the available capacity. Actual throughput is determined together by latency and RTT, packet loss, source storage read performance, target storage write performance, other traffic, and the transfer method.
When a single session cannot use the full available capacity, INNORIX applies Parallel Sessions and Dynamic Concurrency and operates the transfer according to the processing capabilities of the source and target. Rather than looking at a single network number, it treats Source Read → Transfer Processing → Network → Target Write as one End-to-End Performance Path and turns the capacity that can actually be used into File Throughput.
Transfer Condition, Impact on Throughput
- Source Storage — 3 GB/s
- Parallel Transfer — Session 1, 2, 3, 4
- Network — 10 Gbps
- Target Storage — 800 MB/s
File Transfer
Operate Transfer Capacity Across Long Distances, Multiple Networks, and Shared Infrastructure.
Actual performance can differ substantially between transfers inside the same data center and transfers across countries or continents, even on the same 10 Gbps network. As distance increases, RTT and packet loss have a greater impact, and a single connection may struggle to use all available bandwidth. When the source and target have multiple network interfaces or paths, capacity across multiple connections can also be used for Data Movement.
At the same time, enterprise networks are not dedicated exclusively to file transfer. Applications, databases, backups, and user traffic share the same network, making overall capacity allocation and operation as important as the peak speed of an individual transfer. INNORIX uses Parallel Transfer, Dynamic Concurrency, and Queue management to use available capacity across long-distance and Multi-Network environments while operating multiple transfers within the existing infrastructure.
LOCAL
- Server A
- Low RTT
- Server B
LONG DISTANCE
- Seoul
- High RTT
- New York
MULTI-NETWORK
- Source
- Network 1
- Network 2
- Network 3
- Target
Shared Infrastructure
- Applications, Database, Backup, User Traffic
- Queue, Concurrency, Capacity
File Transfer
Scale from One Large File to Multiple Large Transfers and Mixed Datasets.
Large File Transfer does not always mean moving a single file. Multiple users may send large files at the same time, multiple servers may deliver large datasets, or a single dataset may contain hundreds of gigabytes of video alongside thousands of metadata files, large models, and supporting files.
INNORIX manages not only the throughput of an individual large file but also Queue, Concurrency, and Source and Target Capacity when multiple transfers run simultaneously. For datasets that combine Large File and High-Volume characteristics, processing can be adapted to file size and file count while the entire job is managed as a single Run.
Data Profile, Transfer
- Source A, 500GB
- Source B, 1.2TB
- Source C, 280GB
- Source D, 3.4TB
- Queue / Concurrency
File Transfer
Track Progress, Integrity, and Final Results as One Completion Process.
When a multi-terabyte file has been transferred over a long period, simply knowing that a process has ended may not be enough. Operators need to know how far each file was transferred, whether Recovery occurred during the transfer, and whether all required files ultimately completed with the expected result.
INNORIX provides progress visibility through Run and File Status, handles issues during transfer through Recovery, and lets operators verify the final state through File Result and Receipt after completion.
RUN-1842
- RUN-1842
- Receipt
It connects how quickly the data arrived and whether the required file actually completed successfully as one Transfer Operation.
File Transfer
Connect Recurring Large File Transfers to Automation and Flow.
A large-file transfer may be a one-time migration or a dataset delivery repeated every day or every week. The same Large File Transfer should be able to start not only through manual execution in a Console, but also through a Schedule, File Event, API, or request from an existing workflow, with its completion result connected to the next business process.
INNORIX uses the same Transfer Engine across On Demand and One-Time Transfer, Scheduled and Event-Driven execution, API, and Flow. This turns large-file transfer from a separate manual task into a repeatable capability for enterprise data movement.
Execution Method, Use
- Dataset Ready
- Large File Transfer
- Result
- Next Flow / Callback
File Transfer
Apply the Same Large File Transfer from Servers to Object Storage and AI Compute.
Large files do not move only between servers. Source and target combinations continue to change across Data Center-to-Cloud migration, AI datasets delivered from Object Storage to Compute, software and media distributed between headquarters and branches, and Results and Checkpoints returned from Compute to Storage.
The industries and workloads may range from Media/VFX, AI, Research, Healthcare, Engineering, Geospatial, and Backup/Archive to Manufacturing, but the core requirements remain the same: move large files, sustain long-running transfers, and verify the final result. INNORIX applies the same Large File, Resume, Recovery, and Result Transfer Model across different endpoint types and extends the same capability to Server-to-Server, Object Storage, Web, Distribution, and AI Data Delivery.
Transfer, Typical Data
- Source
- INNORIX
- Server
- Cloud
- Object Storage
- Data Center
- Branch
- AI Compute
File Transfer
Keep the Same Transfer and Operation Model as File Size Grows.
Instead of building a separate transfer environment for each file size or workload, large-file transfers can use the same operating model as other Data Movement on the INNORIX Platform. Whether the starting point is Manual Transfer, Flow, API, or an AI Platform, the same Large File Transfer Engine is used, and operational status and results remain visible through Runs and Monitoring, File Status, and Receipt.
10 TB is not the threshold at which a file becomes "large." It is one point in a Scale Test used to verify how far the Transfer Architecture can handle increasing file sizes in the same way. Depending on the operating environment, transfer burden may begin at only a few hundred megabytes. What matters more than a specific number is whether the same Transfer, Recovery, and Operation Model can be maintained as files grow.
Scale, Meaning
- 500MB
- 100GB
- 1TB
- 10TB+
- Same Transfer, Recovery, Operation Model
File Transfer
Extend Transfer Capability as File Size Grows.
Transfer original files as they are from business files measuring hundreds of megabytes to terabyte-scale datasets, use Parallel Processing to take advantage of available network capacity, and continue the same Transfer after interruptions through Resume and Recovery.
Apply the same Large File Transfer across Servers, Cloud, Object Storage, and AI Compute, connect recurring work through Automation and Flow, and verify final results through Run and Receipt.
Every one of these capabilities,on a single platform.
The capability on this page is one of the many file transfer features INNORIX Platform provides. From file transfer to automation and unified operations, try every feature free.
Start FreeConsidering large file transfer?
We'll help you review a stable large file transfer setup that fits your file size and transfer environment.
- Review of environments from GB to TB-scale files
- Transfer configuration that accounts for pause and resume
- Guidance on automating recurring large file transfers