s3cmd VS BorgBackup

did you try this? https://github.com/s3tools/s3cmd/issues/1356

You could also use s3cmd via a drush or bash script to sync what you need

In order to configure this thing you can use a tool named s3cmd. It's available from brew.sh.

I have a cronjob that runs hourly which creates a tarball and then uses s3cmd to push files to Amazon S3. It also removes local backups that are older than 3 hours old, and retention policy removes S3 backups older than 7 days old.

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.