Richard Browne May 5 7:27AM 2017 GUI
Hi I was testing duplicacy as a replcement for Crashplan. Unfortunately for my trial I can only report that it didn't work.
I installed Duplicacy yesterday on our server. Configured it to backup our repository. The GUI told me 2 days.. then 3 days.. I woke up this morning and it tells me 7 days.. Tonight I logged in and ... just nothing. It's as if I had never even started a backup.
In the log tab a recent message says "07:31:16.997 Failed to find the path for the chunk eb74768e9a6f8c6a588dbb198dcfcec807a9503295e591e3c580cc45ef4cdb43: http: read on closed response body"
I get that Lock-Free Reduplication is technically elegant. But sorry this is no replacement for a robust backup solution that actually works.
gchen May 5 9:55AM 2017
Which storage backend are you using?
Richard Browne May 8 4:01AM 2017
I was testing with Backblaze B2
gchen May 8 1:14PM 2017
I suspected the B2 server occasionally may return a 3xx http status code. Currently, only 4xx or 5xx http status codes are treated as errors and handled by a retry mechanism. I think the fix is to treat 3xx status codes as errors too.
I'm busy with a big change to add multithreading support for all storage backends. This fix will be the next job in the queue after that is done.