[Syncing only modified chunks in big files?]

Thanks!

On 5/29/2013 at 2:35 PM, nice_furniture said:

Ok, I found this interesting thread:

:

 

"Sync splits file to 4Mb chunks, if one chunk was changed - it will be transferred. It works well on files that doesn't change the size, for example TrueCrypt volume.

 

If you add one byte in front of the file, all chunks will be shifted and Sync will not be able to detect shifted data."

So it seems, Sync has to transfer the whole file all over someone adds something and so changes the file size.

 

[low transfer Rates via internet - 500KB/s to 2,5MB/s]

Did you ever get this resolved?

[.sync/archive Directory]

To anyone starting out - please DO NOT disable Archiving. There are quirks that without intention (using across Android nVidia Shield TV have caused my source files (to the tune of 700GB) converted to 0KB files. Through accident I found the .sync folder (just before I was going to Google) and was able to restore all my files. God bless the soul of whoever thought it was a good idea to enable Archiving instead of deleting by default. I have still not been able to figure out why the source files were changed to 0KB files. This has already happened twice however there is nothing else that give me 20MB/s speeds and the consistency of Reslio so I am stuck with it for now. Personally, I have made the sync one-way only for now so that source files are not be modified.

I strongly suggest, that you leave Archiving and perform a manual cleanup of the folder for a few weeks of continuous syncing so that you have enough test cases for any quirks that may set in.