Replies: 1 comment 2 replies
-
This option isn't properly saved right now. You see it's not in the command. This is already fixed in the master branch and will be released soon. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
TL;DR: When using Homebrew's Borg on macOS as a remote server (to host the Borg repository), add
--remote-path /opt/homebrew/bin//borg
as Extra Borg Arguments.I wanted to backup my computer (running Linux: let's call it the client) to another computer (running macOS: let's call it the server) using Vorta.
I've installed Borg on the macOS/server using this tap (listed on Borg's documentation) and checked
borg --version
was working.But, on the Linux/client when trying to create a repository on the macOS/server via Vorta the add failed without any clear message.
Running Vorta form CLI gave more verbose output highlighting some issue to run Borg via SSH:
Full log:
As I know Borg is installed and working on macOS/server I tried various commands:
ssh user_name@remote_server borg --version
⤇ "zsh:1: command not found: borg"ssh user_name@remote_server which borg
⤇ "borg not found"ssh user_name@remote_server type borg
⤇ "borg not found"Because I know where Homebrew installed borg (
/opt/homebrew/bin//borg
) I can give it and this time it works:ssh user_name@remote_server /opt/homebrew/bin//borg --version
⤇ "borg 1.4.0"Vorta not able to SSH-execute
borg
because it relies on $PATH working fine is not a Vorta bug, maybe something that could be improved (don't know how as I failed to find a simple command to detect the borg location on the macOS/remote).So I'm leaving this here:
Adding
--remote-path /opt/homebrew/bin//borg
in the new repository window's _Extra Borg Arguments_field fixed the issue for me.Edit: Using Vorta v0.8.12 on Linux Mint 22 ("Wilma")
Beta Was this translation helpful? Give feedback.
All reactions