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

In three years, the data the company
handles grew 100-fold.

From a company handling 100 GB a day to one putting 10 TB a day to work: how data operations change as a business grows.

Three years ago, this company created about 100 GB of data a day.

One data center and a handful of servers were enough for most of its work.

Then the business widened, new services launched, and more teams started working with data.

New servers arrived, and several clouds came into use. Data the company had never kept became an important asset.

Three years on, the company creates 10 TB of new data every day.

It is not only the size that changed. Where data is made, where it is used, and the work that needs it have all changed too.

When data grows 100-fold, how must data operations change?

THREE YEARS OF GROWTH

2026, Data created per day

100 GB

2029, Data created per day

10 TB

  1. 2026Existing businessOn-premises
  2. 2027New service launchAmazon S3
  3. 2028Analytics expandsGoogle Cloud
  4. 2029AI and global businessAzure, GPU Servers

10 TB a day, and a far wider business environment

A story built on the changes a fictional company sees in its data operations over three years of growth.

INNORIX in Practice

2026Nov

Background, November 2026

Three years ago, few teams used data.

In November 2026, the company ran most of its business systems in its own data center.

Data from the business systems went to a separate work server, and some of it was saved to storage for long-term keeping.

The data was mostly business records and information needed to run the business. It was clear which teams created data and which used it, and new transfer jobs were rarely added.

THE COMPANY, NOVEMBER 2026

Data created per day
100 GB
Infrastructure
1
Teams using data
2

On-premises Data Center

Business systems

Windows Server

Creates business data

Data processing

Linux Server

Uses business data

Long-term storage

NAS Storage

Keeps past data

What the company creates each day

  • Business records45 GB
  • System logs30 GB
  • Service data15 GB
  • Business reports10 GB

At the time, the company had no dedicated analytics team and no AI team.

Data was used mainly to do the work and record its results.

But the next year, a new service launched and the company’s data environment began to change.

Live contextNow

A company handling 100 GB of data a dayNovember 2026

Data created per day
100 GB / day
vs. 2026
1×
Active Flows
4

Infrastructure

  • On-premisesIn operation

Teams using data

  • Business ops teamUsing data
  • System ops teamUsing data

Current focus

Existing business operations

NOVEMBER 2026, AN ORDINARY BUSINESS DAY, November 2026

A company handling 100 GB of data a day

Every evening, the company gathers the data its business systems created that day.

Some of it goes to a Linux server for the next day’s work, and some is saved to NAS storage for long-term keeping.

Only a few transfer jobs had to run on a schedule.

INNORIX STUDIO, FLOWS

Regular data operations in 2026

FlowSourceTargetSchedule
Daily business dataWindowsLinux18:00
Service recordsWindowsLinux20:00
Daily archivesLinuxNAS23:00
Weekly archivesWindowsNASSunday

DAILY BUSINESS DATA

75 GB

Completed
Started
18:00
Finished
18:12

Moving data was not a special project. It was routine work, repeated every day.

Data volumes were predictable, and business systems and data destinations rarely changed.

Three years later, the company looks very different.

Live contextNow

A company handling 100 GB of data a dayNovember 2026

Data created per day
100 GB / day
vs. 2026
1×
Active Flows
4

Infrastructure

  • On-premisesIn operation

Teams using data

  • Business ops teamUsing data
  • System ops teamUsing data

Current focus

Existing business operations

MARCH 2027, A NEW BUSINESS BEGINS, March 2027

The company launched a new online service.

It is March 2027.

For a new line of business, the company launched an online service.

Usage could grow fast, so instead of expanding the existing data center, the new service team chose Amazon Web Services.

Data created by the service is stored in Amazon S3.

But not all of the new service’s work happens in the cloud.

The business operations team needed the new service’s usage records and sales data, and the new service needed product and reference data kept in the existing data center.

MARCH 2027, A NEW SERVICE ENVIRONMENT

Existing environment

On-premises

Business operations

110 GB

Data created per day

New environment

Amazon S3

Online service operations

140 GB

Data created per day

Newly added data jobs

DatasetSourceTarget
Product reference dataWindows ServerAmazon S3
Online transactionsAmazon S3Linux Server
Service usage recordsAmazon S3NAS Storage
Company-wide data per day250 GB

The system operations team connected the new cloud and added data jobs that had not existed before.

The transfer jobs already running in the data center stayed as they were.

