rsync VS BorgBackup

rsync can be used to synchronize a local disk to the pCloud drive p. Works similarly as the Sync option of the pCloud Drive app. May be useful if one prefers a bulk upload once a day over a continuous synchronization.

Tools that can be used to handle this include Rsync, Duplicati, Cohesity

To overcome this issue, you can use rsync, a powerful command-line tool for synchronizing files and directories, along with a bash script that excludes the node_modules folder and also filter out anything in a .gitignore file that you specify. In this article, I'll guide you through the process of setting up and using this bash script to sync your Node.js project while ignoring the node_modules folder.

On OL9 I installed rsync using https://github.com/WayneD/rsync/blob/master/INSTALL.md and installing dependencies using the For Fedora 33 commands where possible except xxhash which wasn't found, so I used https://oraclelinux.pkgs.org/9/ol9-codeready-builder-aarch64/xxhash-devel-0.8.1-3.el9.aarch64.rpm.html

rsync will probably work better for this use case

I would prefer to use a revision control system, like git if keeping multiple versions of documents is important. Otherwise, if you don't find anything else to your liking, you could write your own scripts based on rsync with the clone-dest, detect-renamed, and detect-renamed-lax patches.

Give rsync a try, it should handle UTF filenames just fine.

While researching this issue I stumbled upon this thread where someone found out that a rsync 3.2.3 / glibc bug (github issue) leads to the error Operation not supported (95).\ my Proxmox instance is also using rsync 3.2.3: root@proxmox:~# rsync -V rsync version 3.2.3 protocol version 31 In this thread I found it's recommended to upgrade to another rsync version, but I'm not really sure how.\ \ Any thoughts on this?

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.