One tip for using Duplicati. Duplicati will create a local DB file on the source PC. It will be stored somewhere in user's home folder. On Windows, it is under AppData hidden folder. It is better to back that local DB somewhere manually or using a scheduled job. If the source PC crashes, and your local DB is lost, my understanding is that you can still recover all your data but recovery is slow.
Thanks for the tip! I will be sure to have that backed up as well. I noticed that you can run a script after a backup, maybe I will add a robocopy batch file to my Windows machines and a rsync bash script to my parent's Mac to have this done automatically.
On a related note, do you have any experience using public/private keys with Duplicati and ssh? I have been able to get key files to work but I would prefer to have the key included with the Duplicati config. Each time I add the URL-encoded private key to my Duplicati config, I get an error stating that the key is too long. I would prefer this method if I can get it to work so that I don't have to worry about anyone accidentally deleting/moving the key file on their PC.
Main: Intel i7-5775C w/ Noctua NH-D14, single fan | Gigabyte Z97X-Gaming 7 | EVGA GTX 1070 FTW | GSkill DDR3-1866, 32GB | Corsair Pro 750W Gold
HTPC: AMD A10-7850K | ASRock FM2A88X-ITX+ | GSkill DDR3-2400, 8GB | Silverstone SFX 450W