Re: RSync - am i missing something obvious? (RN312/RN102 with 6.10.4)

SLK-Purdue · ‎2020-12-22

I feel like I am missing something obvious but I don't see it. I have used Rsync on Unix and I think I know the concepts. 🙂

Source is RN312 running 6.10.4. Target is RN102 also running 6.10.5. Rsync is enabled on target and target directory has Rsync permission to default Read/Write. Backup job on the source is set up and connection confirmed. Job start on source and completes very quickly. The full directory structure is created on the target destination but no files are copied. What am I missing and it is OK to tell me it is obvious. 🙂

Log says

Backup Job Name: ArchiveForAWS
Backup Job Type: Full
Protocol: rsync
Backup Source: [volume:data]/
Backup Destination: [remote:rsync]/192.168.1.201::ArchiveForAWS
Backup Start Time: Tue Dec 22 2020 14:14:30
Backup Finish Time: Tue Dec 22 2020 14:14:30
Backup Status: Success

sending incremental file list
data/
data/.Trash-1000/
data/.Trash-1000/files/
data/.Trash-1000/info/
data/._share/
data/.apps/
data/.purge/
data/.timemachine/
data/.vault/
data/AmazonCloudDrive/
data/Bench2PC/

...... other directories listed

data/home/
sent 1,277 bytes received 164 bytes 2,882.00 bytes/sec
total size is 0 speedup is 0.00

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

rn_enthusiast · ‎2020-12-22

Seems similar to this post

Maybe we have a trend on the 6.10.4 firmware @Marc_V and @JohnCM_S ?

SLK-Purdue · ‎2020-12-22

A bit more information - if I set up the backup Rsync from a specific source folder to a specific destination folder, that works OK. It would seem a clue might be that both reports are trying to backup from /data.

Scott

@rn_enthusiast wrote:
Seems similar to this post

Maybe we have a trend on the 6.10.4 firmware @Marc_V and @JohnCM_S ?

SLK-Purdue · ‎2020-12-22

On second thought, is this a recursion problem? If the "r" option is missing or not working, this could explain what I am seeing. I will test this theory when I can but wanted to put it out for others to consider.

@SLK-Purdue wrote:
A bit more information - if I set up the backup Rsync from a specific source folder to a specific destination folder, that works OK. It would seem a clue might be that both reports are trying to backup from /data.

Scott

@rn_enthusiast wrote:
Seems similar to this post

Maybe we have a trend on the 6.10.4 firmware @Marc_V and @JohnCM_S ?

StephenB · ‎2020-12-23

@SLK-Purdue wrote:

On second thought, is this a recursion problem? If the "r" option is missing or not working, this could explain what I am seeing. I will test this theory when I can but wanted to put it out for others to consider.

Recursion is working on my systems - backing up individual shares using "pull" backups (meaning that the source is remote).

Marc_V · ‎2020-12-23

HI All,

Happy Holidays! We would like to request for the full logs of your NAS if possible, kindly send it via PM.

Many thanks!

SLK-Purdue · ‎2020-12-23

Link sent to source and destination logs on Dropbox. These logs include the test of sending just one folder that worked. Look for the Rsync of /data.

Thanks for the help and Happy Holidays!!

Scott

@Marc_V wrote:
HI All,

Happy Holidays! We would like to request for the full logs of your NAS if possible, kindly send it via PM.

Many thanks!

SLK-Purdue · ‎2020-12-24

Update - after more testing, it is NOT related to recursion (rysnc "r" parameter). Doing Rsync for a folder with folders inside folders works fine and creates both the directory structure and content. That point the problem back to an Rsync for the volume /data on 6.10.4. I don;t have an easy way right not to go back to 6.10.3 or earlier for testing.

Scott

@SLK-Purdue wrote:
Link sent to source and destination logs on Dropbox. These logs include the test of sending just one folder that worked. Look for the Rsync of /data.

Thanks for the help and Happy Holidays!!

Scott

@Marc_V wrote:
HI All,

Happy Holidays! We would like to request for the full logs of your NAS if possible, kindly send it via PM.

Many thanks!

rn_enthusiast · ‎2020-12-24

Thanks for testing @SLK-Purdue

I have an rsync job that backs up my volume (/data) to another NAS and that works perfectly fine on 6.10.3. I will stay on that firmware for now until Netgear has tested and reverted back to us.

Cheers

SLK-Purdue · ‎2021-01-01

Did the logs should anything interesting?

Scott

SpaceTintin · ‎2021-01-03

I am having the exact same symptom on a deployment with a 3312 backing up to a 314. When running on 6.10.3 the Rsync via SSH functions correctly to backup the entire volume (/data), but if I upgrade to 6.10.4 the back-up says it runs successfully in a few seconds (should take it a few hours nightly) and dones't update any of the files, but will only update folder structure changes. For now I reverted back to 6.10.3 for now and rsync works again. Hoping for a fix on this. Different problem, but still not fixed, the backup setup still messes up the destination file address with an extra "\" when using the gui and I have to edit it out of the backup scripts via ssh before the rsync via SSH even works to begin with.

StephenB · ‎2021-01-03

You could also temporarily run the rsync backup job(s) on the RN314 (which will work with 6.10.4).

DanDevoe · ‎2021-01-08

Hi,

For what its worth, I am experiencing the exact same issues on the 6.10.4 firmware.

I am rebuilding one of my NAS units & I am unable to send the volume data to another NAS, both running 6.10.4 - the directory structures are created & update accordingly, if I create a new folder on the source. But no data is copied.

I have 2 NAS units running 6.10.3 & 2 running 6.10.4 (the latter 2 include a brand new unit & one being rebuilt with new drives). The 6.10.3 appear to back up the volume data fine to 6.10.4. But I cannot backup from 6.10.4 to 6.10.4.

The same behavior is exhibited when backing up a share instead of the volume.

If I setup an rsync job on the destination NAS to pull data from a 6.10.4 (which doesn't allow the volume - just the shares), that works - so the issue appears to be when running the rsync job from the source NAS.

I'll provide logs if needed.

Thank you

-Dan

SLK-Purdue · ‎2021-02-17

Any word on a new firmware version or should I give up and downgrade to 6.10.3?

r32nj · ‎2021-05-14

Is FW version 6.10.5 supposed to correct the RSYNC backup issues that 6.10.4 has? I don't see it mentioned in the release notes so I am hoping someone has tried this already and can confirm.

DanDevoe · ‎2021-05-14

From what I've read, the RSYNC issue is NOT corrected in 6.10.5.

Shame on them...

r32nj · ‎2021-05-14

Thanks for the quick reply. Is there a specific thread that is good to follow for this issue?

DanDevoe · ‎2021-05-14

This is where I read that it wasn't fixed - I did not try it myself.

https://community.netgear.com/t5/ReadyNAS-Beta/OS-6-10-5-Beta/m-p/2087755

r32nj · ‎2021-05-14

That stinks. This issue has been around ever since 6.10.4 was released. Plenty of time to fix it in my opinion.

SLK-Purdue · ‎2021-05-14

Amen to tthat but, sadly, support doesn't seem to be a priority.

bedlam1 · ‎2021-05-14

@JohnCM_S, @Marc_V

Can you advise when this bug, caused by the release of 6.10.4 by Netgear, will be resolved

givememynamebak · ‎2021-05-22

I agree, absolute BS Netgear!