Problems with transferring large backup images. Not a timeout.

[danieltnmi]

So, I'm replicating using StorageCraft ImageManager to a Filezilla server instance running on Windows 2016. The small incremental files can get through to the FTP server without a problem, as can the midsize full images, but anything larger than ~150 GB just sort of gives up midway. I found another post about a similar problem and someone said to check the Windows error logs but there was nothing present related to the problem.

Here are the logs:

(000566)4/9/2018 13:06:33 PM - administrator (xxx.xxx.xxx.xxx)> PWD
(000566)4/9/2018 13:06:33 PM - administrator (xxx.xxx.xxx.xxx)> 257 "/storagecraft-backup/x/x" is current directory.
(000566)4/9/2018 13:06:33 PM - administrator (xxx.xxx.xxx.xxx)> SIZE C_VOL-b001.spf.tmp
(000566)4/9/2018 13:06:33 PM - administrator (xxx.xxx.xxx.xxx)> 213 255548325888
(000566)4/9/2018 13:06:33 PM - administrator (xxx.xxx.xxx.xxx)> PORT x,x,x,x,x,x
(000566)4/9/2018 13:06:33 PM - administrator (xxx.xxx.xxx.xxx)> 200 Port command successful
(000566)4/9/2018 13:06:33 PM - administrator (xxx.xxx.xxx.xxx)> REST 255548325888
(000566)4/9/2018 13:06:33 PM - administrator (xxx.xxx.xxx.xxx)> 350 Rest supported. Restarting at 255548325888
(000566)4/9/2018 13:06:33 PM - administrator (xxx.xxx.xxx.xxx)> STOR C_VOL-b001.spf.tmp
(000566)4/9/2018 13:06:33 PM - administrator (xxx.xxx.xxx.xxx)> 150 Opening data channel for file upload to server of "/storagecraft-backup/x/x/C_VOL-b001.spf.tmp", restarting at offset 255548325888
(000566)4/9/2018 13:06:33 PM - administrator (xxx.xxx.xxx.xxx)> 550 Writing to file failed.

So, from what I can interpret, it performs its normal check to see if the file exists and how big it is if it does, opens all the ports, and then resumes the transfer at the offset of the current size of the file in the directory. It can open the data channel (maybe?) but when it tries to write to the file, it can't do it.

Can anyone help out? Would really appreciate it!

[botg]

Are you using any virus scanners?