A new service was added, but the company did not have to rebuild its whole data operations setup.

Live contextNow

A new online service launchesMarch 2027

Data created per day
250 GB / day
vs. 2026
2.5×
Active Flows
7

Infrastructure

  • On-premisesIn operation
  • Amazon S3Newly added

Teams using data

  • Business ops teamUsing data
  • System ops teamUsing data
  • Online service teamNewly added

Current focus

New service launch

ONE YEAR LATER

The data grew tenfold,but the hours of the work that uses it did not change.

November 2026

100 GB

Data created per day

November 2027

1 TB

Data created per day

INNORIX in Practice

2026Nov

NOVEMBER 2027, TEN TIMES MORE DATA, November 2027

The new service grew faster than expected.

Eight months have passed since the service launched.

More customers use it, and it offers more kinds of content.

Usage records, customer-created data, processing results and system logs began piling up far faster than before.

A year ago the company created 100 GB of data a day. Now it creates 1 TB a day.

The business operations team still starts work at 9 a.m.

The daily business report still has to be ready at the same time.

But the new service no longer creates data only when the workday ends.

As long as customers are using the service, new data keeps coming.

The company decided to switch some of its daily data jobs to hourly, repeating transfers.

DAILY DATA OPERATIONS, ONLINE SERVICE

Same work, a new way data is created

ItemBeforeAfter
ScheduleDaily at 20:00Every hour
What is sentData completed that dayData completed that hour
Used byBusiness ops teamBusiness ops team
DestinationLinux ServerLinux Server

More data did not simply mean sending more of it at once.

The company changed the transfer schedule based on when data is created and when the work needs it.

Handling 1 TB of data a day gradually became the company’s new normal.

Live contextNow

The service grows faster than expectedNovember 2027

Data created per day
1 TB / day
vs. 2026
10×
Active Flows
9

Infrastructure

  • On-premisesIn operation
  • Amazon S3In operation

Teams using data

  • Business ops teamUsing data
  • System ops teamUsing data
  • Online service teamUsing data

Current focus

Running the new service

APRIL 2028, DATA BECOMES SOMETHING MORE, April 2028

Data that was only stored started being used.

In April 2028, the company set up a new data analytics team.

Management wanted to use the business data built up over the years to see the state of the business in more detail.

How customers use the service, results by product, operations by hour of day: data that had never been analyzed was now needed for new work.

The analytics team chose Google Cloud as its analytics environment.

But the data the team needed was not in Google Cloud.

Some of it was kept in the existing data center, and some was still being created in Amazon S3.

NEW DATA ANALYTICS TEAM

Data requested by the analytics team

DatasetCurrent locationSizeRequired
Business recordsOn-premises8.4 TBHistorical
Customer activityAmazon S312.8 TBHistorical
Service usageAmazon S3640 GBDaily
Product dataLinux Server80 GBDaily

ANALYTICS ENVIRONMENT

Google Cloud Storage

Initial analytics data

21.2 TB

One-time transfer

Daily analytics data

720 GB

Repeating transfer

Data that used to just sit in long-term storage now had a new destination.

Two jobs were set up: one to send the 21.2 TB already in storage to the analytics environment, and one to send 720 GB of new data every day.

The company’s data is no longer used only to record its work.

It is now used to analyze past work and prepare for future business.

Live contextNow

Stored data starts being analyzedApril 2028

Data created per day
2.2 TB / day
vs. 2026
22×
Active Flows
13

Infrastructure

  • On-premisesIn operation
  • Amazon S3In operation
  • Google CloudNewly added

Teams using data

  • Business ops teamUsing data
  • System ops teamUsing data
  • Online service teamUsing data
  • Analytics teamNewly added

Current focus

Analytics begins

SEPTEMBER 2028, MORE THAN JUST LARGER FILES, September 2028

More changed than just the size of the data.

By September 2028, the company was creating 3.5 TB of data a day.

But it is not simply that the average file got bigger than three years ago.

Some work produces datasets hundreds of GB in size. Other work produces hundreds of thousands of small files.

The types, sizes and timing of files from different systems also became more varied.

THE CHANGING NATURE OF DATA

Files the company creates in a day

Large analytics data

Analytics results and business datasets made of large files

Many small files

Service usage records, logs, images and small business files

