Differences
This shows you the differences between the selected revisions of the page.
| 2020-10-27 | 2020-10-27 | ||
| no summary (193.244.33.204) (hidden) (untrusted) | no summary (193.244.33.204) (hidden) (untrusted) | ||
| Line 1: | Line 1: | ||
| - | ====== File Transfer Resume ====== | ||
| - | |||
| - | ===== Basic Usage ===== | ||
| - | WinSCP supports resuming file transfers with [[SFTP]] and [[FTP]] protocols. [[SCP]] and [[WebDAV]] protocols do not allow it. With [[S3]] protocol, transfer can be resumed only immediately by reconnecting a lost session, not later. | ||
| - | |||
| a | a | ||
| - | |||
| - | ===== [[manual]] Manual Resume ===== | ||
| - | There's an alternative manual method to resume transfer, which can be used with FTP protocol. | ||
| - | |||
| - | If you attempt to transfer a file already in the target directory and the target file is smaller then the source file, the [[ui_overwrite|overwrite confirmation dialog]] displays a //Resume// command or an //Append// command (when appending is supported), in the drop down menu of the //No// button. After you click //Append//, WinSCP opens another prompt that lets you append source file or resume your transfer. | ||
| - | |||
| - | If you resume the transfer, WinSCP will skip a part of the source file equal to the target file's size. The program will only transfer the remainder. | ||
| - | |||
| - | Note that you must have [[ui_pref_environment#confirmations|overwrite confirmations enabled]] to use the method. | ||
| - | |||
| - | The method is also useful for resuming transfers initiated by other clients and also to update log files. Manual resuming of [[transfer_mode|text mode transfers]] with SFTP-4 and newer is not supported. | ||
| - | |||
| - | ===== Common Problems ===== | ||
| - | If you want to resume your transfer, you must use the same source file version as the interrupted transfer. If you do not, your target file will include the source file's previous version and its current version. For automatic resume, if the partial file is bigger than the source file, WinSCP will display error and disallow resume. | ||
| - | |||
| - | If the target file exists and it is not write-able, but the target directory is, the file will may be transferred anyway with automatic resume. The error overwriting the file will occur only after the transfer finishes. It is because the file is first transferred into temporary file. | ||
| - | |||
| - | ===== [[broken_connection]] Resuming from Broken Connections ===== | ||
| - | With [[sftp|SFTP]] and [[ftp|FTP]] protocols, when connection is broken, WinSCP can automatically reconnect and resume the transfer.((If transfer resuming/transfer to temporary files name is disabled, file transfer will start from the beginning, with [[sftp|SFTP protocol]].)) This can be configured on //[[ui_pref_resume|Endurance page]]// of Preferences dialog. | ||