restic VS BorgBackup

Restic - GitHub

I religiously use Google contacts. It's the simplest way to keep people contacts up to date on Android.

I archive all important documents in specific folders by subject and date. This is backed up to back blaze with restic. https://restic.net/

I use https://ente.io for pictures. I convinced my wife to use it, and she agreed to auto share her photos so I don't nag her for copies. It had simple import from Facebook and Google.

I also keep extensive journals, which really helps to tie it all together. I can basically grep for hangouts, conversations, etc.

I also separate work journal from personal, and have essentially a journal for each project. https://jodavaho.io/tags/bullet-journal.html for how.

I religiously use Google calendar for all plans, you can easily search it for past events to get dates.

I also use monicahq for some notes about things I should remember about people but the habit never stuck.

After Borg, I switched to Restic:

https://restic.net/

AFAIK, the only difference is that Restic doesn't require Restic installed on the remote server, so you can efficiently backup to things like S3 or FTP. Other than that, both are fantastic.

I'm curious, too. I know they've had some issues in the past:

https://github.com/restic/restic/issues/3268#issuecomment-78...

On the other hand, I tested around 15,000 backups last year (multiple hourly backups, daily tests) and they all passed.

I use and recommend restic. I use it for about 60 machines on my LAN, and it's absolutely fantastic.

i use - and recommend - "borgbackup": for example with the "vorta" graphical frontend

* https://www.borgbackup.org/

* https://vorta.borgbase.com/install/windows/

just my 0.02€

I used this many, many years ago but switched to Borg[0] about five years ago. Duplicity required full backups with incremental deltas, which meant my backups ended up using too much disk space. Borg lets you prune older backups at will, because of chunk tracking and deduplication there is no such thing as an incremental backup.

[0] https://www.borgbackup.org/

Currently, I'm auto-backing it up with borg (push mode) through wireguard tunnel to NAS behind ISP's CGNAT. The borg takes care of deduplication in SQL file, so incremental update (even in append-only mode) is very small for PostgreSQL dump.

Borg 2 has been in development for nearly a year and a half [1] and may probably be released early next year, i.e., early 2024 (just a guess, seeing that even RC1 is not yet released and seems to have a lot of work to be done).

Does anyone know how Borg 1.x and 2 would compare to Kopia?

[1]: https://github.com/borgbackup/borg/issues/6602

You could use borgbackup.