Data typeFiles per dayData per day
Large datasets18990 GB
Service records and logs840,000860 GB
Service content120,0001.25 TB
Other business data24,000400 GB

Files created per day

984,018

Data created per day

3.5 TB

The analytics team needs large datasets.

The service operations team needs huge numbers of logs and small business files.

There is no need to put all of this data into the same transfer job.

The company runs separate data jobs based on the kind of data each team actually uses and when it needs it.

Live contextNow

More work comes to rely on dataSeptember 2028

Data created per day
3.5 TB / day
vs. 2026
35×
Active Flows
23

Infrastructure

  • On-premisesIn operation
  • Amazon S3In operation
  • Google CloudIn operation

Teams using data

  • Business ops teamUsing data
  • System ops teamUsing data
  • Online service teamUsing data
  • Analytics teamUsing data

Current focus

Analytics expands

NOVEMBER 2028, THE PAST IS NEEDED AGAIN, November 2028

240 TB of data stored for years was suddenly needed.

The results of the analytics project began to be used in other parts of the business.

To analyze longer-term business trends, the company decided to send years of stored data to the new analytics environment.

The data came to 240 TB in total.

Some of it was in the company’s own data center, and some was kept in Amazon S3.

But the company could not stop its regular work just to move 240 TB.

New data is still being created today, and each team needs its data at set times.

HISTORICAL DATA PROJECT

Historical data and today’s data

Data built up over years

240 TB

On-premises
96 TB
Amazon S3
144 TB

A one-time project, sent in parts

New data created every day

3.5 TB

  • Online service data
  • Business and analytics data

Regular daily work

Two kinds of work in the same period

The system operations team split the 240 TB of historical data into several transfer jobs by period and storage location.

Regular business data keeps moving on its usual schedule. The large historical transfers run in separate time slots, sized to the network and storage the daily work needs.

The team planned operations so that moving historical data would not drop or delay any of today’s business data.

New data keeps coming while the project runs.

Six days have passed since the project started.

Of the 240 TB of historical data, 168 TB has reached the analytics environment.

In the same period, the company created 21 TB of new data.

The part of it the analytics team needs was also sent to Google Cloud every day.

INNORIX STUDIO, RUNS

Historical data project, Day 6

168 TB / 240 TB

70%

Overall project progress

Transfer jobTransferredStatus
Historical data, On-premises72 / 96 TBRunning
Historical data, Amazon S396 / 144 TBRunning
Daily analytics data720 GBCompleted
Hourly service records48 GBCompleted
Daily business data240 GBCompleted

New data created during the project

21 TB

Regular business work

Still running

A new project that uses historical data does not make the existing work go away.

The company’s data operations are a mix of jobs with different purposes and different schedules.

Live contextNow

Putting 240 TB of historical data to useNovember 2028

Data created per day
3.5 TB / day
vs. 2026
35×
Active Flows
23

Infrastructure

  • On-premisesIn operation
  • Amazon S3In operation
  • Google CloudIn operation

Teams using data

  • Business ops teamUsing data
  • System ops teamUsing data
  • Online service teamUsing data
  • Analytics teamUsing data

Current focus

Historical transfer alongside daily work

MARCH 2029, A NEW PURPOSE FOR DATA, March 2029

The company started developing AI.

In March 2029, the company started an AI project built on its own data and business knowledge.

The new AI development team set up a training environment on GPU servers.

The data this team needed was not gathered in one place.

Amazon S3 held service content and customer usage records, Google Cloud held years of analytics results, and the company’s own data center kept its business records.

From each source, only files cleared for AI development had to be selected and sent to the training environment.

AI DEVELOPMENT, TRAINING DATA PREPARATION

Company data used by the new project

SourceAvailable dataSelected data
Amazon S380 TB24 TB
Google Cloud Storage32 TB12 TB
On-premises48 TB6 TB

GPU TRAINING ENVIRONMENT

Data reviewed
160 TB
Approved training data
42 TB
  • Training data
  • Data excluded from transfer

Data on the target server

  • training/service_content/24 TB
  • training/analytics/12 TB
  • training/business_records/6 TB

The AI team did not change where data was stored, and did not move all company data to new servers.

Only the data the project needed went from where it was stored to the GPU servers.

As training went on, new model files and evaluation results also became part of the company’s data.

At a company creating 6 TB of data a day, AI results became important data to manage and deliver too.

Live contextNow

The company starts an AI projectMarch 2029

