After a few months, I finally came back to my problem and succeeded doing the following
enable SSH on the NAS
log as root welc0me
type the following commands
^O to save to disk, this file will be left empty, but the file needs to be there
^X to exit nano
Type the following into the file
the following path works fine. When you setup the backup task in the Synology, you will be able
to choose the desired WD share
path = /shares
uid = root
gid = root
read only = no
list = yes
auth users = all
secrets file = /etc/rsyncd.secrets
the IP address is the one of the Synology backing up to the WD. This provides some security.
hosts allow = 192.168.1.4/255.255.255.0
^O to save to disk
^X to exit nano
#for the Linux learners like me, that is 2 dash signs in front of daemon
Then go to the SYnology and set up a backup destination as a r-sync compatible server. Enter the IP address of the WD (better to have a fixed one). Enter root and welc0me as the user name and password. Pick the “shares” in the list of modules. Then create a backup task using this destination. At that point, you will be able to pick a WD share as the backup directory for all the Synology data.
Run your backup task.
To start rsync automatically on the WD reboot, do the following:
Sadly, I had so many performance issues with the WD My Cloud perpetually scanning and thumbnailing that I gave up and bought a different NAS. Now my WD has been relegated to a rather expensive backup drive but at least it can do that thank to your excellent instructions.
I am only able to see “shares” when I set up my Backup Task. I do not get the shares I have set up on the WD MyCloud. Any suggestions? Am I doing something incorrectly? Do I explicitly need to enter in a different “share” as opposed to the generic /shares ??
I just bought myself a WD Mycloud 8TB (2nd gen) in the hope I can set it up as a backup device for my Synology NAS. Unfortunately it seems this is not supposed to work, as WD does not support rsync out of the box… One should read technical features before buying I guess…
Now I found this forum and stumbled over this thread! Great, so it does seem to be possible…?!
Unfortunately I have hardly any knowledge of Linux and the instructions at the top seemed ok for noobs like me, but then I stumble over missing commands like “nano” when I logon to the device… I guess this is due to the 2nd gen as the original post seems to cover the 1st gen devices. Now there is the stripped down “BusyBox” on the device, which is not helpful at all … There is vi however, so I could fight my way through this, if necessary I guess…
The welc0me password does not work for root either, I just used my admin pwd, does that make any difference?
Also, there is no file /etc/init.d/rsync where I could change the value as described. Do I need to create a new file with this line in it?
Is there anyone who has written down this step-by-stepps for Linux beginners like me?
I am desperate for this to work, alternatively I would just plug out the drive and put it in my Synology…
You don’t need anything but ssh to the box. After you enable ssh and set the password, then you can do ssh firstname.lastname@example.org (that’s right for mine). Once you know that works, you can have rsync ssh to the server and start the rsync server there. Not quite as fast as setting up an rsync daemon, but it is more persistent, and less prone to error.
One thing you have to be careful about is that if you have setup a user “dan” (as I have), and then you rsync to email@example.com:/dan, that will be wrong. You have to do it to the shared directory where there is space.
I use the df -kh command to check this. But also look around. On my box, there is a directory /shares/dan which is a symbolic link into /mnt/HD/HD_a2/dan/ . So, I’m free to use either path, or any other path under /mnt/HD/HD_a2/.
If memory serves, the default ones used by its ssh daemon is crappy diffie-helman based, instead of elliptical curve, or even RSA.
While the MyCloud (gen2) uses a ram-based root file system, it copies the keys from a persistent configuration partition before the sshd starts, so replacing the key files there will persistently give quality encryption with user generated keys. (ALWAYS recommended to NOT use the baked in keys, because those keys live on many devices in the wild! Besides, they are weak sauce DSA keys anyway, which is probably why you are unable to handshake. OpenSSH will actively refuse them.)
These folks seem to feel that even without the ssh tunnel, the actual password will be MD5 hashed, not traveling in clear text.
Since rsync does not handle its own encryption and uses ssh for that, I stand by my suggestion that you generate new (actually strong) ssh keys, preferably in 4096bit RSA or ECDSA flavors, then put them on the MyCloud. I very strongly suspect that the openssh on the synology NAS is rejecting the handshake, because the mycloud is offering a DSA key that is getting refused, and there is no fallback.
If you do that, then the encryption will be much stronger, and the password will still be hashed before being transmitted.
thanks for the very good manual and explantation to activate the rsync on the wdmycloud.
I think i did all thinks in your manual but i have one problem:
I can’t see the folder “shares” in my windows explorer.
But, like I explain in that thread, the problem I have now is that as soon as I reboot the NAS, the rsync server config is gone. What should I do? Also, bear in mind that I don’t have the /etc/init.d/rsync present either and I’m using firmware 5.26.300 (OS 5 I guess).
My intention is to backup my Synology NAS using Hyperbackup on a WD My Cloud EX2 Ultra.