The day started with such promise...
I installed v9.2.1 last night and did not get a chance to test the remote FTP capability until now.
The remote FTP backup STILL does not work. I can FTP the backup manually with command-line FTP and with FTP Client (File-zilla) on the server to my FTP server in my office. However, when I backed up one domain, the backup was 90Meg (config+content-mail). The zip file actually FTP'ed ok even though the backup reported that it failed:
<?xml version="1.0" encoding="utf-8"?>
<execution-result status="error">
<object name="backup" type="backupowner">
<message code="ApplicationException" severity="error">Cannot export dump file 'clients\xxx\domains\xxx.com\Manual_xxx.com_info_0904301800.xml' to 'ftp://[email protected]//' [Transport error: unable to send directory to repository: Transport error: unable to put local file C:/WINDOWS/TEMP/repo_transport_tmp_01c9c9e799b25780/manual_xxx.com_0904301800.zip to manual_xxx.com_0904301800.zip: Curl error: a timeout was reached]</message>
</object>
</execution-result>
However, on another domain where the backup file was 141 Meg, it errored with the same error message, but with that one, the backup was ALSO corrupt.
On the bright side, the ftp transfer went much faster, but still not much help when the backup file reports that it failed, and the actual backup file is corrupt.
Guess I'll be waiting ANOTHER 6 months for the next "fix".
I installed v9.2.1 last night and did not get a chance to test the remote FTP capability until now.
The remote FTP backup STILL does not work. I can FTP the backup manually with command-line FTP and with FTP Client (File-zilla) on the server to my FTP server in my office. However, when I backed up one domain, the backup was 90Meg (config+content-mail). The zip file actually FTP'ed ok even though the backup reported that it failed:
<?xml version="1.0" encoding="utf-8"?>
<execution-result status="error">
<object name="backup" type="backupowner">
<message code="ApplicationException" severity="error">Cannot export dump file 'clients\xxx\domains\xxx.com\Manual_xxx.com_info_0904301800.xml' to 'ftp://[email protected]//' [Transport error: unable to send directory to repository: Transport error: unable to put local file C:/WINDOWS/TEMP/repo_transport_tmp_01c9c9e799b25780/manual_xxx.com_0904301800.zip to manual_xxx.com_0904301800.zip: Curl error: a timeout was reached]</message>
</object>
</execution-result>
However, on another domain where the backup file was 141 Meg, it errored with the same error message, but with that one, the backup was ALSO corrupt.
On the bright side, the ftp transfer went much faster, but still not much help when the backup file reports that it failed, and the actual backup file is corrupt.
Guess I'll be waiting ANOTHER 6 months for the next "fix".