remote backups (by ssh) do not work?

Asked by Anton

When I try to set up a remote backup using nssbackup-config-gui, it fails with the message:

No plugin could deal with that schema 'ssh://<user>@<host>/<directory>/'

of course, <user>, <host> and <directory> were real values, I removed them for security.
In fact, I use the exact same setting that does work in sbackup.

I'm running on a fresh copy from source (Mon 27 Apr 10:46), freshly made and freshly installed.

I have not been able to find known issues with ssh remote backups, only ftp related problems seem to be reported.

Question information

Language:
English Edit question
Status:
Expired
For:
nssbackup Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said :
#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Anton (feenstra) said :
#2

Launchpad Janitor wrote:
> Question #68896 on NSsbackup changed:
> https://answers.launchpad.net/nssbackup/+question/68896
>
> Status: Open => Expired
>
> Launchpad Janitor expired the question:
> This question was expired because it remained in the 'Open' state
> without activity for the last 15 days.

At the risk of annoying people, I'll repeat my origional question. I'd
like to add, that the failure of making remote (ssh) backups prevents me
from using/testing nssbackup *at all*. This also removes my incentive to
work on resolving (other) issues in nssbackup. So, basically, my
question is if anyone can confirm that ssh remote backups do not work.
Then, with some pointers, I'd like to try and fix this.

Details from my previous question:

When I try to set up a remote backup using nssbackup-config-gui, it
fails with the message:

No plugin could deal with that schema 'ssh://<user>@<host>/<directory>/'

of course, <user>, <host> and <directory> were real values, I removed
them for security.
In fact, I use the exact same setting that does work in sbackup.

I'm running on a fresh copy from source (Mon 27 Apr 10:46), freshly made
and freshly installed.

I have not been able to find known issues with ssh remote backups, only
(different) ftp related problems seem to be reported.

Best wishes, and hoping for some reply from someone.

Anton.

Revision history for this message
Anton (feenstra) said :
#3

Launchpad Janitor wrote:
> Question #68896 on NSsbackup changed:
> https://answers.launchpad.net/nssbackup/+question/68896
>
> Status: Open => Expired
>
> Launchpad Janitor expired the question:
> This question was expired because it remained in the 'Open' state
> without activity for the last 15 days.

At the risk of annoying people, I'll repeat my origional question. I'd
like to add, that the failure of making remote (ssh) backups prevents me
from using/testing nssbackup *at all*. This also removes my incentive to
work on resolving (other) issues in nssbackup. So, basically, my
question is if anyone can confirm that ssh remote backups do not work.
Then, with some pointers, I'd like to try and fix this.

Details from my previous question:

When I try to set up a remote backup using nssbackup-config-gui, it
fails with the message:

No plugin could deal with that schema 'ssh://<user>@<host>/<directory>/'

of course, <user>, <host> and <directory> were real values, I removed
them for security.
In fact, I use the exact same setting that does work in sbackup.

I'm running on a fresh copy from source (Mon 27 Apr 10:46), freshly made
and freshly installed.

I have not been able to find known issues with ssh remote backups, only
(different) ftp related problems seem to be reported.

Best wishes, and hoping for some reply from someone.

Anton.

Revision history for this message
Launchpad Janitor (janitor) said :
#4

This question was expired because it remained in the 'Open' state without activity for the last 15 days.