I have been trialling duplicacy for about one week now with a OneDrive for Business share (backup every 4 hours, 100GB). Unfortunately, my first
check -chunks complained after 90% with the following message (4 times):
The chunk 1af01dfe5e78b73f16b16b016d5ac4bb5066254711a39909f5df581e6e704bf3 has a hash id of e55b53129e9e1170a74a707f8a8297d6ff0e0ed8263f4a23b383b24c1861d610; retrying
I tried the procedure mentioned here: Restore fails. The chunk... has a hash id of... retrying . A new
backup indeed lists all chunks again and it finishes without an error message. However, a new
check -chunks again complains about the same chunk.
What can be done? I only have 1 week history so I can start again. However, it is not a good sign something went wrong already.
Probably the OneDrive protocol is not the most reliable for transmitting messages, but if it is included in duplicacy, I expect it to be almost perfectly reliable. Would erasure encoding help for these kind of errors?