Data created per day
6 TB / day
vs. 2026
60×
Active Flows
31

Infrastructure

  • On-premisesIn operation
  • Amazon S3In operation
  • Google CloudIn operation
  • GPU ServersNewly added

Teams using data

  • Business ops teamUsing data
  • System ops teamUsing data
  • Online service teamUsing data
  • Analytics teamUsing data
  • AI teamNewly added

Current focus

Preparing AI training data

JULY 2029, MORE PLACES WHERE DATA IS NEEDED, July 2029

The business expanded into new regions.

In July 2029, the company launched a global service.

The global business team chose Microsoft Azure for the new service.

The existing service used Amazon S3, the analytics team used Google Cloud, the AI team used GPU servers, and the business operations team used the company’s own data center.

The new global service needed data that all of these teams had built.

JULY 2029, DATA REQUIREMENTS

Data the new global service needs

DataCurrent locationInitial transferAfter that
Service contentAmazon S318 TBWhen new content is created
Business reference dataOn-premises800 GBDaily
Analytics resultsGoogle Cloud2.4 TBWhen analysis finishes
AI model filesGPU Servers3.2 TBWhen an approved version ships

NEW GLOBAL SERVICE ENVIRONMENT

Microsoft Azure

Initial data to run the global service

24.4 TB

  • Service contentAmazon S3Ready
  • Business referenceOn-premisesReady
  • Analytics resultsGoogle CloudReady
  • Production AI modelsGPU ServersReady

Starting to use Azure did not take away the role of the existing clouds or the company’s own data center.

Each team keeps doing its work just as before.

The new business puts the data those teams have built to work for its own needs.

As the company’s data grew, so did the ways it is used and the places it is needed.

Live contextNow

Global services widen data operationsJuly 2029

Data created per day
8 TB / day
vs. 2026
80×
Active Flows
40

Infrastructure

  • On-premisesIn operation
  • Amazon S3In operation
  • Google CloudIn operation
  • GPU ServersIn operation
  • Microsoft AzureNewly added

Teams using data

  • Business ops teamUsing data
  • System ops teamUsing data
  • Online service teamUsing data
  • Analytics teamUsing data
  • AI teamUsing data
  • Global business teamNewly added

Current focus

Global service launch

THREE YEARS LATER

A company that once created 100 GB a daynow creates 10 TB of data a day.

November 2026

100 GB / day

Infrastructure

  • On-premises

Teams using data

  • Business ops team
  • System ops team

November 2029

10 TB / day

Infrastructure

  • On-premises
  • Amazon S3New
  • Google CloudNew
  • GPU ServersNew
  • Microsoft AzureNew

Teams using data

  • Business ops team
  • System ops team
  • Online service teamNew
  • Analytics teamNew
  • AI teamNew
  • Global business teamNew

INNORIX in Practice

2026Nov

NOVEMBER 2029, ONE HUNDRED TIMES MORE DATA, November 2029

Three years on, how has the company’s data environment changed?

In three years, the company’s data grew 100-fold.

But the bigger change is that the work that uses data is itself different.

Besides business operations data, the company now creates online service data, analytics results, AI development data and global service data every day.

DAILY DATA GENERATION, 2029

What data does the company create today?

10 TB / day

EnvironmentData createdPer day
On-premisesExisting business and operations2.4 TB
Amazon S3Online service data3.6 TB
Google CloudAnalytics results2.0 TB
GPU ServersAI models and evaluations1.2 TB
Microsoft AzureGlobal service data800 GB

Each kind of data serves different work at the company.

Some data is used only where it is created, some goes to other teams, and some is used by several teams.

So the total data the company creates in a day is not the same as the total data it actually delivers.

Live contextNow

A company where 10 TB a day is normalNovember 2029

Data created per day
10 TB / day
vs. 2026
100×
Active Flows
48

Infrastructure

  • On-premisesIn operation
  • Amazon S3In operation
  • Google CloudIn operation
  • GPU ServersIn operation
  • Microsoft AzureIn operation

Teams using data

  • Business ops teamUsing data
  • System ops teamUsing data
  • Online service teamUsing data
  • Analytics teamUsing data
  • AI teamUsing data
  • Global business teamUsing data

Current focus

AI and global business

AN ORDINARY DAY IN 2029, November 2029

Handling 100 times the data is now an ordinary day.

