Automate a file transfer you run over and over
No more signing in to the same server every day to pick files and copy them, or checking again and again whether a transfer finished. In INNORIX Studio, build a Flow from the source and target devices and the file conditions, then give it a schedule. A transfer you set up once runs at the time you chose, and when something is interrupted or fails, Runs shows you the cause and the result.
- Identify the repeat job
- Name the two devices and the paths
- Create the Flow
- Set a daily schedule
- Review the scheduled run and anything that failed
This guide is about setting up and running scheduled automation. Guide 7 covers N:1 collection from several sites into a central server, guide 9 covers distribution once collection finishes, and guide 11 covers event automation triggered by a new file. This page concentrates on taking a transfer you repeat from one server to another and making it run without a person.
How it is built
- Decide which transfer you want to repeat.
Confirm the source and target servers, the source folder, the receiving path, the kinds of files to send and how often it runs. Decide too whether to resend the same files every time or only files that are new.
- Connect the devices in Devices.
Register the source and target servers in Studio and confirm that both paths are reachable.
- Create the transfer job in Flows.
Set the source and target paths and any file filters, overwrite rules or filename-conflict handling you need. Run it manually first to confirm the files you expected are the ones that arrive.
- Set the repeat in Schedule.
Choose a time and interval that fit the job, for example 02:00 daily. Activate the schedule with your operating hours and the point at which the files finish being written both in mind.
- Check the automated run in Runs.
Confirm that the scheduled job actually ran, which files went across and which ones failed. If something is wrong, fix the cause and rerun only the transfers that need it.
Where it is used
- Daily ERP settlement files
The CSV that the ERP server writes at the end of each day goes to the accounting and settlement server. If the settlement file can be late, review the scheduled time against whether the file is ready.
- Overnight transfer of factory output
Production result files held on the factory server go to the head-office analysis server overnight, keeping the daytime network load down.
- Regular copies of video and design output
Large deliverables move from the finished folder on the production server to the review server every day, with reruns of interrupted jobs managed in Runs.
- Logs and reports between servers
Yesterday's logs or reports from a service server move to the central analysis server. Think of it as moving files that have already been written, rather than as a replacement for a log collection system.
- Feeding a cloud analysis environment
Files generated on an on-premises server go to a connected cloud storage or cloud server on a schedule, so the data for the analysis that follows is ready.
- Regular file exchange with a partner gateway
Files that land on an internal gateway server are passed to other business servers on a schedule. If an external partner only supports SFTP, keep the external leg as it is and automate from the internal hop onwards.
- Standardising repeat work across teams
Manual copies and batch scripts each team ran on its own become individual Flows, so every owner checks results the same way.
Usage guides
Frequently asked questions
Is there a solution that automates a server-to-server file transfer I repeat every day?
INNORIX is a file transfer platform where transfers between connected devices — servers, cloud storage and more — are built as Flows and repeated on a Schedule. The job you defined runs and its results are tracked, without someone picking and copying files each time.
Can files transfer automatically without FTP scripts or Windows Task Scheduler?
Connect the source and target devices INNORIX supports, then set up a Flow and a Schedule in Studio to build the repeat transfer. It does not convert an existing script automatically — the transfer conditions are rebuilt as a new Flow, and the file conditions and results should be verified before you switch over.
Can a folder be sent to another server at a set time every day?
Yes. Name the source and target folders and build a daily schedule. Adjust the run time so the job does not start before the files finish being written, and set the conditions that choose which files to send alongside it.
Can only files with a certain extension be transferred automatically?
The file types the job needs can be set as include and exclude conditions — sending only CSV, for example, or excluding temporary files. Check the actual filter format and where it applies against what your Studio supports.
If the network drops mid-transfer, does everything have to be sent again?
INNORIX can resume an interrupted file transfer. How it resumes in practice can depend on the device connection, whether the file changed and the job settings, so test it before you go live. Failures and the results of reruns are in Runs.
Where do I confirm that a scheduled transfer succeeded?
Studio Runs shows the run time, progress, and whether it completed or failed. Even when a job is marked successful, whether the system downstream processed the file may still need checking separately.
Can a file transfer the moment it is created?
Besides running on a repeating schedule, automation driven by events such as a new file is worth considering. This guide covers scheduled transfers at a set time; triggering on a file creation event is covered separately in usage guide 11.
Can automated transfers across several servers be managed from one screen?
In INNORIX Studio you register several devices and Flows and review each run in Runs. Instead of reading individual script logs scattered across servers, transfer work can be managed centrally.