Some users reported the inability to perform backups from CloudBerry Backup to Syncplify.me Server! Free Edition.
Therefore we have analyzed the situation, and this is what we have discovered:
- By default CloudBerry Backup tries to use 5 (five) concurrent connections to your SFTP server
- The free edition of Syncplify.me Server! is limited to 3 (three) concurrent connections, and drops/cuts the 2 connections that exceed such limit
Since the number of concurrent connection cannot be changed in Syncplify.me Server! Free (hey, after all, it’s a forever-free product for personal use only) then our recommendation is to set CloudBerry to perform 3 concurrent connections instead of 5.
There is also another issue, though, which is much worse: as you can see from the following (contiguous) two lines taken directly from our server’s log file, CloudBerry Backup basically tries to create the same directory twice, the first time without the trailing / (slash) and the second time with the trailing / (slash).
2014-11-18 17:34:58 127.0.0.1 test 127.0.0.1 22 MKD /CBB_WIN-O41SFO31KTU/CBB_Configuration/settings.list$/20141118170244 - 250 0 0 EldoS.SFTPBlackbox.8 3B15186C-63A8-455E-8483-874F60AA348E SFTPv4 created+directory+/CBB_WIN-O41SFO31KTU/CBB_Configuration/settings.list$/20141118170244
2014-11-18 17:34:58 127.0.0.1 test 127.0.0.1 22 MKD /CBB_WIN-O41SFO31KTU/CBB_Configuration/settings.list$/20141118170244/ - 550 0 0 EldoS.SFTPBlackbox.8 3B15186C-63A8-455E-8483-874F60AA348E SFTPv4 cannot+create+directory+/CBB_WIN-O41SFO31KTU/CBB_Configuration/settings.list$/20141118170244/+(directory+already+exists)
The second time CloudBerry Backup tries to create such directory, Syncplify.me Server! correctly replies with an error code (cannot create a directory that already exists). But apparently CloudBerry Backup mistakes such error for a fatal condition, and therefore considers the backup operation as “failed” (and does not continue the process). But the problem is that CloudBerry should not try to create the same folder twice in the first place.
This second issue is obviously not limited only to the interaction with the Free edition of Syncplify.me Server. Our team is at work to find a workaround as this post is written. We may come up with a solution on our side, but we will also contact CloudBerry Labs to report the issue to them.