Actually, I was thinking of rolling hourly/daily/weekly backups and I didn't understand how I would set that up with your program. Would I have to sync the same source to multiple destinations on different schedules? That seems inefficient compared to e.g. http://www.mikerubel.org/computers/rsync_snapshots/
Please don't get me wrong, I'm not trying to denigrate the software you've written! I was just surprised to see it marketed as a backup tool instead of a file synchronization tool.
The git packfile format is neat; I'm sure you can get some inspiration from https://github.com/bup/bup (which uses it) and http://obnam.org (which has it's own format).
We occasionally get questions from clients about using some file sync tool or another for their backups, and we are very firm with them: file sync is not a backup.
It looks like your software protects to some extent against accidental deletions of files, which puts it far ahead of most file sync tools. But, if it's still possible to accidentally delete the contents of a file or otherwise corrupt it, then it's not a backup.
We usually end up recommending Acronis TrueImage, which is in the same price range as your software. I'd happily recommend your software instead, since TrueImage is clunky and slow, but without archiving it doesn't count as backup software.
(For one real-world example: we had a corporate client get hit by Cryptolocker. It looks like in this case your software would've automatically copied the changed files over to the backup directory; is this the case, or am I missing something?)
This reminds me how every time someone posts a salad recipe to /r/cooking the whole discussion inevitably converges to the topic of a salad without a mayo not being a real salad ... just as it is not a salad with the mayo :)
Every backup has a set of risks that it mitigates. If the goal is to mitigate human errors, then, yes, versioning/archiving is a must. However if someone just needs to have a daily snapshot of their photos and documents to protect them against fire of theft, then you can certainly call it a file sync, but it still is a backup. To each his own. "Backup" is not an exact term, but rather a range of data protection techniques.
> "Backup" is not an exact term, but rather a range of data protection techniques.
We're trying to narrow the range of things that people consider a "backup" so that they don't get wildly disappointed in the future. This isn't a matter of taste.
To be fair, if someone casually links to a HowTo for rsync-based snapshots, saying that he can't understand how a mirroring app can be used for setting up rolling backups is a pretense modesty.
What I meant was I don't understand how I could set up an efficient rolling backup scheme using this tool. I included the link to Mike Rubel's page because it demonstrates using hard links to share unchanged files between backups.
Please don't get me wrong, I'm not trying to denigrate the software you've written! I was just surprised to see it marketed as a backup tool instead of a file synchronization tool.
The git packfile format is neat; I'm sure you can get some inspiration from https://github.com/bup/bup (which uses it) and http://obnam.org (which has it's own format).