Hacker News Reader

Comment by mekster | Hacker News Reader

Too bad they couldn't target S3 endpoints or anything other than SSH for remote target on this breaking change or else it would've been the best of the bunch.

View on HN

I'm wondering if there's a less painful way to use Borg with https://rclone.org/ than just maintaining a local Borg repo and then syncing that.

Theoretically you can mount rclone to a local directory, but realistically it doesn't work because in the absence of serverside borg it is very heavy on network IO and slows to a crawl, even for sshfs over a short physical distance. To use it remotely, you really need to have borg installed on a server. I currently do as you describe.

I've used it with an rclone mount, it seems to work fine. See https://github.com/rclone/rclone/issues/3641.

The GitHub ticket hints that support for cloud storage backends (s3) might come in a future release:

  as you see above, there is already a huge scope of what should be done.
  to not grow the scope even further, some stuff shall not be done (now):
    * no new locking system
    * no public key cryptography (neither by gpg nor by reinventing gpg for borg)
    * not adding cloud storage backends (like s3)

https://github.com/borgbackup/borg/issues/6602

Take a look at Duplicacy, it's the only one that really hits all the sweet spots.

Until it exhausted the memory for the instance to become completely unresponsive.

Feature list is only half of what it is.

This has not been my experience at all.

Can you explain in more detail?

Duplicacy has been one of the best pieces of software I've ever used.

Reply on news.ycombinator.com