Syncovery Support Forum

OK maybe I uploaded some files with the old settings and did not delete them. I will delete the integrity error files and continue uploading,

If I run the sync in "attended" mode, Syncovery shows that it won't make an update to this file.

I am still running into problems. I have 32mb file in my backup. Then: Test Integrity shows an error. Manual download and unzipping the encrypted-zip file does not succeed. So the problem is confirmed. The file at PCloud is only 7MB of size. So there is a problem. The zip file was uploaded to Pcloud...

The new version 10.1.0 now always uses temporary filenames for uploading to PCloud. I have also implemented improvements to the Binary Comparison during the folder scanning phase, but "Test Integrity" is actually more efficient and faster for this purpose. Not sure I understand. Test Integrity with...

Yep thanks got it

Yes but it is not feasible to do that after every sync.

Are you saying that the resume option + verify copied files is not 100%?

I tried that option but found it not resuming indeed . I will test it.

I think making these settings optional is a little dangerous. Users can’t have that knowledge. What about making that a hard coded setting?

Are there any other parameters I should care more about?

Got it. After the bugfix I will still reupload everything with the same setup to see if this was the problem.

Thanks that gives me hope.

Did you find out why the „verify copied files“ did not catch the error? Or maybe it did but did not delete? Or maybe it never got that far?

OK, and then there was in fact one corrupt zip file in my test. But the upload error was reported when uploading. Did your upload log file show any errors in the result summary? The error in my case was: Exception uploading Tobias_2020~1.mgb.s48448891.zip: Synapse TCP/IP Socket error 10060: Connect...