INNORIX in Practice / Server & Cloud-to-Cloud Transfer

The company with no one
in charge of file transfer

From Monday morning to a Sunday when no one comes in: a week of data operations inside one company.

Every morning, each team's data is ready. In the afternoon, analysis results move on to other systems, and the day's business data is filed away in its set storage.

At this company, countless files move between servers and clouds every day.

Yet no one comes in to send files, and no one waits for a transfer to finish.

Even after everyone has gone home, even at weekends when no one comes in, the data keeps moving.

So who manages file transfer here, and how?

SUNDAY

03:00

Scheduled

Weekly data archiving

Source
Amazon S3
Target
Linux Archive Server
Run statusRunning
What the company is doing
Day off
People stepping in for file transfer
None
A week of data operations in a fictional company.

INNORIX in Practice

Monday06:00

The company

Every day, teams at this company exchange data.

The company's business systems create new data every day.

The data analytics team collects and analyzes data from several systems, and the service operations team uses the results to run new services.

The data management team keeps the work results from each team, and the infrastructure team manages the company’s systems and storage.

Each team does different work, but each one needs data that lives in another system.

THE COMPANY

The company's data environment

EnvironmentInfrastructureMain role
Business systemsWindows ServerCreates business data
Shared data storageAmazon S3Stores company data
Data analyticsGoogle CloudAnalysis and results
Service operationsMicrosoft AzureUses analysis results
Long-term storageLinux ServerData archiving

Data jobs at the company

Runs whenJob
Daily 06:00Daily business data delivery
Daily 07:00Data prep for analysis
When analysis finishesNew analysis result delivery
Daily 18:00Business results archive
Sundays 03:00Weekly data archiving
When a new file appearsData delivery to downstream systems

The company has set up these data movement jobs in INNORIX.

For each job, it defined in advance the data, the destination, the run conditions, the file selection rules and how to handle exceptions.

Staff can set up transfers for new work or review the results, but they do not run the daily file transfers themselves.

Live contextNow

06:00Monday

Company now
Before work
Transfer job
Daily business data delivery
Run status
Scheduled run
Human action
None

Next

09:00 Workday starts

MONDAY, 06:00

No one is in yet, but the work has begun.

It is 6 a.m. on Monday.

No one has arrived at the office yet. But the teams starting work at 9 a.m. need the data created on the last working day.

Files kept on the company’s business server start moving to Amazon S3.

At 7 a.m., the data the analytics team will use is made ready in Google Cloud Storage.

MONDAY MORNING, INNORIX STUDIO

08:00

Data ready
StartedFlowSizeStatus
06:00Daily business data delivery124 GBCompleted
07:00Data prep for analysis86 GBCompleted
07:30Business reference data delivery12 GBCompleted
Scheduled business data
222 GB
Transferred so far
Transfers run by hand
0
Run on a preset schedule

No one logs in to a server to pick the files to send.

Each transfer job delivers the data it needs according to predefined file selection conditions and save rules.

The transfer job as configured

Flow
Daily business data delivery
Source
Windows Server
Source path
D:\BusinessData\Daily\
Target
Amazon S3
Schedule
Daily 06:00
Include
Business data files
Exclude
Temporary files and files in progress
Save rules
Store in a folder by run date
Recovery
Resume after reconnection

Live contextNow

06:00Monday

Company now
Before work
Transfer job
Daily business data delivery
Run status
Scheduled run
Human action
None

Next

09:00 Workday starts

09:00

People start their work.

At 9 a.m., people arrive at work.

The business operations team checks the new business data, and the data analytics team starts its morning analysis.

No team asks anyone to send files. The data they need is already there.

MONDAY, 09:00

Each team starts the day's work.

Business operations

Today's business data

  • daily_operations.csv
  • business_records.parquet
  • daily_summary.json
Ready at 06:24

Work in progress

Data analytics

Morning analysis data

  • analysis_input.parquet
  • source_dataset.csv
  • historical_records.zip
Ready at 07:18

Analysis in progress

Service operations

Service reference data

  • service_reference.json
  • business_rules.csv
  • reference_data.zip
Ready at 07:34

Service running

No one’s first task is file transfer.

What matters to staff is not which server the data came from or how the files were moved.

It is that the data they need is ready when they need it.

Live contextNow

09:00Monday

Company now
Teams start work
Transfer job
Morning data prep
Run status
Ready
Human action
None

Next

Morning analysis

TUESDAY, 14:32

A new analysis result has been created.

The data analytics team has finished the analysis it started in the morning.

At 2:32 p.m., a new analysis result file is created in Google Cloud Storage.

The company’s service system on Microsoft Azure is waiting for this data.

