Like every other website on the planet, SmallNetBuilder uses cookies. Our cookies track login status, but we only allow admins to log in anyway, so those don't apply to you. Any other cookies you pick up during your visit come from advertisers, which we don't control.
If you continue to use the site, you agree to tolerate our use of cookies. Thank you!

Router Charts

Click for Router Charts

Router Ranker

Click for Router Ranker

NAS Charts

Click for NAS Charts

NAS Ranker

Click for NAS Ranker

More Tools

Click for More Tools

NAS How To

Testing the rsync

With the rsync target now set, you need to either kill and restart the inetd process to start rsync as a daemon, or just reboot the MBWE.

I used the Synology DS109+ to run the test, creating a job as shown in Figure 6. Note that instead on the MBWE's IP address, I used its host name. This is because of its nasty habit of grabbing a new IP address on each reboot when it is set as a DHCP client. If I were going to have the MBWEII on my LAN permanently, I would have assigned it a static IP or reserved an IP in my DHCP server.

Note that the backup module name is set to test, meaning this job is using the access-controlled test folder. If I wanted to use the Public folder, I just would set the Backup module to Public.

Synology to MBWE backup job

Figure 6: Synology to MBWE backup job

Once I had everything set up, a click on the Synology's Back up Now button on its Backup page, ran the rsync successfully.

One thing I did note was a succession of these messages in the MBWE's log:

07/13 16:52:03 MyBookWorld daemon.info rsyncd[9955]: connect from UNKNOWN (10.168.3.245)
07/13 16:52:03 MyBookWorld daemon.info rsyncd[9955]: name lookup failed for 10.168.3.245: Name or service not known
07/13 16:51:53 MyBookWorld daemon.info rsyncd[9954]: connect from UNKNOWN (10.168.3.245)
07/13 16:51:53 MyBookWorld daemon.info rsyncd[9954]: name lookup failed for 10.168.3.245: Name or service not known
07/13 16:51:47 MyBookWorld daemon.info rsyncd[9953]: connect from UNKNOWN (10.168.3.245)
07/13 16:51:47 MyBookWorld daemon.info rsyncd[9953]: name lookup failed for 10.168.3.245: Name or service not known
07/13 16:51:37 MyBookWorld daemon.info rsyncd[9932]: connect from UNKNOWN (10.168.3.245)
07/13 16:51:37 MyBookWorld daemon.info rsyncd[9932]: name lookup failed for 10.168.3.245: Name or service not known

I'm not sure what the problem is or why the rsync daemon is trying to do a reverse name lookup. But these messages don't seem to affect the rsync process.

Next time, I'll show you how to use Buffalo NASes as rsync targets.

More NAS

Wi-Fi System Tools
Check out our Wi-Fi System Charts, Ranker and Finder!

Support Us!

If you like what we do and want to thank us, just buy something on Amazon. We'll get a small commission on anything you buy. Thanks!

Over In The Forums

Hi allIt seems that devices on 5G-1 and 5G-2 cannot "see" each other.On Wireshark it seems some packets can't traverse from one 5G band to the other. ...
Hello, I'm looking for advice for the build in the subject line. I'm a landscape architect starting my own small office. It will be two people at firs...
So I have a newer RT-AC3100 I've been running as my main router the past few months. I also had two older RT-N66 running as APs also. Everything was f...
Is this ok to do ? Also allow only specified ip address.I want to do this my for cousins so i don't have to go over there every time.I notice the 86u ...
About 2 years ago the WAN port on my R7000 died. About a year and a half ago I managed to get Tomato 1.28.0000 -140 K26ARM USB AIO-64K installed, with...

Don't Miss These

  • 1
  • 2
  • 3