NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Rsync over SSH to Digital Ocean Droplet
Hi, when stting up a backup job I am struggling to get my Ultra6 to connect to my remote Digital Ocean Droplet , so it can download ald locally store backups from there. I have added the SSH publ...
Hi thanks - looks like you were on to something with missing 'ReadyNAS' account.
I tried and apparently succeeded in adding an account by this name in Linux, but still no luck - but when I tried logging in as 'root' instead from ReadyNAS, the connection tested as ok. However I was not able to browse for the source directory (browse button was greyed out)
Manually enetering the source path, then running a backup it looks like remote directory and contents were found, but copying failed; giving 'Disk quota exceeded (122)' error.
The selected directory to sync contains only 90mb, and to my knowledge I have not set any quotas at source or destination.
Where is this error likely comming from?
One possibly relevent clue - when I use PuTTY to acess the Digital Ocean droplet server as root, I have to supply a pass phrase related to my root SSH key to log in . Supplying of passphrases does not even seem to be an option from ReadyNAS. Does this sound relevent?
ArchPrime wrote:
Hi thanks - looks like you were on to something with missing 'ReadyNAS' account.
I tried and apparently succeeded in adding an account by this name in Linux, but still no luck - but when I tried logging in as 'root' instead from ReadyNAS, the connection tested as ok. However I was not able to browse for the source directory (browse button was greyed out)
To be clear, I think this account is needed on the Digital Ocean server, not the NAS. The key also needs to be connected to this account. (that is, placed into the account's ~/.ssh/authorized_keys).
ArchPrime wrote:
One possibly relevent clue - when I use PuTTY to acess the Digital Ocean droplet server as root, I have to supply a pass phrase related to my root SSH key to log in . Supplying of passphrases does not even seem to be an option from ReadyNAS. Does this sound relevant?
Could be. Have you checked the service status on the server when you are using root?
sudo service ssh status
ArchPrime wrote:
Manually entering the source path, then running a backup it looks like remote directory and contents were found, but copying failed; giving 'Disk quota exceeded (122)' error.
The selected directory to sync contains only 90mb, and to my knowledge I have not set any quotas at source or destination.
Where is this error likely coming from?
You were copying to the ReadyNAS? If so, what was the destination path?
Thanks Stephen
I set up 'ReadNAS' as a username on the Digital Ocean Server (I think) but may not have pulled this off correctly - certianly did not manage to connect to the server from the ReadyNAS device using this user name. (I should probably have picked a different name to avoid confusion!). Not all of the instructions for adding a new user account that I found online worked as describedI gave up on that and ended up adding the ReadyNAS device's ssh public key to the authorized_keys file on the Digital Ocean server for my root account - which at least now allows me to connect as as user 'root' from my ReadyNAS device, Even if I can get no further.
Yes, I am trying to initiate a connection from ReadyNAS device, in order to retrieve the contents of a folder on the Digital Ocean server and save a copy of these to ReadyNAS shared folder
*** EDIT ***
While I was typing this response, it seems the problem has somehow self corrected - I had set up backup interval to once per day, and it so happened that this backup just executed itself automatically, and succeeded! I have no idea why it failed when initiated manually before.
I wonder if being simultaneously logged in as root from my PC via PuTTY helped in some way, or issuing that check status command you suggested somehow shook something loose?:
sudo service ssh status
Either way, much appreciate your help!
ArchPrime wrote:
While I was typing this response, it seems the problem has somehow self corrected - I had set up backup interval to once per day, and it so happened that this backup just executed itself automatically, and succeeded! I have no idea why it failed when initiated manually before.
That is mysterious (not sure how it would resolve a quota error), but if it is working, then all is well. You should manually check the destination folder on the NAS, just to make sure everything is ok.
If you are doing incremental backups, you can combine this with custom snapshots on the destination share to give you some retention (ability to roll back to previous versions). There is a setting there to only make snapshots when there are changes.
Note there is also an option in the advanced settings that will delete files on the destination (readynas) when they are deleted in the source (digitalocean). I use that option for my own backups (together with the custom snapshots). Then the main share has the same contents as the source, with older files (deleted, renamed, etc) saved in the snapshots.
Tkanks Stephen - that makes sense.
For anyone else tryingto do the same thing, below is the process that eventually worked for me:
Enable SSH on ReadyNAS https://kb.netgear.com/30068/ReadyNAS-OS-6-SSH-access-support-and-configuration-guides
Use PuTTy to access Digital Ocean server and type
nano /root/.ssh/authorized_keys
in the editor, copy-paste in the public key used by ReadyNAS, appending this at the end of the /root/.ssh/authorized_keys file (be careful to not overwrite any keys already present).
In the ReadyNAS backup dialog settings, I used::
Name: Backup via Rsync over remote SSH (drop down selection)
Host: mydomain.com (or server IP address)
Port: 22
path: /var/discourse/shared/standalone/backups/default (the path to files I want backed up on host - change to suit your own situation)
Login: root(Noting that if you followed the instructions for setting up ReadyNAS for SSH access correctly, no SSH passphrase will be associated with its public/private SSH key pair. This is rather important, as the ReadyNAS backup dialog does not provide for a passphrase)
As noted, at first this process did not work fully for me - using the ‘Test’ button in the ReadyNAS backup dialog with these settings did result in successful connection, but then initiating a backup generated error ‘Disk quota exceeded (122)’
But then a couple of hours later, without further (obvious) intervention on my part, when the backup process initiated itself again on its auto designated hour, this time it just worked as it should.Possibly my previous efforts at achieving a connection and testing using different settings were having some residual effect that impeded things at thetime, or perhaps being simultaneously logged in to the server from my PC as root via PuTTY at the same time as root via FileZilla (both using the original/default SSH public key associated with root) and then trying to log in as root via ReadyNAS device backup utility (using ReadyNAS’s public key that I added to authorized_keys file for root) was problematic.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
