The usual way
Transferred by way of intermediate storage
SourceIntermediate storageTarget
- Stored in between, then moved again
- Extra storage space required
- Longer transfer time
SERVER-TO-SERVER FILE TRANSFER
Wherever your servers are,
files transfer directly.
Connect servers in different environments, from Windows and Linux to the data center and the cloud, on a single platform. Browse files without logging into each server separately, and transfer the data you need directly by choosing a Source and a Target.
A simple file copy, a large data move, a repeating transfer between several servers: all of them are handled the same way. Transfer progress and completion results are visible in one place, which makes moving files between servers simpler to operate.
/data/inspection
NameSizeModified
%20--%3e%3c!DOCTYPE%20svg%20PUBLIC%20'-//W3C//DTD%20SVG%201.1//EN'%20'http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd'%3e%3csvg%20version='1.1'%20id='Layer_1'%20xmlns='http://www.w3.org/2000/svg'%20xmlns:xlink='http://www.w3.org/1999/xlink'%20x='0px'%20y='0px'%20width='42px'%20height='36px'%20viewBox='0%200%2042%2036'%20enable-background='new%200%200%2042%2036'%20xml:space='preserve'%3e%3cdefs%3e%3cfilter%20id='Adobe_OpacityMaskFilter'%20filterUnits='userSpaceOnUse'%20x='0.688'%20y='0.811'%20width='40.625'%20height='34.375'%3e%3cfeColorMatrix%20type='matrix'%20values='1%200%200%200%200%200%201%200%200%200%200%200%201%200%200%200%200%200%201%200'/%3e%3c/filter%3e%3c/defs%3e%3cmask%20maskUnits='userSpaceOnUse'%20x='0.688'%20y='0.811'%20width='40.625'%20height='34.375'%20id='mask0_1465_251'%3e%3cpath%20fill='%23FFFFFF'%20filter='url(%23Adobe_OpacityMaskFilter)'%20d='M41.313,0.811H0.688v34.375h40.625V0.811z'/%3e%3c/mask%3e%3cg%20mask='url(%23mask0_1465_251)'%3e%3cpath%20fill='%23F7AC35'%20d='M2.908,0.951C2.423,1.108,1.97,1.373,1.61,1.733c-0.281,0.281-0.5,0.61-0.672,0.97%20C1.297,1.858,2.017,1.201,2.908,0.951z'/%3e%3cpath%20fill='%23F7AC35'%20d='M16.298,1.715c-0.438-0.422-0.985-0.719-1.58-0.844C15.313,0.996,15.86,1.278,16.298,1.715z'/%3e%3cpath%20fill='%23FFBF7B'%20d='M40.391,7.982c-0.578-0.578-1.375-0.921-2.203-0.921h-37.5v25.125c0,0.797,0.313,1.563,0.875,2.125%20s1.328,0.875,2.125,0.875h34.672c0.781,0,1.531-0.313,2.078-0.859c0.563-0.547,0.875-1.297,0.875-2.078V10.186%20C41.313,9.357,40.984,8.576,40.391,7.982z'/%3e%3cpath%20fill='%23F7AC35'%20d='M21.641,7.061H0.688V3.92c0-0.203,0.016-0.406,0.063-0.594V3.295C0.797,3.107,0.859,2.92,0.922,2.748%20c0.016-0.016,0.016-0.031,0.016-0.047c0.172-0.359,0.391-0.687,0.672-0.969c0.359-0.359,0.813-0.625,1.297-0.781%20c0.297-0.094,0.594-0.14,0.906-0.14h10.297c0.203,0,0.406,0.031,0.609,0.062c0.594,0.125,1.141,0.422,1.578,0.844L21.641,7.061z'/%3e%3c/g%3e%3c/svg%3e)
imagesApr 21, 09:15- logsApr 21, 09:21
- reportsApr 21, 09:23
inspection_data_001.dcm1.2 GBApr 21, 10:24- inspection_data_002.dcm1.1 GBApr 21, 10:20
- inspection_data_003.dcm1.3 GBApr 21, 10:18
summary.csv8.4 MBApr 21, 09:12
/archive/inspection
NameSizeModified
- 2024Apr 21, 09:15
- 2025Apr 21, 09:21
- archiveApr 21, 09:23
- inspection_data_001.dcm1.2 GBApr 21, 10:24
- inspection_data_002.dcm1.1 GBApr 21, 10:20
- inspection_data_003.dcm1.3 GBApr 21, 10:18
training_data.zip2.4 GBApr 21, 08:56
DIRECT DATA MOVEMENT
No storage in between,
server to server, directly.
There is no need to store a file on an intermediate server and forward it to its destination the way the old approach did: it transfers straight from Source to Target. Cutting out needless data copies and staging steps keeps the transfer path simple.
The file data itself moves between the servers, while the INNORIX Platform manages the run, the progress and the result centrally. Large files and repeating server-to-server transfers get the same efficient data movement and consistent operation.
INNORIX direct transfer
Straight from server to server
SourceTarget
INNORIX PlatformControl & MonitoringMonitoring
- Direct transfer with no storage in between
- Unnecessary data movement kept to a minimum
- Transfers set up and monitored centrally
SERVER CONNECTIVITY
Different servers,
the same way to transfer.
Windows and Linux, on-premises and cloud, head office and branch: servers in different environments are connected into one transfer environment. Whatever the operating system or where it is installed, you browse and transfer files through the same interface.
When a new server is added, the existing transfer method and operating procedure carry over unchanged. There is no separate transfer tool or management approach per server environment, so moving files across distributed servers stays consistent.
OPERATING SYSTEM
Linux ↔ Linux
Browse the files on separate Linux servers and transfer them directly.
SupportedMajor distributions
CROSS PLATFORM
Linux ↔ Windows
Servers running different operating systems are handled in one transfer environment.
SupportedWindows Server
ON-PREM & CLOUD
Data Center ↔ Cloud
Connects file movement between on-premises servers and cloud servers.
SupportedMajor clouds
DISTRIBUTED ENVIRONMENT
Headquarters ↔ Branch
Connects servers on separated networks, such as headquarters and branch offices.
SupportedRemote networks
CENTRALIZED TRANSFER MANAGEMENT
Every server’s transfers,
watched and managed in one place.
There is no need to start and check transfer jobs server by server: every server-to-server transfer is managed on one screen. Source and Target, file count and volume, progress and run state are all visible as they happen, and a job that runs into trouble is easy to spot.
Reuse the server connections and transfer settings you use often, and set up new jobs in the same place. Transfer history and completion results are kept together, so the overall picture stays clear as servers and jobs multiply.
Transfer Overview
2 Running13 Completed1 Failed4 Scheduled
TransferSource → TargetFilesSizeProgressStatus
Research DataResearch-01 AI-Cluster12,8492.8 TB100%Completed
Daily BackupBranch-02 Data Center8,4211.2 TB100%Completed
- Source
- Branch-02 /backup/daily
- Target
- Data Center /vol/backup
- Transfer details
- 8,421 · 1.2 TB · 100%
Media AssetsMedia-01 Cloud Storage2,340480 GB38%Retrying
Inspection FilesProduction-01 Archive-0256,2316.4 TB0%Scheduled
Firmware PackageBuild-02 Branch-071,20496 GB68%Running
RESUME & RECOVERY
Interrupted transfers resume,
and only the failed files are sent again.
When a network or server failure hits part way through a large file or a great many files, there is no need to start over. The files that already finished are kept, and an interrupted file resumes from the part that is left.
If only some files failed, only those are sent again; files that arrived correctly are not processed twice. You can follow the retry and the recovery and verify the final result, so even a long-running server-to-server transfer finishes reliably.
Server TransferProduction-01 Cloud-Compute
Completed
Total files12,842
Completed12,842
Failed0
Remaining0
File nameSizeProgressStatus
dataset_part_01.zip12.8 GB100%Completed
dataset_part_02.zip12.8 GB100%Completed
dataset_part_03.zip12.8 GB100%Completed
dataset_part_04.zip12.8 GB100%Completed
dataset_part_05.zip12.8 GB100%Completed
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 server-to-server file transfer?
We'll help you review a direct transfer setup that fits your current servers and network environment.
- Review of On-Prem, Cloud, and Hybrid environments
- Proposal for a server-to-server Transfer Path setup
- Guidance on recurring transfer and operational automation