I’m still getting up to speed with testing Syncthing so this is definitely a “living post” (expect edits) and any input from existing users would be appreciated! This post is a Wiki, so feel free to add / fix anything you deem necessary.
Syncthing (https://syncthing.net/) is an mutli-platfrom (Windows, Linx, Mac, Android, etc.) Open Source P2P (person-to-person) tool for syncing files between multiple devices.
The reason I’m mentioning it here is that it supports versioning of synced files in a way that could be used for backup purposes. (See docs @ 2.14. File Versioning — Syncthing v0.14 documentation)
|x||*||Backup tool (*Per Syncthing docs “
|x||*||Cloud destinations supported (*Clouds visible as local mount points MIGHT work)|
|*||x||Peer-to-peer destinations supported (*Peers visible as local mount points or accessible via VPN or SSH routing MIGHT work)|
|x||*||File versioning (*Syncthing versioning makes copies of entire files)|
|x||x||Multiple OS support|
|x||x||Free (donations accepted)|
|x||“Real time” scanning (Syncthing defaults to scans every 60 seconds but DOES support real time)|
|*||x||One-to-many copies (*Duplicati can do it but requires multiple jobs)|
|x||x||CLI (Command Line Interface) available|
|x||x||Web based UI|
|x||Application based UI (third party GUIs have been developed for the likes of Linux, Windows, and Android)|
|x||*||Supports UAT (*Syncthing handles some permissions)|
|x||x||Files handled in smaller blocks to reduce bandwidth on file changes|
It should be pointed out again that while Syncthing does support versioning, it does so by making a duplicate copy of the file with a timestamp. This means if you make a 1k change to a 200MB file, Duplicati will (by default) need ~1k more space at the destination while Syncthing will need 200MB (for a full copy of the file).