par2cmdline VS BorgBackup

An alternative is including PAR2 files.

Not only that but if you budget for an expected error rate of let's say 10% you can use par2 to create additional files that add that redundancy to your archives.

https://github.com/Parchive/par2cmdline

That's the same reason I do archive files. For parity I personally use (https://github.com/Parchive/par2cmdline) which does create extra files, so I can see how WinRAR would have something to add there.

Here's the first example I could find.

https://pthree.org/2014/04/01/protect-against-bit-rot-with-p...

Basically, you take a normal TAR file and creates external parity files that can be used to recover data in the case of bitrot. Something like this would have been great to have on a few data files I had to retrieve from tape that ended up with a bit flip somewhere in the network > disk > tape > disk process.

However, it doesn't look like the program is maintained anymore...

http://parchive.sourceforge.net/

> DISCLAIMER: This project web space is not actively mantained and is presented here for archive purposes. However some project members still montior the project mailings lists if you have questions. (sic)

The last release was in 2004 (Wikipedia says it was active until 2015, but I don't see that).

Check out par2. I don't know personally of an open source one except I used QuickPar for Windows in the distant past. There's also multipar: https://github.com/Yutaka-Sawada/MultiPar and parchive: https://github.com/Parchive/par2cmdline

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.