Differences

This shows you the differences between the selected revisions of the page.

2011-07-30 2013-04-15
sftp ftp scp (martin) Merging-in documentation of transfer to tempoerary file name from ui_pref_resume (martin)
Line 4: Line 4:
WinSCP supports resuming file transfers with [[SFTP]] and [[FTP]] protocols. [[SCP]] protocol does not allow it. WinSCP supports resuming file transfers with [[SFTP]] and [[FTP]] protocols. [[SCP]] protocol does not allow it.
-===== [[automatic]] Automatic Resume ===== +===== [[automatic]] Automatic Resume/Transfer to Temporary Filename ===== 
-When transferring file with SFTP protocol((Supported for SFTP-2 and newer only (most of the current SFTP servers) )), it is first transferred into a temporary file with ''.filepart'' extension. Only after the transfer is completed the extension is removed.+WinSCP is able to store file being transferred to temporary filename first, renaming it to the target name only once the transfer successfully finishes.
-If your transfer is interrupted, a partial file (with ''.filepart'' extensions) 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]]).+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. 
 + 
 +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 loose all attributes of the original file (such as owner and group) except for permissions; 
 +    * 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 KiB. 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 tab]]// 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]]. Note that partial files can be distinguished in file panel by special [[ui_file_panel#special_files|"torn sheet" overlay icon]].
-For performance reasons, WinSCP only supports automatic file transfer resumption for files larger than a given threshold. By default, the threshold is 100 KiB. This can be configured on //[[ui_pref_resume|Endurance tab]]// of Preferences dialog. Also automatic resuming of [[transfer_mode|text mode transfers]] is not supported.+Transfer to temporary filename is supported with [[sftp|SFTP protocol]] only and only for [[transfer_mode|binary transfers]].
===== [[manual]] Manual Resume ===== ===== [[manual]] Manual Resume =====

Last modified: by martin