Replies: 1 comment 1 reply
-
Hmm. I think your install matches how I run backrest on Windows (re: where things are installed) so that’s a bit surprising— I’d expect the restic command to be the full path to the binary e.g. including C:\ProgramFiles\… are you overriding BACKREST_RESTIC_COMMAND or anything of that sort? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm a bit puzzled on what I did to get my backrest install borked, so I'm hoping someone out there can give me some direction. I've installed backrest on another PC and it has worked fine. Tonight I was setting up on a different windows PC and I was having trouble to a rest server that I was also setting up for the first time. I was getting password errors and such, so I was getting that straighten out on the rest server docker.
I think my issue started when I tried to run the restic-0.16.4.exe on a command line to try to init a rest server repo outside of the backrest UI. But I'm not entirely positive on that point. I don't have a restic folder in appdata, so I'm not sure there doesn't seem to be a cache folder. This is reflected in the restic cache command as well.
At this point whenever I try to create a repo in the UI, even just a local folder, I get the following error:
Operation failed: [unknown] failed to init repo: init failed: command "restic-0.16.4.exe init --json -o sftp.args=-oBatchMode=yes" failed: exec: "restic-0.16.4.exe": cannot run executable found relative to current directory
I have backrest in the program files folder, I'm running the command prompt as admin, I've run the uninstall.sh file, I've deleted the program files folder, and the appdata folder and reinstalled and even restarted the windows machine, and I still get the same error.
I appreciate if anyone can give me some idea on what to try next.
Beta Was this translation helpful? Give feedback.
All reactions