But the analytics team does not tell the service operations team that the file is there.

TUESDAY, DATA EVENT

14:33:12

Transfer complete

Analytics system

Google Cloud Storage

  • /analytics/results/
  • analysis_result_1108.parquet
  • analysis_result_1246.parquet
  • analysis_result_1432.parquet1.8 GB, created 14:32

Service system

Azure Blob Storage

  • /service/input/
  • analysis_result_1108.parquet
  • analysis_result_1246.parquet
  • analysis_result_1432.parquet1.8 GB, received 14:33

INNORIX, EVENT EXECUTION

Analysis result created eventDetected

Analysis result delivery FlowCompleted

INNORIX runs a transfer to deliver the new result, based on a predefined event condition.

The file appears at a different time each day, but no one has to coordinate a schedule to deliver it.

The transfer job as configured

Flow
Analysis result delivery
Source
Google Cloud Storage
Target
Azure Blob Storage
Trigger
Analysis result file created (event)
Include
analysis_result_*.parquet
Files sent
Files passed by that event
Save rules
Save to the set service input path

The file creation event is set up with the company’s analytics system so that it is sent only after the file has been fully written.

Live contextNow

14:32Tuesday

Company now
Data analysis
Transfer job
New analysis result delivery
Run status
Event-triggered run
Human action
None

Next

Service data processing

14:35

Another team is already using the data.

The service system sees that the new result has arrived and starts downstream processing.

The analytics team moves on to its next analysis, and the service operations team puts the new data to use.

The two teams never had to talk to each other to hand over the file.

THE LIFE OF A FILE

analysis_result_1432.parquet

A 1.8 GB analysis result created in Google Cloud Storage

TimeSystemRecord
14:32:00Data analytics systemAnalysis result created
14:32:04INNORIXFile transfer started
14:33:12Azure Blob StorageFile received
14:35:00Service systemDownstream processing started
From creation to arrival
72 s
Files delivered by hand
0

Live contextNow

14:35Tuesday

Company now
Service operations
Transfer job
New analysis result delivery
Run status
Delivered
Human action
None

Next

Downstream processing

WEDNESDAY, AFTER MIDNIGHT02:14

Something went wrongwhile everyone slept.

INNORIX STUDIO, RUNS

Nightly business data archive

Transferred

68.4 GB

/ 120 GB

Network connection interruptedWaiting

Last connection check: 02:14:08

No one is watching this transfer right now.

On Monday and Tuesday, the scheduled work ran as planned. Now something happens outside normal operations.

INNORIX in Practice

Monday06:00

WEDNESDAY, 02:14

The network connection dropped mid-transfer.

The network connection dropped while nightly business data was moving from Windows Server to Amazon S3.

68.4 GB of the 120 GB has been delivered.

Following a predefined recovery policy, this transfer waits for the connection to come back.

Meanwhile, another transfer job from Google Cloud Storage to Azure Blob Storage is not affected by the outage and keeps running.

INNORIX STUDIO, RUNS

Transfers running at 02:14

FlowTransferredStatus
Nightly business data archiveWindows Server / Amazon S368.4 / 120 GBWaiting for connection
Nightly analysis result deliveryGoogle Cloud / Azure Blob Storage12.8 / 18 GBRunning
Service operations data archiveAzure Blob Storage / Archive Server8.2 / 8.2 GBCompleted

Policy in effect

Wait for reconnection, resume after recovery, alert an admin if the recovery limit is exceeded

One failure does not stop every file transfer at the company.

The affected transfer is handled by its recovery policy, and other independent transfers keep running.

Live contextNow

02:14Wednesday

Company now
After hours
Transfer job
Nightly business data archive
Run status
Waiting for connection
Human action
Waiting within policy limits

Next

Reconnection

02:38

The network connection is back.

Twenty-four minutes later, the network connection comes back.

The interrupted transfer runs again under the preset policy. Data already delivered is kept, and the rest is sent from the last resumable point.

No one logs in to a server, picks the files again from scratch or clicks a transfer button.

INNORIX STUDIO, RUN DETAILS

Nightly business data archive

Resuming
Interrupted
02:14
Resumed
02:38
Completed
—

At 3:16 a.m., all of the data has been delivered.

The operations team will not be in for hours yet.

Live contextNow

02:38Wednesday

Company now
After hours
Transfer job
Nightly business data archive
Run status
Resuming where it stopped
Human action
None

Next

03:16 Transfer complete

09:00

The operations team checks what happened overnight.

People have arrived at work.

Reviewing the results of the night’s transfer jobs, the operations team learns that the network failed in the early hours.

