NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
VelocityCS1
Nov 16, 2012Aspirant
Duo v2 NAS-NAS RSync frustration
Hi guys
I just bought 2 of these devices, with the intention to sync or mirror NAS1 to NAS2, or at least one or more Shares
I've tried so far a 2 step process:
1. RSync local share to local share - [Work] to [Backup]. Works fine
2. RSync Server remote sync. This is where the issue comes in...
I created a share on NAS2 [Mirror] and enabled RSync for it. For now, left anonymous
2.1. Tried an RSync pull from NAS2 (source: remote rsync server, host NAS1. destination: share, share: mirror). If I "test connection" with the Path left blank, I login successfully. Once I add a path (tried /backup and /c/backup) I get the "Cannot connect to share because of an incorrect network name or permission was denied. Code: 7077010012"
2.2 So, then tried an RSync push from NAS1 (source: share, share:backup. destination: remote, RSync Server, host NAS2). Again, if I "Test connection" I get exactly the same results as 2.1 above
The admin pass for both NAS boxes is the same
What am I doing wrong???
Eventually I would like to do Local [Work] to local [backup] ran 2 hourly, then NAS1/backup to NAS2/Work ran overnight each night, so effectively I have a mirrored failover
Thanks in advance
I just bought 2 of these devices, with the intention to sync or mirror NAS1 to NAS2, or at least one or more Shares
I've tried so far a 2 step process:
1. RSync local share to local share - [Work] to [Backup]. Works fine
2. RSync Server remote sync. This is where the issue comes in...
I created a share on NAS2 [Mirror] and enabled RSync for it. For now, left anonymous
2.1. Tried an RSync pull from NAS2 (source: remote rsync server, host NAS1. destination: share, share: mirror). If I "test connection" with the Path left blank, I login successfully. Once I add a path (tried /backup and /c/backup) I get the "Cannot connect to share because of an incorrect network name or permission was denied. Code: 7077010012"
2.2 So, then tried an RSync push from NAS1 (source: share, share:backup. destination: remote, RSync Server, host NAS2). Again, if I "Test connection" I get exactly the same results as 2.1 above
The admin pass for both NAS boxes is the same
What am I doing wrong???
Eventually I would like to do Local [Work] to local [backup] ran 2 hourly, then NAS1/backup to NAS2/Work ran overnight each night, so effectively I have a mirrored failover
Thanks in advance
1 Reply
Replies have been turned off for this discussion
- VelocityCS1AspirantWell after another couple of hours.... Solution!
I did a wee search of rsync's man page, and it appears the source needs to have a trailing (not leading) / to denote a folder. For a GUI-only user, definitely not intuitive. Why does the ReadyNAS not either mention this or add it invisibly?
However, I now have local [Work] to local [backup] on NAS1, and on NAS2 a Pull job, pulling from NAS1::backup/ to [Work]
Happy as Larry (eventually)
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!