Start Free

LARGE FILE & MASSIVE FILE TRANSFER

10TB files, 100M files,
and no starting over.

Transfer ultra-large single files and vast numbers of small files reliably. If a transfer is interrupted by a network outage, device reboot or lack of storage, completed data is kept and only what is needed is sent again.

Single file transfer
10TB+
Small files in one transfer
100M
Interruption and recovery test cycles
1,000
Studio / Runs

LARGE FILE TRANSFER

Even a multi-terabyte file goes as one piece, with no splitting.

Transfer very large files such as backup images, raw high-resolution video, research data and database dumps.

Single files over 10TB are supported, and if the connection drops during a long transfer it resumes from the point of interruption.

Studio large file transfer

MASSIVE SMALL-FILE TRANSFER

Tens of millions of files, handled as one transfer job.

Transfer vast numbers of small files such as images, logs, sensor data and documents in one batch.

Up to 100 million files per transfer are supported, and completed and incomplete files are kept separate to ease recovery of massive transfers.

Studio massive file transferRun status

INTERRUPTION & FAILURE RECOVERY

Network down, device rebooted, and the completed data is still there.

In large and massive file transfers, recovery after an interruption matters as much as speed. Depending on the failure type, INNORIX waits, reconnects, resumes or selectively retries to avoid unnecessary duplicate transfers.

Recovery by failure type
FailureRecovery
Network disconnectedResume from interruption after reconnecting
Server or device rebootRecover incomplete transfers after reconnection
Out of storage spaceWait until space is available, then resume
Device offlineResume when the device reconnects
Some files failedRetry failed files, excluding completed ones
Repeated unstable connectionInterrupt and recover as the connection allows

SELECTIVE RETRY

If 30 of a million files failed, resend just those 30.

When only some files in a massive transfer fail, there is no need to resend the ones that completed normally.

Only the failed files are identified and retried, cutting recovery time and network usage.

Studio per-file transfer resultsSample run

UNSTABLE NETWORK RESILIENCE

The transfer keeps going even where the connection keeps dropping.

In environments with unstable connectivity, such as branch offices, remote devices, maritime and satellite networks, the transfer can interrupt and resume repeatedly.

It reduces unnecessary retransmission caused by unstable networks and raises the likelihood of completion.

Unstable network, durability test

30% packet loss and 1,000 disconnections are durability test conditions. They do not guarantee the same transfer speed or completion time in a production environment.

TRANSFER ACROSS ENVIRONMENTS

The same applies to server, cloud and device transfers.

Large and massive file transfer and recovery are not limited to one environment. They apply to server-to-server transfer, Object Storage integration, fleet-scale distribution and collection, and more.

Studio / Runs
EnvironmentTypical use
Server ↔ ServerLarge backups, data migration
Server ↔ Object StorageBulk data upload and download
Cloud ↔ CloudMove files between different Object Storage services
Central ↔ Many devicesBulk file distribution and result collection
Remote site ↔ Data centerData transfer over unstable networks

FREQUENTLY ASKED QUESTIONS

Frequently asked questions about
large and massive file transfer

How large a file can INNORIX transfer?

Single files over 10TB are supported. Large backup images, raw video, research data and other big files can be transferred without splitting them.

Can it transfer tens of millions, or 100 million, files?

Small-file transfers of up to 100 million files are supported. A massive set of files is handled as one transfer job, with completed and failed states kept separate.

If the network drops during a large file transfer, does it start over from the beginning?

No. For recoverable network interruptions, the data already transferred is kept and the transfer resumes from the point of interruption.

Can a transfer recover after a server or device reboots?

Where transfer state is preserved, incomplete transfers can be recovered after the device reconnects.

What happens if a transfer stops because storage runs out?

It can be configured to wait until space is available and resume the remaining transfer once the recovery conditions are met.

If only some of a million files fail, do I have to resend them all?

No. Files that completed normally are kept, and only the failed files are retried.

Can it transfer under heavy packet loss or repeated disconnections?

It is designed for repeated interruption and recovery, with durability test scenarios such as 30% packet loss and 1,000 interruptions. Actual performance depends on the network environment.

Can I search failed files and retry results?

In Studio Runs you can check transfer results and search per-file status and retry results.

Does it work with Object Storage or transfers between many devices?

It applies to transfers between servers, Object Storage, cloud and many devices. The specific transfer configuration depends on the product and connection environment.

EXPLORE PRODUCTS

Where do you need large and massive file transfer?

Servers and cloud, field devices, software and websites. Choose the product for the environment where you will use INNORIX large-file transfer and interruption recovery.