ioztat VS BorgBackup

Also: https://github.com/jimsalterjrs/ioztat

It might be worth installing and firing up ioztat to see if you can identify where you're experiencing the latency issues.

Have you considered using ioztat to try to isolate the problematic bits of the workload? If you go this route, it would help to carve your home directory (or wherever you're doing the most work that hits disk) into discrete datasets--eg make ~/Pictures, ~/Videos, ~/Documents their own datasets.

See if someone asked me had I done anything with zfs after I was bragging about it, I might just link to this: https://github.com/jimsalterjrs/ioztat/blob/main/ioztat

While we're on the subject of testing ZFS scripts, I've done loads with ioztat — /r/zfs' answer to zfs iostat — and plan on releasing 2.0 soon. If you want to kick the tires on that, now is certainly the time to do it.

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.