FTP backups no longer finishing (after update to build 14110?)
Hey everyone,
I have been doing backups to an FTP for about a year or so now without any issues.
But since not too long ago they keep on failing. I think it's since I update the the latest version of TI2019 which is build 14110.
The backup job starts but eventually hits an "can't write file error" with the option to abort, retry or "select destination".
Retrying doesn't work no matter how often I try.
If I abort and restart the backup job it hit the same error at exactly the same GB amount (always when it's XX.XX GB).
Doing the backup job to a local destination works. Nothing on the FTP changed, I can write other data without issues.
It happens with two seperate backup jobs (one for disk and one for files).
Recreating the backup task didn't help.
LOG (abbreviated):
...
018-10-16T20:46:14:448+02:00 5288 I00640000: Schreibe vollständige Version zu Datei: WindowsDisk_FTP_encr_full_b1_s1_v31.tib
2018-10-16T20:47:31:549+02:00 1568 E00040003: Error 0x40003: Fehler beim Schreiben der Datei.
| Ablaufverfolgungsebene: Fehler
| line: 0x1d8eab676a3f6ab7
| Datei: c:\bs_hudson\workspace\589\products\imager\archive\impl\operations\archive_message_callback.cpp:1166
| Funktion: TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback
| line: 0x1d8eab676a3f6ab7, c:\bs_hudson\workspace\589\products\imager\archive\impl\operations\archive_message_callback.cpp:1166, TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback
| Path: ftp://192.168.0.1:21/backups/TIH-Backups/WindowsDisk_FTP_encr_full_b1_s…
| $module: ti_demon_vs_14110
|
| error 0x40003: Fehler beim Schreiben der Datei.
| line: 0x74c96bd8d1217f01
| Datei: c:\bs_hudson\workspace\589\core\network\ftp\ftp_ofile.cpp:124
| Funktion: FTPOFile::Write
| line: 0x74c96bd8d1217f01, c:\bs_hudson\workspace\589\core\network\ftp\ftp_ofile.cpp:124, FTPOFile::Write
| $module: ti_demon_vs_14110
2018-10-16T20:48:01:552+02:00 1568 I00040003: Error 0x40003: Erneuter Versuch für die Aktion Fehler: Fehler beim Schreiben der Datei..
| Ablaufverfolgungsebene: Information
| line: 0x1d8eab676a3f6690
| Datei: c:\bs_hudson\workspace\589\products\imager\archive\impl\operations\archive_message_callback.cpp:103
| Funktion: `anonymous-namespace'::TraceReattemptError
| line: 0x1d8eab676a3f6690, c:\bs_hudson\workspace\589\products\imager\archive\impl\operations\archive_message_callback.cpp:103, `anonymous-namespace'::TraceReattemptError
| $module: ti_demon_vs_14110
|
| error 0x40003: Fehler beim Schreiben der Datei.
| line: 0x1d8eab676a3f6ab7
| Datei: c:\bs_hudson\workspace\589\products\imager\archive\impl\operations\archive_message_callback.cpp:1166
| Funktion: TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback
| line: 0x1d8eab676a3f6ab7, c:\bs_hudson\workspace\589\products\imager\archive\impl\operations\archive_message_callback.cpp:1166, TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback
| Path: ftp://192.168.0.1:21/backups/TIH-Backups/WindowsDisk_FTP_encr_full_b1_s…
| $module: ti_demon_vs_14110
|
| error 0x40003: Fehler beim Schreiben der Datei.
| line: 0x74c96bd8d1217f01
| Datei: c:\bs_hudson\workspace\589\core\network\ftp\ftp_ofile.cpp:124
| Funktion: FTPOFile::Write
| line: 0x74c96bd8d1217f01, c:\bs_hudson\workspace\589\core\network\ftp\ftp_ofile.cpp:124, FTPOFile::Write
| $module: ti_demon_vs_14110
2018-10-16T20:48:01:552+02:00 1568 I00640000: Schreibe vollständige Version zu Datei: WindowsDisk_FTP_encr_full_b1_s1_v32.tib
2018-10-16T20:48:01:552+02:00 1568 E000B042B: Error 0xb042b: Die Netzwerkfreigabe ist nicht verfügbar.
| Ablaufverfolgungsebene: Fehler
| line: 0x4d3f22948e29f391
| Datei: c:\bs_hudson\workspace\589\products\imager\archive\impl\utils.cpp:698
| Funktion: TrueImage::Archive::CheckVolumeNetworkPath
| line: 0x4d3f22948e29f391, c:\bs_hudson\workspace\589\products\imager\archive\impl\utils.cpp:698, TrueImage::Archive::CheckVolumeNetworkPath
| Path: ftp://192.168.0.1:21/backups/TIH-Backups/
| $module: ti_demon_vs_14110
|
| error 0x40011: Die spezifizierte Datei existiert nicht.
| line: 0x5dc3786a32fb1936
| Datei: c:\bs_hudson\workspace\589\core\network\ftp\ftp_dir.cpp:753
| Funktion: FTPDirectory::GetIterator
| line: 0x5dc3786a32fb1936, c:\bs_hudson\workspace\589\core\network\ftp\ftp_dir.cpp:753, FTPDirectory::GetIterator
| $module: ti_demon_vs_14110
2018-10-16T20:48:31:552+02:00 1568 E0004000A: Error 0x4000a: Fehler beim Erstellen der Datei.
| Ablaufverfolgungsebene: Fehler
| line: 0x1d8eab676a3f6ab7
| Datei: c:\bs_hudson\workspace\589\products\imager\archive\impl\operations\archive_message_callback.cpp:1166
| Funktion: TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback
| line: 0x1d8eab676a3f6ab7, c:\bs_hudson\workspace\589\products\imager\archive\impl\operations\archive_message_callback.cpp:1166, TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback
| Path: ftp://192.168.0.1:21/backups/TIH-Backups/WindowsDisk_FTP_encr_full_b1_s…
| $module: ti_demon_vs_14110


- Log in to post comments

Your log file shows the remote destination as being ftp://192.168.0.1:21/backups/TIH-Backups which looks to be a local network address. Have you tried either mapping a Windows drive letter for the remote location, or else using SMB to access that location?
I tried via SMB to the same location and it worked without issues. So it seems the issue is in the FTP functionality of that particular build ( 14110 ) of TIH 2019.
I'll try to open an ticket with Acronis support.
But it would be great if other people with the same issue would reply here never the less. This will increase the odds of this issue being fixed since it would proof that it's not an issue with my setup but indeed with TIH 2019.
- Log in to post comments

Glad to hear that using SMB was successful to your remote destination. How much data is involved in this backup, as that is an important detail particularly when FTP gets involved?
- Log in to post comments

I created a new backup task for my ATI 2019 #14110 using FTP to my NAS and this was successful but the source data was just over 5GB so doubt that this is approaching the size that you have for your FTP backup task. I find that using FTP is much slower than using SMB so I would need to allow for around 24 hours to complete a much larger FTP backup to my NAS to test this further.
If I abort and restart the backup job it hit the same error at exactly the same GB amount (always when it's XX.XX GB).
What is the actual XX.XX GB value that you are seeing here? From your log information, this looks to be over 60GB (based on file: WindowsDisk_FTP_encr_full_b1_s1_v32.tib) where each of these 32 files would be of 2GB size.
- Log in to post comments

With the Windows disk backup it's like you say always when file #31 hits around 1.8 GB.
So it's at about 61,8 GB when the error happens. But when I do the other backup it happens at a later point like 80 GB or so. But that other point is consistent as well.
The whole backup is 65 GB. The other one with files and folders is about 210 GB.
SMB and FTP is equally fast for me. The smaller backup takes about 2 hours or so including validation.
There's a reason I need to use FTP for this, I can't just switch to SMB. So I hope this will be patched soon.
- Log in to post comments

I have tried a disk & partitions backup via FTP to my NAS with a total size of 76.6GB where 66.5GB was transferred by FTP without any issue showing up.
The log for the backup task showed the following entry towards the end of the log.
18/10/2018 23:03:20 :535 The following backups have been successfully created: ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v1.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v2.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v3.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v4.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v5.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v6.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v7.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v8.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v9.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v10.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v11.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v12.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v13.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v14.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v15.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v16.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v17.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v18.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v19.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v20.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v21.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v22.tib
ftp://192.168.0.29:21/Backup/Test/FTP2toNAS_full_b1_s1_v23.tib
18/10/2018 23:03:27 :535 Operation has succeeded.
- Log in to post comments