Duplicacy VS Back In Time

Duplicacy Reviews

Back In Time Reviews

Duplicacy mentions (78)

• Duplicity

  Not to be confused with Duplicati [1] or Duplicacy [2]. There are too many backup programs whose names start with 'Duplic'. [1] https://www.duplicati.com/ [2] https://duplicacy.com/. - Source: Hacker News / 3 months ago

• Duplicity

  I have been having great luck with incremental backups with the very similar named Duplicacy https://duplicacy.com/. - Source: Hacker News / 3 months ago

• Restic – Simple Backups

  My recommendation would be Duplicacy [0]. Code is also on GitHub [1]. It has a paid GUI version, $20 for the first year and $5 for subsequent years with discounts for multiple machines [2]. At least once they've run a promotion for a very cheap lifetime license. Use it just from the CLI is free. My setup is pretty simple, Syncthing and Duplicacy (GUI version) run in a docker container on my home server. Everything... - Source: Hacker News / 4 months ago

• Your privacy is optional

  Having all your data in one place isn't wise though, so I am planning on storing encrypted backups on Dropbox and Backblaze B2 using Duplicity so that I am following the 3-2-1 backup rule. - Source: dev.to / 7 months ago

• Ask HN: How do you do backups for personal/home server?

  I tried a bunch of different ways but ultimately settled on Duplicacy [0]. It runs inside a Docker container and backs up both my data as well as configurations like my docker compose file and smb.conf. Off site storage was Backblaze B2, but I moved to Hetzner. Likely will move back just because B2 is cheaper and a bit faster for my region. Another layer of backup I do is use Duplicacy to backup to a portable hard... - Source: Hacker News / 11 months ago

Back In Time mentions (24)

• Opportunity for beginners: Some code cleaning in "Back In Time"

  It is often asked by beginners how and where starting to contribute. As member of the maintenance team of Back In Time (Backup software using rsync in the back, written with Python and Qt) I would like to introduce one of our "good first issues" (#1578). Source: 5 months ago

• Free software project "Back In Time" requests for translation

  I'm member of the upstream maintenance team of Back In Time a rsync-based backup software. No one gets payed. No company behind hit. Even the maintainers and developers are volunteers. Source: 6 months ago

• Why is contributing soo hard

  Back In Time is a round about 15 years old backup software using rsync in the back. I'm part of the 3rd generation maintenance team there. A lot of work in investigating and fixing issues, understanding, documenting and refactoring old code. Source: 7 months ago

• [English -> Portuguese EU / Brazil] Text about attracting translators to a FOSS project

  This request is related to an Open Source project named Back In Time. Everyone there works voluntarily and unpaid. Source: 8 months ago

• Is it normal practice in Github for a valid issue to be closed if the Dev can't work on it at the moment?

  In my own project we do it more transparent. We close if there is a good reason for it. We don't close just because no one is working on something. If there are no resources to work in it now but it seems important we keep it open until it is fixed. We do use milestones and priority labels to give the users an idea about our plans. Source: 10 months ago