Orbi WiFi 7 RBE973
Reply

Partial RSYNC failure or ReadyNAS bug?

courtier1
Aspirant

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?
Message 1 of 15
StephenB
Guru

Re: Partial RSYNC failure or ReadyNAS bug?

Try deleting or renaming the backup share on the ReadyNAS, and create a new one.
Message 2 of 15
vandermerwe
Master

Re: Partial RSYNC failure or ReadyNAS bug?

You haven't mentioned anything about any advanced access rights settings on the readynas, are all these identical for all shares? I'm not sure if these affect rsync access, but perhaps you could confirm.
Message 3 of 15
courtier1
Aspirant

Re: Partial RSYNC failure or ReadyNAS bug?

@Vandermerwe

Are you referring to the other permissions like HTTPS/AFP/CIFS/FTP? Why would those affect RSYNC? But just for sanity's sake I did have that thought before posting this and I have verified that in all four cases read-write access is allowed on all four shares for all of the active sharing protocols. (Meaning I don't use CIFS so it is disabled across the board.) Or are you referring to some other access rights?
Message 4 of 15
courtier1
Aspirant

Re: Partial RSYNC failure or ReadyNAS bug?

StephenB wrote:
Try deleting or renaming the backup share on the ReadyNAS, and create a new one.



@StephenB

I just created a test share called TEST with wide open permissions for all protocols (CIFS, AFP, HTTP, FTP, and RSYNC). But still only the three previous shares show up on the QNAP as options. I think there is a bug with ReadyNAS related to RSYNC.
Message 5 of 15
vandermerwe
Master

Re: Partial RSYNC failure or ReadyNAS bug?

Under "advanced share permissions" are all the settings identical for all the shares?
Message 6 of 15
StephenB
Guru

Re: Partial RSYNC failure or ReadyNAS bug?

Did you enable NFS?

I'm not familiar with the QNAP, but I'm not sure what you mean by not "showing up the QNAP" because of an RSYNC bug. The QNAP shouldn't be seeing a list of shares that are enabled for RSYNC, as there is no way to advertise them.
Message 7 of 15
courtier1
Aspirant

Re: Partial RSYNC failure or ReadyNAS bug?

vandermerwe wrote:
Under "advanced share permissions" are all the settings identical for all the shares?



Yes, I confirmed that the Advanced Options are the same across the board.

Share folder owner: root
Share folder group: root

Share folder owner rights: greyed out
Share folder group rights: Read/write
Share folder everyone rights: Read/write

Grant rename and delete privileges to non-owner of files: checked

Shift share content timestamps by 0 minutes (default)

--------------

RSYNC jobs are all managed by user: b4ckUp (and yes, I've checked and rechecked and rechecked, etc. that the username and password are the same across the board)
Message 8 of 15
courtier1
Aspirant

Re: Partial RSYNC failure or ReadyNAS bug?

StephenB wrote:
Did you enable NFS?

I'm not familiar with the QNAP, but I'm not sure what you mean by not "showing up the QNAP" because of an RSYNC bug. The QNAP shouldn't be seeing a list of shares that are enabled for RSYNC, as there is no way to advertise them.


@StephenB

Please see:

This shows the 3 working RSYNC jobs (from QNAP to ReadyNAS)

Please see:

This shows me trying to create the 4th job and source/destination pair. Notice that only 3 possible destinations show up when in fact there are 5 shares on the ReadyNAS configured for RSYNC (the 3 shown, "backup", and one newly created "TEST").
Message 9 of 15
courtier1
Aspirant

Re: Partial RSYNC failure or ReadyNAS bug?

Any comments or suggestions from the NetGear team?
Message 10 of 15
JohnnyB11
Aspirant

Re: Partial RSYNC failure or ReadyNAS bug?

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
Message 11 of 15
StephenB
Guru

Re: Partial RSYNC failure or ReadyNAS bug?

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.
Message 12 of 15
courtier1
Aspirant

Re: Partial RSYNC failure or ReadyNAS bug?

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.
Message 13 of 15
courtier1
Aspirant

Re: Partial RSYNC failure or ReadyNAS bug?

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.
Message 14 of 15
JohnnyB11
Aspirant

Re: Partial RSYNC failure or ReadyNAS bug?

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).
Message 15 of 15
Top Contributors
Discussion stats
  • 14 replies
  • 4958 views
  • 0 kudos
  • 4 in conversation
Announcements