Backup rsync over sftp

NethServer Version: 7.6.1810
Module: backup

I configured a backup with rsync on sftp. The first time the file backup.marker file is created, this error is also generated.

Same thing for subsequent bakups. I have seen that the declared port is the 22 actually it would be 1212.

thanks

I think you found a bug (the code might be missing the port parameter, unless the port is set on another phase):

and same goes for sftp on restic:

The output message you got is from rsync_tmbackup script (which accepts the port parameter).

I think that’s not a bug, but a missing feature: a custom SFTP port.

Sorry, i am wrong!
The prop exists…


and it’s called SftpPort
Maybe a sort of getprop SftpPort could output 22
Therfore, a correct setport could do the workaround for lacking interface… The db toolbox seems here
https://wiki.nethserver.org/doku.php?id=howto:db_command_tutorial
But…
This Backup is the configuration backup? or it’s a “data” backup called backupconfig?

'cause Cockpit Interface handles the SftpPort…


And Rsync + Sftp is part of “cockpit only” version of Backup (multiple backups).

(and I cannot generate an SFTP test configuration without an SFTP host to “test”)

I’m using restic over sftp on port 2222 without problems.

I’ve reproduced the bug of rsync over sftp on non standard port.

2 Likes

this backup is “data” backup called backupconfig.
I created the backup in the well and set the port to SFTP Port to 1212. At the first run the system correctly writes the backup.marker file but fails and returns the error I indicated above.

Issue:

Please @AndreLinux something to test https://github.com/NethServer/dev/issues/5804#issuecomment-524893472

Could you verify the issue

yum install http://packages.nethserver.org/nethserver/7.6.1810/testing/x86_64/Packages/nethserver-backup-data-1.6.0-1.1.gae9821d.ns7.noarch.rpm
1 Like

Hi Stephane,

thanks for everything,

do you think I can install it in a production environment?

Yes, it’s safe :wink:

1 Like

The issue has been fixed.

1 Like

I confirm that the issue has been solved.

thanks

2 Likes