NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

cs_giuseppe's avatar
cs_giuseppe
Apprentice
May 23, 2017
Solved

RSYNC backup from nas OS6 to nas OS6 change file permission/owner

Hi,

 

I have 2 NAS with active directory security, there is a a rsync backup job from nas A to nas B. Nas B file persission/owner are set as default but after the rsync backup there are messed.

After that the webgui of the shares became slow in refreshing and in systemd-journal.log I found many errors like these:

readynasd[3105]: Failed 'wbinfo --gid-info 32802': failed to call wbcGetgrgid: WBC_ERR_DOMAIN_NOT_FOUND

readynasd[3105]: Could not get info for gid 32802

 

Any ideas how to avoid this?

 

Thanks

  • True, you can't transfer the snapshots with a backup job.
    But when the job starts on NAS A, a snapshot is automatically taken before transferring the data and released once complete. This is to ensure data consistency.
    That's what I think OP was referring to.

    The issue is because the destination NAS doesn't recognize the UID/GIDs used for file permissions.
    Since 6.5.0, there were changes in the algorithm responsible for the AD SIDs to UID/GIDs mapping. If both NAS are integrated to AD, using "rid" instead of "tdb" (check smb.conf), then the mapping will be calculated consistently on both sides. Otherwise it won't.

6 Replies

Replies have been turned off for this discussion
    • cs_giuseppe's avatar
      cs_giuseppe
      Apprentice

      Hi crazy_toy

       

      the option is not flaggable in the rsync job when is on the sender nas, if i made a rsync job on the destination nas the otion is flaggable.

      But in this case I lost the automated snapshot before the job and used for rsync

       

      Giuseppe

  • True, you can't transfer the snapshots with a backup job.
    But when the job starts on NAS A, a snapshot is automatically taken before transferring the data and released once complete. This is to ensure data consistency.
    That's what I think OP was referring to.

    The issue is because the destination NAS doesn't recognize the UID/GIDs used for file permissions.
    Since 6.5.0, there were changes in the algorithm responsible for the AD SIDs to UID/GIDs mapping. If both NAS are integrated to AD, using "rid" instead of "tdb" (check smb.conf), then the mapping will be calculated consistently on both sides. Otherwise it won't.
    • cs_giuseppe's avatar
      cs_giuseppe
      Apprentice

      Hi jak0lantash,

       

      yes, all true.

       

      NAS A and NAS B are in AD

      NAS A is old and FW latest and NAS B is new and FW latest

      smb.conf in NAS A has idmap config * : backend = tdb

      smb.conf in NAS B has idmap config * : backend = rid

       

      There is a method for change idmap to rid for NAS A? Even reconfiguring all samba access?

       

      Thanks

NETGEAR Academy

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

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More