DUPLICACY VS GOODSYNC UPDATE

I really wanted it to work, given that it's free, is pretty flexible if you're willing to dive into the more hidden features, and runs on pretty much everything. I let it burn me once, but then 2-3 more times and the failed repair and I was out. Luckily, it was just during testing, but it was about 6 months of testing and a lot of time configuring things to perfectly fit my complicated setup. +1 for multiple backup corruption issues with repairs taking multiple days and one never completing. Bash scripting was relatively new to me when I started so at first I just had a short little raw backup script, but every now and then I put a bit of time into improving it little by little. rsync -a -delete -link-dest will make a new incremental backup with hardlinks to all unchanged files, rather than duplicating them). Of course, sync'ing isn't the same as backup, but rsync does have the capability to do snapshots once you get into the advanced features (e.g. No UI, alas, so its going to be all command-line and text logs, but rsync is veeery robust, and if it does somehow fail anywhere the log output is file-by-file with plenty of detail.

DUPLICACY VS GOODSYNC UPDATE

If you're syncing several TB or more the first time you do it will take a long time, but after that rsync will only need to update the files that have changed so it's pretty quick. If you have the time, patience, and/or know-how ( pick 2 :P ) to write a bash script, you can use the User Scripts plugin and add a bash script that periodically runs rsync to sync your files to an external hard drive.

Duplicacy vs goodsync