NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
rgm60527
Jan 04, 2014Aspirant
Permission pro 312
I continue to struggle with my goal of migrating to a new pro 312 from my ultra plus. I created a share on my volume and then rysnc'd a share from my ultra plus. Then to test I swap host names for t...
StephenB
Jan 05, 2014Guru - Experienced User
rsync isn't making up the uid/gid - it is attempting to preserve the owner/group of the source files (e.g., on the ultra). In the case of backup 3, it is using the uid/gid for nobody/nogroup on the ultra - which is likely what the source share is set to.
Resetting permission/ownership from the web ui should ripple through, but the problem will recur every time you run the backup. If this is a pure backup, the one option is to ignore it. If you don't care about ownership on the source, you could also change the file ownerships on the ultra to admin/admin which will map.
You might also try using the backup option to reset ownership. Though that also had an issue when I tried it (pre-RN102 launch) - the backup job picked up the current ownership of the share (when the backup was already completed and the damage done). Hopefully that has been fixed.
Resetting permission/ownership from the web ui should ripple through, but the problem will recur every time you run the backup. If this is a pure backup, the one option is to ignore it. If you don't care about ownership on the source, you could also change the file ownerships on the ultra to admin/admin which will map.
You might also try using the backup option to reset ownership. Though that also had an issue when I tried it (pre-RN102 launch) - the backup job picked up the current ownership of the share (when the backup was already completed and the damage done). Hopefully that has been fixed.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!