Resuming an Interrupted Transfer

The client and server each keep track of regular file transfer progress, allowing the transfer to be resumed from the last checkpoint in case of interruption.  For temporary disruptions, such as a loss of network connectivity, the client will automatically retry the transfer after a short wait.  For disruptions requiring or resulting from user intervention, such as canceling a transfer, you can resume by repeating the GET or SEND action and answering the prompt that you wish to resume.

If you know or suspect that the source file contents may have changed since the previous transfer attempt, you should start over rather than resuming.  Resuming transfer of a file which has changed may result in corruption of the file.

For uploads, the server maintains checkpoint information in -sv.tmp and -sv.met files.  See the Upload Status section for details.  For downloads, the client maintains checkpoint information in .TMP, and on Windows .CHK files.  Be careful not to move, rename, or delete those files unless you intend to discard the partial upload.

Non-Resumable Transfers

Streaming Folders and Object Handlers cannot be resumed from the point of interruption and must be restarted from the beginning.  Compressed uploads can only be resumed with compression disabled.  One-at-a-time (not Streaming) folder transfers can be resumed from the point of interruption when automatic retry is in effect.  Manually repeating a folder transfer will retransfer all of the contents.