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.
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.
When no other options are specified and the terminal is interactive, movedat will prompt you to either resume, start over, or skip any file transfer which is eligible to be resumed. Selecting resume will continue from the point where the previous attempt was interrupted. Choosing to start over will discard the previous attempt and transfer the entire file.
The following options determine how movedat will respond to resumable transfers:
|-r||Resume interrupted transfers if possible.|
|-y||Resume interrupted transfers if possible, otherwise start over.|
|-O||Always start over from the beginning, discarding any previous attempts.|
|-c||Partial downloads will be ignored and data will be written directly to the destination file. This prevents the creation of ".TMP" and ".CHK" files, but if the transfer is interrupted, it will not be resumable. This does not affect uploads.|
|-I||A partial transfer will be ignored if IgnoreExisting is set and a complete file also exists at the destination.|
|-t||TryInterval can be used to change the interval between automatic retry attempts, abort movedat in case of error, or skip problematic files.|
Streaming Folders, Object Handlers, and pipes 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.