NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MugiMuc
Feb 05, 2018Aspirant
ReadyDR - Operation not permitted
Hi, I just did the transition from "ReadyNAS Replicate" to "ReadyDR". I'm using two RN312 NAS'. One is the main NAS server and the second is the BACKUP NAS. The first problem I encountered was,...
MugiMuc
Feb 13, 2018Aspirant
We still have the problem with our ReadyDR job!
We URGENTLY need help, but didn't receive any feedback from NETGEAR yet.
We're sure it is in NETGEARS interest to help customers in need!
Please help us!
StephenB
Feb 13, 2018Guru - Experienced User
What firmware are you running?
You might need (paid) support via my.netgear.com for this, and not the community support that is offered here. If you purchased your RN312 between 1 June 2014 and 31 May 2016 then you have lifetime free chat support.
Another (brute force) approach is to rebuild the source NAS (factory default) and then restore the NAS from backup.
(Note I don't work for Netgear),
- MugiMucFeb 13, 2018Aspirant
Thank you for your reply.
We run firmware 6.9.2. (the most up-to-date one)
"Unfortunately" we bought the two NAS we are using in January 2014, so no support....
To be quite honest we do not want to buy a "SUPPORT" from Netgear. It should be a matter of course , that if there is a question or problem, that Netgear tries to help directly. OK, perhaps not via telephone or chat, but I just saw that even email support is not available... so without money no direct support from Netgear :-(
The last days we saw that our NASs have the names "NAS_Backup" and NAS_Server". We chose these names 4 years ago and the systems accepted the names without any problem. Now, I saw that the "_" character could be a problem. The questions is: Is it really likly that the "_" causes this problem. We really only want to change the NAS names if it is probably the solution. We use the NAS names at several locations in our company and would have to change all of them. After we change the name, we can not change it back.
Thank you for your help.
- StephenBFeb 13, 2018Guru - Experienced User
wrote:To be quite honest we do not want to buy a "SUPPORT" from Netgear.
They do charge for support after 90 days, and that was their policy when you purchased back in 2014. Of course, one way or another the customers always pay for support - either they purchase it separately, or the support costs are bundled into their original purchase price. Similarly, the warranty costs are always bundled into the purchase price. Otherwise, the vendor quickly goes out of business. As noted above, I don't work for Netgear.
Just guessing here, but I doubt your problem could be resolved by their Tier-1 support, I'm thinking it would need escalation to a Tier-2 or Tier-3. It's not something I've seen posted here before.
wrote:
Now, I saw that the "_" character could be a problem. The questions is: Is it really likly that the "_" causes this problem. We really only want to change the NAS names if it is probably the solution.
It seems unlikely that the "_" causes your problem, since only some snapshots generate the error. You can test it by setting up a test ReadyDR backup job that uses the NAS IP addresses instead of their hostnames. But if the solution (or some future issue) requires a factory default, then you will be forced to change the hostnames, since you can no longer enter a name that includes the "_" character.
My guess is that your issue is related to a BTRFS issue with the specific snapshots (or perhaps shares) that generate the "Operation Not Permitted".
- MugiMucMar 20, 2018Aspirant
The last three weeks we made extensive tests to find the reason for the problem "Permission Denied" that we described.
There is one thing that really puzzles us:
To localize the problem, we created a new share (directory ) on our RS312 server , we put some data in it (some data from our main share) and created a ReadyDR job for a automatic daily backup. The result was that everything worked fine and we received the message: "ReadyDR Job xyz completed successfully." Sounds great!
After that we copied ALL data from our main share (40GB) to the new share and tested the backup. Still everything worked fine.
At this point, our main share and our test share data was identical. The automatic ReadyDR backup of our test share worked great, but the backup of our main share failed every single night. ("Permission denied").
So we desided to rename our main share to "xyzOLD" and renamed our test share to the same name as our original share (the main share name is really simple, 11 characters, no special symbols, only lower case letters and one leading upper case letter).
From this point on everything went south. We again got the message "Permission denied" and the backup failed.
What could be the reason for that?? The physical data and core of the "new" share must be okay because it was freshly been created.
Hope anyone can help us.
Thank you.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!