Post a reply

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

sdo@decisiondesign.com

Problem restarting large file transfer

I've got a batch job to transfer large SQL Server backup files to an offsite location. Several of the files are large: > 9 GB. We often have a connection problem which interrupts the file transfer. When this happens WinSCP reconnects when the connection is restored and tries to resume file transfer but repeatedly times out with the following messages:

< 2017-01-17 07:59:41.715 227 Entering Passive Mode (10,0,0,81,19,235).
. 2017-01-17 07:59:41.715 Server sent passive reply with unroutable address 10.0.0.81, using host address instead.
> 2017-01-17 07:59:41.715 REST 2019776855
< 2017-01-17 07:59:41.780 350 Restart position accepted (2019776855).
> 2017-01-17 07:59:41.780 STOR MyDatabase_backup_2017_01_15_000006_1826520.bak
. 2017-01-17 07:59:56.049 Timeout detected. (control connection)
. 2017-01-17 07:59:56.049 Copying files to remote side failed.
. 2017-01-17 07:59:56.049 Connection was lost, asking what to do.
. 2017-01-17 07:59:56.049 Asking user:
. 2017-01-17 07:59:56.049 Lost connection. ("Server sent passive reply with unroutable address 10.0.0.81, using host address instead.","Server sent passive reply with unroutable address 10.0.0.81, using host address instead.","Timeout detected. (control connection)","Copying files to remote side failed.")
< 2017-01-17 07:59:56.049 Script: Lost connection.
< 2017-01-17 07:59:56.049 Script: Server sent passive reply with unroutable address 10.0.0.81, using host address instead.
< 2017-01-17 07:59:56.049 Server sent passive reply with unroutable address 10.0.0.81, using host address instead.
< 2017-01-17 07:59:56.049 Timeout detected. (control connection)
< 2017-01-17 07:59:56.049 Copying files to remote side failed.

This repeats ad infinitum until I intervene.

The batch job is run via this command:
WinSCP.com -script=c:\bin\sqlftpscript.txt

The sqlftpscript.txt file contains the following:
option batch on
option confirm off
option reconnecttime 1200
# Synchronize excluding specific folder(s)
synchronize remote -criteria=both -transfer=binary

WinSCP version is:
. 2017-01-16 08:51:39.946 WinSCP Version 5.9.2 (Build 6958) (OS 6.3.9600 - Windows Server 2012 R2 Standard)

My guess is that it's taking too long to move to the resume point and the connection times out after 15 seconds. Is there an option/setting I can use to extend the amount of time WinSCP waits for the restart?