NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
dschwartzer
Jul 22, 2017Luminary
ReadyDR job failure: Input/output error
I use a RN526X as my primary NAS and use a RN314 for backup and for the ReadyDR jobs. I have has ongoing issues where the 314 becomes Read Only after about two weeks of backups. I did a factory res...
dschwartzer
Jul 25, 2017Luminary
Thanks for your note.
The Read Only problem, like the current input/output error only affects the ReadyDR jobs. The backup job has always, and continues to run without issue.
The backup job is set up on the Backup tab of the 526 and backs up the entire 526 data share to a share on the 314 called Backup. Within the backup folder is a folder called Data (written by the backup job), and within Data are all of the Shares and files on the 526. That backup runs each night at 10:00 pm and continues to run properly.
The ReadyDR jobs are set up on the 526 as "push" jobs to the 314. Therre is a dedicated ReadyDR job for each share on the 526 and that corresponds to a dedicated DR share on the 314. The DR shares were created as part of setting up the ReadyDR process.
Previously, they would run for a week or two and then the shares on the 314 would become "Ready Only" and the push jobs would fail.
While the 314 has not yet become read only, the Ready DR jobs are continuing to fail each night and I get the input/output error.
The only thing different now from precious times is that previously, I was letting the 314 power itself down after the Ready DR job ran (they run just after midnight), at about 1:00 am. Since doing a Factory Restore a couple of weeks ago, I did not power down the 314 until after I started getting a No Route to Host mesage for all of the backup and RaedyDR jobs. At that point I rebooted the 314 and the backup job started working again but the ReadyDR jobs fail.
I did check the IP addresses for both units and they are correct I have also rebooted the 526 but that did not correct the issue.
Hope that helps. Let me know if you need anything else.
Regards,
David
Marty_M
Jul 26, 2017NETGEAR Employee Retired
Hello dschwartzer,
There are concerns raised exactly similar to this problem we are encountering and the fix will be provided on the beta firmware or on the official release of firmware 6.8.0, you may want to try to beta firmware and you may download it from here.
Regards,
Marty_M
NETGEAR Community Team
Related Content
NETGEAR Academy

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