This has been a major pain
, and I'm only posting here in case someone has bumped into something similar and found a solution.
I've been in contact with the Backup4All developer, the Hosting provider, the router manufacturer
and we seem to be running in ever diminishing circles with most people excusing themselves, understandably, and saying it's not their responsibility.
OK: What's the story:
I've got a paid-up latest version of Backup4All Pro that I'm using, amongst other things, to back up off-site, via FTP, to my Windows hosted site at LunarPages.com.
No problems at all locally. Plenty of FTP problems though. B4A almost seems incapable of overwriting a file, not all the time, but when it fails (99% of the time) it always fails when it's trying to write a file that exists on the FTP server. It'll do an initial backup and FTP it to my site without problems. When I do another backup, it'll successfully FTP the next *.zip but fail with the catalog.
The B4A devs have investigated the log files and catalog and said the failure is caused by:
I tested B4A using some free FTP space over at 0catch.com and it performed fine without problems, using exactly the same backup job (just changing the destination).
I tried the FTP backup to my site with SyncBackSE and it performed without problems (obviously using the same FTP account: therefore it's definitely not permissions).
So I think I can presume:
It can only be the combination of B4A and my site??? Is that possible
, and I'm only posting here in case someone has bumped into something similar and found a solution.
I've been in contact with the Backup4All developer, the Hosting provider, the router manufacturer
and we seem to be running in ever diminishing circles with most people excusing themselves, understandably, and saying it's not their responsibility.OK: What's the story:
I've got a paid-up latest version of Backup4All Pro that I'm using, amongst other things, to back up off-site, via FTP, to my Windows hosted site at LunarPages.com.
No problems at all locally. Plenty of FTP problems though. B4A almost seems incapable of overwriting a file, not all the time, but when it fails (99% of the time) it always fails when it's trying to write a file that exists on the FTP server. It'll do an initial backup and FTP it to my site without problems. When I do another backup, it'll successfully FTP the next *.zip but fail with the catalog.
The B4A devs have investigated the log files and catalog and said the failure is caused by:
Quote from: B4A Developers
The problem is that the FTP connection is interrupted during the backup.
I tested B4A using some free FTP space over at 0catch.com and it performed fine without problems, using exactly the same backup job (just changing the destination).
I tried the FTP backup to my site with SyncBackSE and it performed without problems (obviously using the same FTP account: therefore it's definitely not permissions).
So I think I can presume:
- It's not a router issue as SyncBack works on my site, B4A works on 0catch.com and Filezilla works on my site.
- It's not a permissions issue as SyncBack works fine.
- It's not my site, as SyncBack works on my site as does Filezilla
- It's not B4A, as it works on 0catch.com
It can only be the combination of B4A and my site??? Is that possible






).
Apparently it's a standard Windows2003 & IIS install, so why would it be mucking up just with Backup4All, or are all other softwares taking a similar approach to get around that "bug"??