Hacker News Reader

Comment by ahnick | Hacker News Reader

Duplicacy has been incredibly stable for me over the years and I still prefer it's lock-free deduplication design. Looks like 28 days ago there was a major release as well. Time to upgrade. :)

https://github.com/gilbertchen/duplicacy

View on HN

Agreed, duplicacy seems to be more resilient to the inevitable errors or hiccups along the way. The only downside is that it seems to be inefficient with storage with small metadata updates which happen frequently with my use case.

Another happy long-term Duplicacy user here. My only problem with it is; on the rare occasions I need to restore something from backup, I can never remember the correct syntax and always have to look it up again.

Make a script!

Or a do-nothing script if you don't want to automate it right away.

https://blog.danslimmon.com/2019/07/15/do-nothing-scripting-...

Never seen that concept before. I've done similar in the past using aliases in my ~/.zshrc

  alias taskname='echo "blah. blah... instructions for task..."'

Of course, then I have to remember what nemonnic I used for 'taskname'!

I had the exact same reaction. I have little "README.md" text files scattered about to remind me how to do things and never thought to make an interactive post-it note.

Same. I ended up writing the steps in a file because I could never remember them. It's not very complicated but a bit counter-intuitive: instead of pulling everything from the remote you first have to recreate "repository" with the same parameters as the original one, and _then_ run the restore command.

Note, its not open source. Duplicati is.

It seems to be open source (source code is in github), but the license isn't free for commercial use. I'm not exactly sure what to call it...

Source-available, I guess.

Source available

Proprietary Source available

Reply on news.ycombinator.com