Complete F5 Automated Backup Solution
Updated Jun 06, 2023
Version 2.0Was this article helpful?
@Xian Zhong: I've probably found the reason for this issue. My customer encountered the same issue, when he was using the FTP transfer method from the iApp. It seems, that the iApp is using ASCII instead Binary transport to the FTP server (ASCII is the default mode of the builtin ftp client in Linux). Therefore the compressed file is corrupted. The issue was solved by using SCP/SFTP for transfer.
If necessary you can repair the broken files on your FTP server by using "fixgz" (http://www.gzip.org/faq1)..) It worked for me to rescue the corrupted files.
@Thomas: If you would add the command "binary" to the scriptfile before the transport starts (put command), it should work as expected.
Regards, Sven