- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
SFTP backup From(!) ReadyNAS TO external sftp server (port22), how?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
On my RN424 I like to backup to a remote server via SFTP, but the RN424 only seesm to know FTP. But FTP is not accepted by my remote server. How to use SFTP?
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Solution found: Provider supports SSH shell access on another server with access to smae files as with the ftp server. If I use the shell access server I am able to do rsync with it.
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: SFTP backup From(!) ReadyNAS TO external sftp server (port22), how?
Rather than using SSH File Transfer for this, use Rsync over SSH instead. Rysnc is much more optimized for backups and there is a facility in the GUI to set it up.
https://kb.netgear.com/29929/ReadyNAS-OS-6-Setting-up-a-backup-job-with-rsync-over-SSH
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: SFTP backup From(!) ReadyNAS TO external sftp server (port22), how?
For rsync I need to add the public key of the ReadyNAS,
I added it to ~/.ssh/authorized_keys file.
But a connection seems not to be working. I doubt whether the sftp server accepts rsync.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: SFTP backup From(!) ReadyNAS TO external sftp server (port22), how?
But yes, you need to do keys for authentication which is more secure anyway. It's very easy to setup though.
The connection test fails due to authentication because you haven't done the key "exchanges" yet.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: SFTP backup From(!) ReadyNAS TO external sftp server (port22), how?
You did the key exchange. Misread.
What path do you enter on the NAS? The remote path.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: SFTP backup From(!) ReadyNAS TO external sftp server (port22), how?
Just the name of a directory which exists on the sftp server without any slashes: RN
Even if I add the full path to my directory /home/some-path-to-my-directory it does not work, although now testing my connection says the connection failed istead of doing nothing.
Please note that I am not the owner of the sftp server, so I can only access my own directory and added the ,ssh/authorized_keys file to it,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: SFTP backup From(!) ReadyNAS TO external sftp server (port22), how?
Ok, so that won't work. You gotta specify full path here. Would have been the same if using something SFTP.
Starting with the / and it is case sensitive.
For example:
/home/myuser/RN
If it still does not work, PM me and give me screenshot of the settings on your backup job. I don't want you to post any public IPs here 🙂
Also, ensure you select "Rsync over Remote SSH" on the backup jobs page.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Solution found: Provider supports SSH shell access on another server with access to smae files as with the ftp server. If I use the shell access server I am able to do rsync with it.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: SFTP backup From(!) ReadyNAS TO external sftp server (port22), how?
@PeterBremer1 wrote:
Solution found: Provider supports SSH shell access on another server with access to smae files as with the ftp server. If I use the shell access server I am able to do rsync with it.
Great. Though I guess we'd have to call it a work-around, I think it will actually work out better for you.