THE INFORMATION IN THIS ARTICLE APPLIES TO:
If a file is being downloaded or uploaded with an Event Rule, and the connection breaks (network issues, etc.), will the transfer automatically resume? Will it pick up where it left off?
When files are being transferred with Event Rules (copy, move, or download), if there are connection problems (e.g., the network is unavailable), EFT Server will attempt to establish a connection the number of times specified in the Event Rule. When EFT Server is able to re-establish the connection, it continues to transfer the file from where it stopped, even if there are multiple interruptions. There are no retry attempts after a login failure.
If the network is lost while the Web Transfer Client is transferring files, it waits for a timeout period (30 seconds) and then shows a red X for the transfer. The Status in the queue pane indicates that the transfer failed. If you want to attempt to transfer the file again, you must login again when the network is available. After the Web Transfer Client reconnects, it resumes the transfer from where it stopped.)
When you add a Copy/Move file to host or Download file from host Action to a Rule, the ClientFTP (offload engine) performs retries upon failures -- network failures is the typical example -- based upon the settings in the Advanced Options dialog box.
Be aware that the Copy/Move file to host or Download file from host Action takes place synchronously; that is, EFT Server follows the logic of doing the transfer, including all retries, before moving on to the next Action, such as an email notification. So a really long running transfer that also retries numerous times with large delays will cause the Event Rule to take a long time to complete.
The transfer/retry options include:
- Max concurrent transfer threads
- Connection timeout
- Connection retry attempts
- Delay between retries
If you are using EFT Server's Secure Ad Hoc Transfer module, and if EFT Server and IIS are installed on the same computer, when creating the Event Rule for upload notifications, create an additional Condition for REMOTE IP does not match 127.0.0.1. The Rule’s Conditions should read:
If settings level is Ad-Hoc
AND If remote ip does not match <ip address of IIS server>
AND If remote ip does not match 127.0.0.1
The second Condition (in red) should not be added if EFT Server and IIS are not installed on the same computer.
(The default Settings Template name was changed in version 6.x to "EFTAdHoc," but you could have given it any name when you installed SAT.)