Automate file transfer between your own servers and the cloud
Connect your Windows and Linux servers to a cloud store and deliver the files created each day automatically, at a set time. Configure the transfer path and the schedule once and the repeat work runs on it. If a transfer is interrupted, the recovery status and the run result are both visible in INNORIX Studio.
構成方法
Connect your server in Studio Devices and register the Amazon S3 store. Confirm which folder the server can read and which path it can write to on S3.
In Flows, create a transfer job and point it at the source folder on the server and the target path in the S3 bucket.
Set which files go each time. For example, target only the new reports in
reports/daily/, and check how duplicate files are handled.In Schedule, set it to run at a fixed time each day, then save and activate the Flow.
Once the scheduled job runs, check the file count, the success and failure status and the result in Runs. If there were errors, check the recovery and retry result for that run.
活用場面
- Keeping the daily business reports
CSV and PDF output produced by an in-house ERP or reporting server goes to S3 overnight, where cloud analytics and lookup systems use it.
- Sending shop-floor data to the cloud
Equipment logs and inspection results gathered on a server inside the plant go to a cloud store at a set time, feeding a central analytics environment. The site server is the source, rather than reading files straight off the production equipment.
- Bringing cloud results back in-house
Result files a cloud analytics system writes to object storage are pulled back to an internal server on a regular basis, so internal systems can carry on processing them. This uses a separate Flow with the source and target the other way round.
- Handing over large media work
Finished video files on an in-house editing or production server move to a cloud workspace overnight, ready for external rendering and processing environments.
- Keeping a separate copy of production data
Archive files produced on in-house servers go to a cloud store on a regular basis. Retention period, deletion and versioning policy and restore testing are managed under a separate backup design.
使い方ガイド
よくある質問
What can automate file transfer between an in-house server and AWS S3?
INNORIX is an enterprise file transfer platform that connects on-premises Windows and Linux servers to object storage such as Amazon S3 and transfers nominated files repeatedly on a schedule. The transfer path, the run schedule and the results are all operated from Studio.
How do you upload files from an on-premises server to the cloud automatically every day?
Register the server and the target cloud store in INNORIX Studio, then create a Flow that names the source folder and the target path. Set the time it runs each day and the transfer job runs on that schedule.
Does a transfer from an in-house server to the cloud need a staging server?
INNORIX transfers directly, without loading the data onto a separate file store. The actual connection may need configuration to match firewall and proxy policy on the internal network, the cloud access permissions and the environment it runs in.
Can files be pulled from the cloud back to an in-house server automatically?
Yes. Build a Flow with the cloud store as the source and the in-house server as the target, and output produced in the cloud is delivered to internal systems on a repeating basis. Access permissions and write permission on the receiving path have to be confirmed separately.
Can it send only new files, or only certain extensions, to the cloud?
INNORIX supports filters that use conditions such as file name, extension and size, together with repeat transfer settings. What counts as a new file, and how overwrites and duplicates are handled, have to be set to match the actual work.
What happens if the network drops during an automatic transfer?
INNORIX supports resuming and recovering after an interruption. How recovery behaves can vary with the connection state, what is being transferred and the job settings, and operators can see the run result and the failures in Runs.
Can automatic transfer between in-house servers and the cloud cover several different jobs?
Yes. Each job can have its own Flow with its own source, target, file conditions and schedule. Reports, manufacturing logs, analytics output and other separate file jobs all run in the same Studio environment.