NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

courtier1's avatar
courtier1
Aspirant
Jul 24, 2013

Partial RSYNC failure or ReadyNAS bug?

I have a QNAP TurboNAS which I back up to a Netgear ReadyNAS NV+. There are four shares that I want to replicate via rsync. Both sets of folders exist on both devices. Rsync is successfully working on a daily schedule for three of the pairs (multimedia, download, film_vault) but refuses to work for the fourth pair (backup). I mention all of this to establish the following:

1. I have three successful RSYNC jobs setup and working. So I'm fairly confident I'm doing this right.
2. I'm using the same user and password on all four jobs.
3. I realize I'm involving a third party (QNAP) device, but based on my testing, I think the issue lies with the Netgear device.
4. I have upgraded both devices to their latest respective firmware.
5. I have disabled and then re-enabled RSYNC on both devices. I have rebooted both devices. I have reset the configurations for RSYNC on both devices. Nothing has worked.
6. In the setup screen of the QNAP despite everything I try, I am unable to see the "backup" share on the Netgear. The other three all show up as destination targets, but "backup" never appears. I have tried disabling one of the other three on the hunch that the QNAP had a bug in which it could only display three destinations. When I do that, the share on the Netgear that I disable RSYNC on disappears from the QNAP leaving only 2 possible targets. So my belief is that there is somehow a bug on the Netgear related to the share name "backup" or that somehow prevents it from advertising more than three shares via RSYNC.

Thoughts or suggestions?

14 Replies

Replies have been turned off for this discussion
  • StephenB's avatar
    StephenB
    Guru - Experienced User
    JohnnyB wrote:
    StephenB wrote:
    The QNAP shouldn't be seeing a list of shares that are enabled for RSYNC, as there is no way to advertise them.


    If you know the server, rsync will show you all (listable) modules:
    # rsync nas.local::
    backup "Backup Share"
    media "Media Server Share
    Might be worth trying on the qnap (using the ReadyNAS IP address).

    Note that the :: at the end of the command line is needed.
  • StephenB wrote:
    JohnnyB wrote:
    StephenB wrote:
    The QNAP shouldn't be seeing a list of shares that are enabled for RSYNC, as there is no way to advertise them.


    If you know the server, rsync will show you all (listable) modules:
    # rsync nas.local::
    backup "Backup Share"
    media "Media Server Share
    Might be worth trying on the qnap (using the ReadyNAS IP address).

    Note that the :: at the end of the command line is needed.



    @JohnnyB:
    Well, thanks for disproving my theory. :wink: Here are the results:

    From the ReadyNAS (IP = 192.168.200.5)
    dls-00-rd1:~# rsync 192.168.200.5::
    TEST "TEST"
    backup "Backup Share"
    downloads "all downloaded applications, utilities, and extensions"
    film_vault "all film files and applications"
    media "Media Server Share"
    dls-00-rd1:~#


    And the results from the QNAP
    [~] # rsync 192.168.200.5::
    TEST "TEST"
    backup "Backup Share"
    downloads "all downloaded applications, utilities, and extensions"
    film_vault "all film files and applications"
    media "Media Server Share"
    [~] #


    So based on this test it seems the ReadyNAS is in fact configured correctly for the RSYNC share "film_vault" and in fact the fault lies with the QNAP for not displaying it in the GUI (when it is clearly visible from the command line). So now I'm off to QNAP support. Thank you to everyone for their assistance in pinpointing where the error is -- not always easy when multiple products/companies are involved.
  • Timing. Is. Everything.

    I was about to open a thread on the QNAP forum for this issue. I had gathered my documentation and test results from this thread. Then I saw that there was a major firmware update (3.8.2 -> 4.0.2). I knew if I posted something about an older rev I'd be told to upgrade. So I researched the new code and seemed it "safe enough." I did the upgrade then went to configure the fourth (and missing) RSYNC pairing and... Voila. Worked perfectly. So QNAP bug -- now fixed in the new code -- all along. Thanks again to everyone who helped.
  • courtier wrote:
    Worked perfectly. So QNAP bug -- now fixed in the new code -- all along. Thanks again to everyone who helped.

    I'm glad I could help (indirectly).

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More