They can see when the failure happened, how long it lasted and how it was handled.

INNORIX STUDIO, RUN DETAILS

Nightly business data archive

Completed
Size
120 GB
Connection drops
1
Final recovery status
Recovered

Execution history

TimeEventStatus
01:45:00Transfer startedRunning
02:14:08Network connection interruptedWaiting
02:38:02Connection restoredRecovered
02:38:04Transfer resumedRunning
03:16:00Transfer completedCompleted
Final result
All data delivered
Manual reruns
None

The operations team checks whether any work was affected and, if needed, looks into the cause of the network problem.

But no one has to run the transfer again to finish the delivery.

Live contextNow

09:00Wednesday

Company now
Reviewing the night
Transfer job
Nightly business data archive
Run status
Completed after recovery
Human action
Reviewing results

Next

Network cause review

THURSDAY, 11:20

The destination is out of storage.

It is 11:20 a.m. on Thursday.

While business data is moving to the company’s long-term storage server, the server runs out of space.

This server keeps data from several teams every day, and a separate storage management job clears old temporary data on a regular cycle.

For now, the transfer has nowhere to write more data.

ARCHIVE SERVER

Storage capacity

Insufficient space

20 TB / 20 TB

0 GB free

  • Archived business data 16 TB
  • Temporary data 4 TB

Transfer job now running

Business data archiving

Data still to store
1.2 TB
Status
Waiting for storage
Existing storage cleanup job
Scheduled for 12:00

For cases like this, the company set a policy that holds the transfer until space is freed.

INNORIX does not keep sending files that cannot be stored, and it does not delete existing data on its own.

If no space is freed, the policy marks the job as needing review by the operations team.

Live contextNow

11:20Thursday

Company now
Day-to-day work
Transfer job
Business data archiving
Run status
Waiting for storage
Human action
Waiting within policy limits

Next

12:00 Storage cleanup

12:10

Storage space has been freed up.

The storage management program the company already runs starts on schedule.

Under the company’s storage policy, 4 TB of expired temporary data is cleared.

With space freed up, the waiting file transfer runs again.

ARCHIVE SERVER

12:46

Data archived

17.2 TB / 20 TB

2.8 TB free

  • Existing archived data
  • Temporary data
  • Newly delivered data
  • Free space
JobStatus
Existing storage cleanupCompleted
Business data archivingCompleted
Manual rerunNone

At 12:46 p.m., the remaining 1.2 TB is archived.

The storage management program did its part, and INNORIX finished delivering the data.

While the two systems each did their job, no one had to run the file transfer again.

Live contextNow

12:10Thursday

Company now
Day-to-day work
Transfer job
Business data archiving
Run status
Resumed once space was freed
Human action
None

Next

Transfer complete

FRIDAY, 17:00

How much got done this week?

On Friday afternoon, the operations team reviews the results of the week’s data work.

Since Monday, some transfers ran on a fixed schedule, and others ran as new data was created.

There was also an unexpected connection drop and a storage shortage.

The team does not log in to each server to check transfer records or gather logs from several programs.

It checks the results for the period in INNORIX.

THIS WEEK, MONDAY — FRIDAY 17:00

This week's data transfer jobs

Total transfer runs
117
Scheduled runs
30
Event-triggered runs
87
  • Scheduled
  • Event-triggered

Final results

Completed normally
115
Recovered after an exception
2
Unresolved failures
0
Run by hand
0
Manual reruns
0

Fictional operations record up to 5 p.m. Friday.

Of the 117 transfer runs, 2 ran into problems along the way, but both finished under the predefined policies and recovery conditions.

Instead of delivering files, the operations team is reviewing the state of the company’s data operations.

Live contextNow

17:00Friday

Company now
Weekly ops review
Transfer job
Transfer results and exceptions
Run status
Reviewing results
Human action
Reviewing results

Next

Weekend scheduled jobs

17:10

So what does the operations team need to check?

The operations team still has plenty to do.

It sets up file transfers for new business needs, reviews existing transfer policies and looks into the causes of recurring problems.

When needed, it changes run conditions, file selection rules and exception policies.

WEEKLY OPERATIONS REVIEW

This week's exceptions

WhenWhat happenedOutcome
Wed 02:14Network connection lostRecovered
Thu 11:20Out of storageRecovered

What INNORIX does

  • Runs transfers on schedule
  • Delivers new data
  • Selects and saves files as configured
  • Handles exceptions by policy
  • Records results and history

What the operations team does

  • Sets up new data operations
  • Decides company policy
  • Reviews results and warning signs
  • Finds the cause of infrastructure issues
  • Fixes problems beyond automatic recovery
