After climbing up the learning curve, I am pleased to to report good progress with the 4TB WD MyCloud as automated NAS backup for Windows and Linux PCs and servers on my home network (see Setup of Linux/Windows shares on 4TB mycloud as NAS device on LAN). To date, the following backup scenarios are working well with one notable exception:
Windows 7 desktop: Image archive to NAS using Acronis ATH 2010; file backup with mapped NAS share.
Windows Server 2008 R2: Image archive to NAS using Windows Server Backup; file backup sync using FreeFileSync.
Centos 7 linux server: Image archive to NAS using USB-based Clonezilla; file backup to NAS using rsync not working.
In my attempts to get rsync working from the Centos 7 server, I enabled SSH on the MyCloud and in the process noticed some peculiarities which I suspect are by design. The BusyBox embedded Linux shell appears to reset its base configuration (as set by the html admin portal) upon reboot (as discussed in After a reboot everything is reset - is this documented? how to people work around it?). From a design perspective, this behavior is understandable as it provides protection for the embedded operating system, but contradicts the instructions for configuring a persistent rsync daemon in http://www.diogosoares.ca/blog/2015/08/30/how-to-enable-rsync-in-a-wd-mycloud/.
So to get a persistent one-way rsync WDmycloud receiver working on my LAN, my question is “Do I need to configure a persistent rsyncd on the MyCloud device?” Since my rsync usage is one-way into the MyCloud, and SSH is enabled on the MyCloud, can the MyCloud rsync respond to RPC invocation via SSH or does rsyncd need to be persistently configured and running?
Any help or references to rsync and persistent SSH credential registration on the MyCloud would be appreciated. Thanks.