
With that said, let’s see what’s available. Note: Of the following backup solutions, only Duplicati is licensed as open source. And, I will be demonstrating on the Elementary OS platform, but all of the tools listed will function on most Linux desktop distributions.

I’ll also be focusing on various, consumer-grade cloud services (e.g., Google Drive, Dropbox, Wasabi, and pCloud ). I will focus on GUI tools, because they offer a much lower barrier to entry to many of the CLI tools. And because Linux powers the cloud, many services offer Linux tools.

Why is that such a game changer? By backing up to the cloud, you have access to those files, from any computer you have associated with your cloud account. What makes the cloud really important to users, is when it’s employed as a backup. The file was corrupted.We have reached a point in time where most every computer user depends upon the cloud … even if only as a storage solution. Question is if you had any of these really corrupted files, or just the Alternate Data Stream extraction problem mentioned in my previous reply. I will check what's the best way to do this. So, what we need is a complete verification in an additional profile run, similar to "Test Backup Integrity", which eventually re-uploads any corrupt files. Normally Syncovery deletes the incompletely uploaded file, but if the server does not accept any API requests for some time, the deletion may fail and leave an incomplete zip file on the server. Such errors are Internet communication or server problems.

Did your upload log file show any errors in the result summary?Įxception uploading Tobias_2020~1.:Ĭonnection timed out, in SendBuffer, FNonBlockSendTimeout=80000 (ESynapseError), CP:SynHttpsPutRaise4 OK, and then there was in fact one corrupt zip file in my test.īut the upload error was reported when uploading.
