We've set up a DR Rsync job to copy data on NAS1 to NAS2. We'd like to have the job running weekly but when the job runs, it copies the data but creates a completely bizzare (and very incorrect) set of NTFS permissions on the NAS2 side. The set of permissions is the same whatever we set as the source; from an entire share to a single folder. The permissions set does not match what is set on NAS1 (source) or the NTFS permissions set on the source(s).
It seems to be a problem with the Rsync job itself or the ReadyNAS OS (6.10.2). Windows copy completes as expected and I've tried using SyncBack to run the job and this also copies correctly.
Has anyone else come across such a bizzare problem or have any insight?
What are the permissions I'm seeing when I browse to the shared folder (or any of the sub-folders) in Windows Explorer and view Properties > Security > Advanced? These don't match anything I can see when I connect to the NAS via the web console and look at the permissions set there in Network Access or File Access.
I cannot seem to connect to the NAS using SSH. When I enter the credentials in Putty, the window simply vanishes. SSH is deinately enabled on the NAS though...
I'm trying the command below to browse to the directory I want to check permissions on but when I enter the path, I get an error saying "No such file or directory exists".
cd /<share name>/
The directory does very much exist. I can browse to it and open files. For some reason, the command line will not see it.
I've attached a screenshot of what I can see in Windows Explorer. The highlighted yellow items should not be there and the two red boxes are duplicates.
drwxrwx---+ 1 administrator domain admins 172 Oct 30 07:56 <directory>
Sub-folders are the same.
Is the system using Active Directory?
If you look on the "options" tab of the backup job, is the option to change ownership of files in the backup destination set?
When you look at the file access tab in the share settings are you seeing "administrator" as the folder owner, and "domain admins" as the folder group? What are you seeing on the file access tab for the source share?
You should also check if the UID for administrator and GID for "domain admins" on the destination NAS matches the UID/GID for the folder owner and folder group on the source.
All File Access settings were identical on Friday. This morning however, I've found a user account and two groups not there previously in the File Access list. No-one has put them there and they were 100% not there on Friday.
Also, when looking in Windows Explorer at the share, the Inheritance is enabled. I had disabled this on Friday too.
Something else I have noticed: On the source NAS in File Access > Default Access, we have the "Specify permission when new file/folder is created" ticked. On the destination NAS, if I tick this and click apply, it unticks itself.
Yes, something is happening which clearly should not be.
How would I check the OS partition?
On ARM-based NAS you can use
# cd //
# df . -h
# df . -i
On x86 NAS (OS 6) you also need
# btrfs fi show /
# btrfs fi df /
because the OS partition uses BTRFS.
The "used" space in the btrfs indicates allocated space (some of which is actually free). It can be hard to interpret, so perhaps post what you see here.
Another option is to just do a factory reset, and start clean. You'd have to rebuild the NAS and you'd lose the data on it.
Ok. That makes it unlikely that the configuration settings just aren't taking.
One option is to use paid support (my.netgear.com).
I'm not thinking of any good avenues to explore, but if you have enough disk space you could try creating a new share, and moving the files into it. Then delete the old share, and rename the new to match it.
