Updating this as I figured out more about what's going wrong. Basically, I'm having issues with automating offsite backups because backup software can't see the sshfs mount properly.
When I use the command line "net use \sshfs etc" way of mounting the remote folder, I have no problems with setting it as a destination from EaseUS or Paragon backup programs. However, there seems to be no way to use a custom location/filename for my private key in that setup, which I need to do.
On the other hand, when I use the sshfs-win.exe cmd/svc command line approach, or mount the storage using sshfs-win-manager, I can set a custom file path for the key, but the mounted storage shows up as a local drive rather than a network location, and for some reason, backup programs can't see it.
Is there any way to do a "net use" command that gives me more options than the standard use?
Updating this as I figured out more about what's going wrong. Basically, I'm having issues with automating offsite backups because backup software can't see the sshfs mount properly.
When I use the command line "net use \sshfs etc" way of mounting the remote folder, I have no problems with setting it as a destination from EaseUS or Paragon backup programs. However, there seems to be no way to use a custom location/filename for my private key in that setup, which I need to do.
On the other hand, when I use the sshfs-win.exe cmd/svc command line approach, or mount the storage using sshfs-win-manager, I can set a custom file path for the key, but the mounted storage shows up as a local drive rather than a network location, and for some reason, backup programs can't see it.
Is there any way to do a "net use" command that gives me more options than the standard use?