NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
debumitra
Nov 23, 2017Tutor
ReadyDR job from RN314 to RN424 starts, copies some snapshots, then fails
Hello, This is my first attempt to set up a ReadyDR jobs between two ReadyNAS NAS's that I have. The source is an old RN314 and the destination is a brand new RN424. I chose a very small share "Musi...
- Nov 28, 2017
Hi debumitra!
We appreciate your feedback and for letting us know that your issue has been resolved. Others might benefit from having this workaround that you shared in case someone experienced the same problem. Kindly mark this thread resolved by clicking the “Accept as Solution” button.
Regards
Retired_Member
Nov 26, 2017PM sent
debumitra
Nov 27, 2017Tutor
After posting the message. I did a lot of research myself to be able to fix the issue as I was eager to solve the problem and set up the back up jobs without delay. Initially I thought that it was some kind of a permission issue as the source (RN314) and the destination (RN424) RN's didn't have the same users/uid's. So I deleted and recreated the users on the destination RN (this is the brand new one with no data) to match the source RN. But this did not solve the problem.
On some of my shares, I had snapshots all the way from 2013. These are the ones that were failing. The ReadyDR job will start and copy snapshots starting the most recent one backward (i.e, present to past). The snapshots up to Jan/2015 will be copied ok but the Dec/2014 one will fail. This made me think that there was some change in ReadyNas OS starting January 2015 that made pre-Jan/2015 snapshots incompatible with ReadyDR framework. This is just a hypothesis.
So I deleted all snapshots starting Dec/2014 backward in one share and lo and behold, the ReadyDR job went through.
Success!
So now I have removed all pre-Jan/2015 snapshots from all my shares and all the ReadyDR jobs are working.
I have no way of reproducing the problem any more. I don't know what the root cause of the problem was.
Thanks.
- Marc_VNov 28, 2017NETGEAR Employee Retired
Hi debumitra!
We appreciate your feedback and for letting us know that your issue has been resolved. Others might benefit from having this workaround that you shared in case someone experienced the same problem. Kindly mark this thread resolved by clicking the “Accept as Solution” button.
Regards
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!