3 ms·
In the FAQ [1] SSHFS is mentioned a few times and here is the citation where I got this idea from when I read it way back when: “When Borg is writing to a repo
by beermonster 5y ago
In the FAQ [1] SSHFS is mentioned a few times and here is the citation where I got this idea from when I read it way back when:
“When Borg is writing to a repo on a locally mounted remote file system, e.g. SSHFS, the Borg client only can do file system operations and has no agent running on the remote side, so every operation needs to go over the network, which is slower.”
SSHFS would be tool agnostic/transparent though of course would result in operations going over the network as it’s not a local repo, but pseudo-local.
I’m curious, how do you use plain SFTP transport with borg using rsync.net?
[1] https://borgbackup.readthedocs.io/en/stable/faq.html https://borgbackup.readthedocs.io/en/stable/faq.html
- rsync 5y agohmmm ... it appears that I might be the one that is not quite right ... I was positive that there was a less-featured usage mode over plain old SFTP. Either way, having the borg executable on the server side is the "correct" way to do things.
- ThomasWaldmann 5y agoborg does either use a directory as repo (no matter whether local or mounted via network fs) or works client/server via pipes that are usually over ssh (in that case, it needs a remote borg process to talk to). instead of ssh, one could also use anything rsh-like, but of course ssh is the best option here. no sftp inside borg (nor anything else).