Three years ago, each evening the company sent the day’s data to a work server and storage.

Today, data is created at many times of day, and many transfers run across different environments.

24 HOURS, NOVEMBER 2029

The company’s daily data operations schedule

TimeMain job
02:00Regular delivery of data for analytics
03:00Archiving model files from the AI environment
06:00Business data for the morning’s work
09:00Finished analytics results to other environments
12:00Morning service operations data
16:00Approved AI models to the service environment
18:00Daily business operations data
22:00Long-term archive data
HourlyRepeating delivery of online service data

Creating and moving data is no longer bunched into set hours of the day.

Depending on the work, a job runs on a fixed schedule or after new data has finished being created.

At any given time, several transfer jobs are running between different servers and clouds.

A look at today’s data transfers at the company.

INNORIX STUDIO, RUNS

November 16, 2029

Data created today
10 TB
Data delivered
14.8 TB
Jobs completed
186
FlowSourceTargetSizeStatus
Daily operationsWindowsLinux1.2 TBCompleted
Service contentS3Azure2.6 TBCompleted
Analytics inputS3GCS1.8 TBCompleted
Business analyticsLinuxGCS1.4 TBCompleted
Analytics resultsGCSGPU1.6 TBCompleted
Model releaseGPUAzure840 GBCompleted
Global result dataAzureLinux960 GBCompleted

Some of the transfer jobs completed today

Data delivered today, by destination

  • Amazon S32.4 TB
  • Google Cloud4.2 TB
  • Microsoft Azure3.8 TB
  • On-premises2.8 TB
  • GPU Servers1.6 TB

The company created 10 TB of new data today, but the completed transfers delivered 14.8 TB to its environments.

That is because one dataset can be used by several teams, and stored past data is delivered as needed alongside today’s data.

To understand a company’s data operations, look beyond how much data it creates to what data is actually used, and where.

Live contextNow

A company where 10 TB a day is normalNovember 2029

Data created per day
10 TB / day
vs. 2026
100×
Active Flows
48

Infrastructure

  • On-premisesIn operation
  • Amazon S3In operation
  • Google CloudIn operation
  • GPU ServersIn operation
  • Microsoft AzureIn operation

Teams using data

  • Business ops teamUsing data
  • System ops teamUsing data
  • Online service teamUsing data
  • Analytics teamUsing data
  • AI teamUsing data
  • Global business teamUsing data

Current focus

AI and global business

THREE YEARS OF CHANGE, 2026–2029

What changed at the company in three years?

2026–2029

Business growth and changing data operations

What changed2026202720282029
Data created per day100 GB1 TB3.5 TB10 TB
Files created per day8,400186,000984,0182,840,000
Infrastructure1235
Teams using data2346
Active Flows492348
Transfer runs per day3~43294186
Data delivered per day125 GB1.4 TB5.2 TB14.8 TB

The data grew, but not everything grew at the same rate.

  • Data created per day100×
  • Infrastructure5×
  • Teams using data3×
  • Active Flows12×

Growth compared with the starting setup in 2026

New work was added, new infrastructure came in, and more teams started using data.

Each time, the company kept its existing transfer jobs running and added only the new ones it needed.

The data grew 100-fold, but the number of Flows behind the transfer jobs did not.

The company’s data operations grew to match not only the size of its data, but also changes in its teams’ work and infrastructure.

Live contextNow

A company where 10 TB a day is normalNovember 2029

Data created per day
10 TB / day
vs. 2026
100×
Active Flows
48

Infrastructure

  • On-premisesIn operation
  • Amazon S3In operation
  • Google CloudIn operation
  • GPU ServersIn operation
  • Microsoft AzureIn operation

Teams using data

  • Business ops teamUsing data
  • System ops teamUsing data
  • Online service teamUsing data
  • Analytics teamUsing data
  • AI teamUsing data
  • Global business teamUsing data

Current focus

AI and global business

THE BUSINESS KEEPS GROWING

100 times more data than three years ago.And far more possibilities.

Companies start new businesses.They adopt new technology.They put data to work that they never used before.

A company’s growthshouldn’t be held back by its data operations.

INNORIX delivers a growing company’s data to where it is needed.

THE TECHNOLOGY BEHIND THIS STORY

Server & Cloud-to-Cloud Transfer

Even as a company creates more data and adds new servers and clouds, you can deliver and manage the data each job needs.

Explore the product