Differences
This shows you the differences between the selected revisions of the page.
2019-03-29 | 2020-10-27 | ||
Resume and Append are menu commands for a while already (martin) | no summary (193.244.33.204) (hidden) (untrusted) | ||
Line 4: | Line 4: | ||
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. | 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. | ||
- | ===== [[automatic]] Automatic Resume / Transfer to Temporary Filename ===== | + | a |
- | WinSCP is able to store file being transferred to temporary filename first, renaming it to the target name only once the transfer successfully finishes. | + | |
- | + | ||
- | Reasons to do that: | + | |
- | * If the transfer is interrupted, on the next attempt (either manual or automatic), WinSCP is able to automatically detect the partial/temporary file and offer you to resume the transfer (or even resume automatically). | + | |
- | * While updating an existing file, the original version of the file exists during whole transfer. This is particularly useful when updating frequently accessed file on web sites. | + | |
- | * If the server runs a process that automatically picks new files and processes them, it can be configured to ignore distinct names of temporary files. It prevents the process from picking an incomplete file, while it's uploaded. See [[script_locking_files_while_uploading|locking files while uploading]]. | + | |
- | + | ||
- | Reasons not to do that: | + | |
- | * As the file is uploaded to a temporary name, it is technically a new file, even though the file with target name already exists. As such: | + | |
- | * after the original file is deleted and temporary file is renamed to the original file name, you lose all attributes of the original file (such as owner and group) except for basic permissions;((For this reason WinSCP never transfers to temporary file name first, if the target file is know to be owner by another user. Note that the owner name can be detected with SFTP-4 and newer only.)) | + | |
- | * while you may have permissions to overwrite the existing file, you might not have permissions to create new (temporary) file. | + | |
- | + | ||
- | For performance reasons transfer to temporary file name is enabled by default for files larger than a given threshold. The threshold is initially 100 KB. You can change the threshold. You can also enable the feature for all files, particularly when looking to achieve the second impact. You may also need to disable the feature altogether, particularly if you do not have permissions required (e.g. permissions to create a new file in target directory). This can be configured on //[[ui_pref_resume|Endurance page]]// of Preferences dialog. | + | |
- | + | ||
- | If your transfer is interrupted, a partial file (with ''.filepart'' extension) remains in the target folder. After you try to transfer the file a second time, WinSCP looks for the partial file. If it finds a partial file, it offers you chance to resume the transfer ([[ui_pref_environment#confirmations|the confirmation can be disabled]]). | + | |
- | + | ||
- | Note that partial files can be distinguished in file panel by special [[ui_file_panel#special_files|"torn sheet" overlay icon]]. | + | |
- | + | ||
- | To configure transfer to temporary file name in [[scripting]], use ''-resumesupport'' switch of file transfer commands. In .NET assembly use ''[[library_transferoptions#resumesupport|TransferOptions.ResumeSupport]]''. | + | |
- | + | ||
- | Transfer to temporary filename is supported with [[sftp|SFTP protocol]] only and only for [[transfer_mode|binary transfers]]. | + | |
===== [[manual]] Manual Resume ===== | ===== [[manual]] Manual Resume ===== |