/ production-data
| Name | Size | Modified |
|---|---|---|
| datasets | 1.2 TB | 2024. 10. 15. |
| models | 450 GB | 2024. 10. 14. |
| logs | 320 GB | 2024. 10. 14. |
| metadata.json | 12 MB | 2024. 10. 13. |
OBJECT STORAGE TRANSFER
Across Clouds and Regions,
Transfer Files Between Object Storage.
Connect object storage of many kinds, Amazon S3 among them, and transfer files between different Buckets, Accounts and Regions. Public cloud, private cloud and S3-compatible on-premises storage all work in one environment.
Browse the files in each storage directly and move the data you need by choosing a Source and a Target. Everything from a single large file to a dataset of countless objects can be transferred, with progress and completion results managed on one platform.
/ ai-training-data
| Name | Size | Modified |
|---|---|---|
| datasets | 1.2 TB | 2024. 10. 15. |
| training | 680 GB | 2024. 10. 14. |
| archive | 210 GB | 2024. 10. 13. |
| README.md | 6 KB | 2024. 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
us-east-1 · /production-data
Local StorageDownload · Store · Re-upload
Google Cloud StorageAccount B
ap-northeast-1 · /ai-training-data
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
| Name | Size | Modified | |
|---|---|---|---|
| training-001.parquet | 24 GB | 2024. 10. 15. 14:21 | |
| training-002.parquet | 18 GB | 2024. 10. 14. 09:12 | |
| training-003.parquet | 12 GB | 2024. 10. 13. 18:45 | |
| metadata.json | 8 MB | 2024. 10. 12. 11:30 | |
| config.yaml | 4 KB | 2024. 10. 12. 11:20 | |
| access-2024-10.log | 2 GB | 2024. 10. 15. 03:00 | |
| resnet-50.ckpt | 6 GB | 2024. 10. 09. 17:40 | |
| vit-base.ckpt | 9 GB | 2024. 09. 28. 10:05 |
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
CompletedKeep 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
CompletedEvery 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 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