Replies: 2 comments 1 reply
|
When using
The borg client tries to start borg on windows is rather experimental, so the smb mount method might be more stable and tested for such a setup. |
1 reply
|
Closing this as outdated: it has seen no activity for a long time and predates the current borg releases. If this still affects you on a current version - borg 1.4.x (stable) or the borg 2.0.0 beta - please open a new discussion with up-to-date details. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I am using borgbackup under Rocky Linux 9.2.
My repository is stored on a mounted SMB file system from a Windows machine. The command:
borg list /mnt/borgpath
correctly lists the contents of my repository, so I am confident that I have borg operating properly. Also, I have borg create running every two hours on a cron job and it reports success every time.
I am trying to get rid of the need to mount the SMB share. After a considerable struggle, I got sshd running on the Windows machine, and I am able to ssh into the Windows machine The command:
borg list myname@WindowsMachineIP:/SMBsharename/borgpath
first asks for an ssh password as expected. But then I get messages from the remote Windows machine that borg is not recognized as a command. Then "Connection closed by remote host. Is borg working on the server?"
What am I not understanding? I didn't expect to need borg running on the Windows machine providing the SMB share.
All reactions