Start Free

OBJECT STORAGE TRANSFER

Object Storage Systems Apart,
Connected and Transferring Right Away.

From Amazon S3, Azure Blob and Google Cloud Storage to private and On-premises object storage.
Choose a Bucket and a storage path and transfer your files. Data movement between different Accounts, Regions and cloud environments runs on one platform.

SOURCEAmazon S3Account A, us-east-1Connected

/ production-data

NameSizeModified
datasets1.2 TB2024. 10. 15.
models450 GB2024. 10. 14.
logs320 GB2024. 10. 14.
metadata.json12 MB2024. 10. 13.
TARGETPrivate Storage (S3-Compatible)On-Prem, SeoulTransfer complete

/ ai-training-data

NameSizeModified
datasets1.2 TB2024. 10. 15.
training680 GB2024. 10. 14.
archive210 GB2024. 10. 13.
README.md6 KB2024. 10. 12.

STORAGE CONNECTIVITY

From the Same S3 to Multi-Cloud,
Connect a Wide Range of Object Storage.

Transfer between different Buckets, Accounts and Regions inside the same Amazon S3, and connect object storage across different clouds such as AWS, Azure and Google Cloud. Private storage inside your company and S3-compatible storage can be set as Source and Target too.

Choose the pair of storages to transfer between and the data path is composed to suit each environment. Data can be migrated or replicated without being tied to one cloud or one region, which leaves you free to handle cloud migration, data consolidation and cross-region movement as they come.

TRANSFER PREVIEW

SOURCEAmazon S3Bucket A, us-east-1
TARGETAmazon S3Bucket B, ap-northeast-2

Select a different object storage environment to see how the transfer is configured.Object storage across different public clouds can be connected and transferred.Object storage in a private cloud and in internal enterprise environments can be connected and transferred.A range of S3 API-based compatible storage can be connected and transferred.

DIRECT DATA PATH

Between Object Storage,
Files Move Directly.

There is no need to download a cloud file to a local server and upload it again to another storage the way the old approach did: it transfers straight from Source to Target. Removing staging space and needless data copies keeps the transfer structure simple.

The file data itself travels the configured path, while the INNORIX Platform manages the run, the progress and the result centrally. Moving large data between different clouds or regions no longer means operating an intermediate storage server of your own.

Amazon S3Account A
us-east-1, /production-data
Local StorageDownload, Store, Re-upload
Google Cloud StorageAccount B
ap-northeast-1, /ai-training-data

INNORIX PlatformHandles transfer control and monitoring; it is not a waypoint where files are held.

SELECTIVE OBJECT TRANSFER

From an Entire Bucket to Just the Files You Need,
Choose the Transfer Scope Freely.

Migrate a whole Bucket, or pick only the files under a particular Prefix. Narrow the targets by conditions such as file name pattern and modified date, and select the files you want directly from the actual object list.

Rather than copying all the data again, only the objects you need are delivered to the other storage, which suits dataset moves and pulling out the data for a given period. Check the selected file count and the total volume before you run the transfer, so even a large body of objects is managed to purpose.

s3://production-data

Amazon S3, Account A, us-east-1Object Selection
NameSizeModified
training-001.parquet24 GB2024. 10. 15. 14:21
training-002.parquet18 GB2024. 10. 14. 09:12
training-003.parquet12 GB2024. 10. 13. 18:45
metadata.json8 MB2024. 10. 12. 11:30
config.yaml4 KB2024. 10. 12. 11:20
access-2024-10.log2 GB2024. 10. 15. 03:00
resnet-50.ckpt6 GB2024. 10. 09. 17:40
vit-base.ckpt9 GB2024. 09. 28. 10:05
Target Bucketgs://ai-training-data/datasets/Google Cloud Storage, Account B, asia-northeast33 files selected, 54 GBTransfer selected files Transfer complete

CONTINUOUS DATA MOVEMENT

From a One-Time Migration,
To Continuous Transfer Automation.

Move the data in your existing object storage to a new environment in one pass, or deliver the files you need over and over on a schedule or by event. After the first migration, newly created and changed files can be set to keep moving to other clouds and storages.

When a transfer completes it can connect to the next job, Processing or Archive among them, and be automated as a single Flow. It does not end at a storage migration: the whole cycle of data moving and being used across environments is operated on one platform.

A One-Time Migration

Files in existing storage are migrated to the new environment.

Storage ASource
Storage BTarget
Completed

Keep Delivering Changed Files

The files you need are transferred repeatedly on a schedule or by event.

Schedule
Event
Delivery
Waiting for next run...

Connect to the Next Task

When a transfer completes, it connects to follow-up work such as Processing and Archive.

Processing
Archive
Completed

Faster than an explanation: try it yourself.

Connect the devices and build the distribution flow.

Add flowCancelSave draftSave & active

Flow canvas

Daily · 02:00HQHQ-BUILD-01TOKYO-EDGE-07EdgeTOKYO-EDGE-01OSAKA-EDGE-02NAGOYA-EDGE-03SAPPORO-EDGE-04FUKUOKA-EDGE-05TOKYO-EDGE-06

0 devices · 1 step

Configuration

Start when

NowSchedule

Every day · 02:00

Source

HQ-BUILD-01

Target

Choose target

GET STARTED

Now put it to work in your application.

TECHNICAL FAQ

Frequently asked questions

Which object storage services can I connect?

You can connect Amazon S3, Azure Blob Storage, Google Cloud Storage, Alibaba OSS, Cloudflare R2 and supported S3-compatible storage. The features available in detail can differ by storage type and connection method.

Can it transfer between different AWS accounts or regions?

Yes. Object storage in different buckets, accounts and regions can be set as source and target. The access rights and the network connection needed have to be configured.

Can it transfer from Amazon S3 to Azure Blob or Google Cloud Storage?

Supported cloud object storage services can be connected to each other and transferred between. The authentication and API connection conditions for each have to be confirmed.

Can on-premises S3-compatible storage be used as well?

Supported S3 API-compatible storage can be connected. Actual compatibility has to be verified against that storage's API implementation, authentication method and network environment.

Do files have to be downloaded to a local PC or a separate storage server?

INNORIX supports a direct transfer setup that removes the separate steps of storing files locally and uploading them again. The actual data path has to be confirmed against the storage type and the network configuration.

Can I transfer only selected files rather than a whole bucket?

Yes. Use the supported bucket, prefix, file pattern and file selection conditions to transfer only the objects you need.

Can it transfer files of several TB or large numbers of small files?

INNORIX supports both very large and very numerous file transfers. The scale and performance you actually get depend on the storage API, the network, the object characteristics and the transfer settings.

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 Free

Considering transfer between object storage systems?

We'll help you review a transfer setup that fits your Object Storage and Data Path in use.

  • Review of your Object Storage combination and environment
  • Data Path setup across Cloud and Region
  • Guidance on applying Migration and recurring transfer

We use these details only to answer your inquiry. See our Privacy policy.