Delivering files and managing a company's data operations are different jobs.

This company does have people who manage its data operations.

But it does not assign anyone to carry out the routine file transfers.

Live contextNow

17:10Friday

Company now
Ops policy review
Transfer job
Transfer results and exceptions
Run status
Reviewing results
Human action
Reviewing results

Next

Weekend scheduled jobs

EVERYONE HAS GONE HOME, FRIDAY EVENING18:00

The company's week is over.The data operations week isn't.

UPCOMING RUNS

Run timeJobStatus
Fri 18:00Business results archiveScheduled
Sat 06:00Service operations data deliveryScheduled
Sat 18:00Service results archiveScheduled
Sun 03:00Weekly data archivingScheduled
Sun 22:00Next week's business data prepScheduled
Mon 06:00Daily business data deliveryScheduled

Data jobs that will run before people are back on Monday.

People head home, wrapping up the week’s work.

But the company’s service systems keep creating new data over the weekend, and next week’s data still has to be prepared.

The operations team does not put anyone on a weekend file transfer rota for this work.

INNORIX in Practice

Monday06:00

SUNDAY, 03:00

Even on a day no one comes in, the data moves.

It is 3 a.m. on Sunday.

A job starts that moves the week’s business data, service operations results and analysis results to the long-term storage server.

Under the company’s retention policy, data for the set period is selected and saved to that week’s archive path.

SUNDAY, 03:00

Weekly data archiving

Source

Amazon S3

  • business-data/1.2 TB
  • service-results/640 GB
  • analytics-results/480 GB
  • weekly-reports/80 GB

Target

Linux Archive Server

  • /archive/2026/
  • week-43/
  • week-44/
  • week-45/
  • week-46/This week's data archived

Weekly archive

Completed
Started
03:00
Size
2.4 TB
Completed
05:42

The new week’s data is archived under the same policy as last week.

Next week, the following week’s data is selected, and the same job repeats after that.

No one on the operations team has to come in on a day off to deliver files.

Live contextNow

03:00Sunday

Company now
Day off
Transfer job
Weekly data archiving
Run status
Scheduled run
Human action
None

Next

Next week's data prep

22:00

Getting ready for a new week.

It is 10 p.m. on Sunday.

The business reference data and service operations data needed the next morning start being prepared.

Every team at the company will start new work on Monday morning.

PREPARING FOR MONDAY

Monday 08:00

Next week's dataUsed byStatus
Business reference dataBusiness operationsCompleted
Service reference dataService operationsCompleted
Weekly analysis dataData analyticsCompleted
Daily business dataBusiness operationsCompleted

When the teams start work next

Monday 09:00

All scheduled data ready

Live contextNow

22:00Sunday

Company now
Day off
Transfer job
Next week's business data prep
Run status
Scheduled run
Human action
None

Next

Monday 09:00 Workday starts

NEXT MONDAY, 09:00

The company starts a new week.

It is 9 a.m. on Monday.

People arrive and start their work.

Last week’s work is archived, and the data for the new week is ready.

The data analytics team starts new analysis, and the service operations team puts the new data to use.

Just like a week ago, nobody’s first task is file transfer.

MONDAY, 09:00

What happened at the company last week

DayCompany workData operations
MondayA new week beginsBusiness data prepared
TuesdayData analysis and useAnalysis results delivered
WednesdayDay-to-day businessNight connection failure recovered
ThursdayWork and results archivingResumed once space was freed
FridayWeekly operations reviewTransfer results and exceptions checked
SaturdayDay offService data delivered
SundayDay offWeekly archiving and next week's prep
What the company did
Analysis, services, operations, decisions
What INNORIX did
Delivered the data the business needed
The company starts a new week.And the work of delivering the data it needs starts again.

Live contextNow

09:00Next Monday

Company now
A new week begins
Transfer job
Daily business data delivery
Run status
Ready
Human action
None

Next

The new week's work

ANOTHER WEEK BEGINS

From Monday to Sunday,the company's data kept moving.

TypeMonTueWedThuFriSatSun
Company workWorkWorkWorkWorkWorkOffOff
File transfer5 transfer runs6 transfer runs5 transfer runs6 transfer runs5 transfer runs3 transfer runs4 transfer runs

Scheduled runs, event-triggered runs, exception recovery, data archiving

People came to work and did their jobs.

They went home, and rested at the weekend.

Meanwhile, the data went where it was needed.

People do the business.INNORIX moves the data.

THE TECHNOLOGY BEHIND THIS STORY

Server & Cloud-to-Cloud Transfer

Deliver the data each team needs between different servers and clouds, and run file transfer jobs automatically according to company policy and business schedules.

Explore the product