Is it normal that local adminitrator shows as SID on snapmirror destination volume ?
Applies to
- ONTAP 9
- Snapmirror
Answer
- It is expected behavior.
- All information of the Snapmirror destination volumes are synchronized through snapmirror transer, including the ACL information in the file, which should be consistent with that on the source volume.
- If using XDP snapmirror relationship, not SVMDR, that is, the configurations in the source SVM root volume cannot be synchronized to the destination cluster.
- CIFS local user
- CIFS loca group
- The SID of the administrator user in destination SVM is different from that of the user in source SVM, so it is displayed as: source adiministrator's SID or win-name.
Example:
Demo_DES::*> vserver services access-check authentication translate -node Demo_Des-01 -vserver naafstest -win-name NAAFSTEST\Administrator
S-1-5-21-1859220071-2216865930-2624919371
Demo_SRC::*> vserver services access-check authentication translate -node Demo_SRC-01 -vserver naana006 -win-name NAANA006\Administrator
S-1-5-21-1738220992-1147683932-2156450179-500
Additional Information
- NTFS ACLs are tied to SIDs, not windows users name or groups name.
- Even if a local user or group with the same name is configured, it will not be accessible if the SID is different.