Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 5 results
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Why_is_Ctime_not_updated_when_copying_a_file_from_a_Windows_client_to_a_CIFS_share
      Applies to ONTAP 9 CIFS Answer In a multiprotocol environment, it is normal behaviour that the change time won't be modified when a file gets copied from a Windows client to the NetApp CIFS share The ...Applies to ONTAP 9 CIFS Answer In a multiprotocol environment, it is normal behaviour that the change time won't be modified when a file gets copied from a Windows client to the NetApp CIFS share The change time update during file closure could cause Robocopy extremely inefficient incremental updates. Additional Information CONTAP-30616: Robocopy might copy ACLs even when they have not changed
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Is_there_any_risk_for_a_Windows_user_to_access_a_volume_with_Unix_security_style_through_name-mapping
      Applies to ONTAP 9 Multiprotocol This question involves the multiprotocol NAS access As long as the multiprotocol is correctly configured and used, there will be no risk How to verify the name-mapping...Applies to ONTAP 9 Multiprotocol This question involves the multiprotocol NAS access As long as the multiprotocol is correctly configured and used, there will be no risk How to verify the name-mapping is working as intended What are the important considerations when setting up CIFS and name-mapping in clustered Data ONTAP Troubleshooting Workflow: CIFS or SMB Access Denied TR-4887: Multiprotocol NAS in NetApp ONTAP Overview and Best Practice TR-4668: Name Services Best Practices Guide
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/What_are_the_effects_of_changing_the_security_style_from_NTFS_to_UNIX
      Previous NTFS permission will no longer apply after changing the security style from NTFS to UNIX. After changing from NTFS to UNIX security style, ONTAP will use the approximate UNIX permissions base...Previous NTFS permission will no longer apply after changing the security style from NTFS to UNIX. After changing from NTFS to UNIX security style, ONTAP will use the approximate UNIX permissions based on the original NTFS ACL. If we change back from UNIX to NTFS permissions, files and folders that existed before the first change, and where the unix permissions were not updated, should regain the original NTFS permissions.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_to_change_the_UNIX_permission_for_created_files_by_Windows_user
      Applies to ONTAP 9 Multiprotocol Description How to change the UNIX permission for those Windows user created files under the UNIX security style volume.
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Application_unable_to_write_working_files_to_qtree_after_qtree_permission_change
      Applies to A qtree with NTFS permissions that is also multi-protocol mounted to NFS clients and used for writing application working files had the permission style changed from UNIX to NTFS The hosts ...Applies to A qtree with NTFS permissions that is also multi-protocol mounted to NFS clients and used for writing application working files had the permission style changed from UNIX to NTFS The hosts that have the qtree mounted NFS using multi-protocol name mapping are no longer able to write working files to the qtree Issue The qtree permissions change broke the permissions for the application work flow Applications were no longer able to read and write the working files to the qtree