Mugatu If I had to venture a guess, I would say that you've done a few things wrong there to get this behavior. #1. When creating SMB shares, either do so from the CLI or when doing so from the WebUI Change the radio button from "Apply the Windows Default ACLs" to "Do Not Change existing permissions" #2.  ACLs always inherit, unless you on-purpose break inheritance that's their behavior, but the question is how you created the target parent directory.  The recommended method when doing a data migration is always create the directories using the CLI meaning they will have POSIX permissions by default, therefore there won't be any ACLs to worry about inheriting. #3.  When doing an SMB migration to Isilon, on the source side you need local administrator and backup operator rights for the account doing the copy, on Isilon, use a special administrative share at the root of the access zone, that is administratively hidden, and give run-as-root permissions, only to the service account doing the copy.  So if the data was stored at: /ifs/clustername/accesszonename/finance, I would create a share at /ifs/clustername/accesszonename as accesszonename$ and give the account you are using to do the copy say domain\username --run-as-root rights.  Be really careful with this, but it'll give you what you likely need to get the data there intact. #4.  Something most people overlook until it bites them; Isilon does not support Historical SIDs, so if your source data has HSID values in the ACE entries for users or groups, you need to translate those during the migration or risk losing access.  See KB88513 on support.emc.com.  Use emcopy with /sidmapfile to remediate this. #5.  Evaluate if the source uses local users and groups in filesystem permissions.  Like above we would always recommend using /sidmapfile with LOCALGROUPSID:NEWDOMAINGROUPSID to get rid of those old permissions when you migrate, and move to AD only permissions.  This is critical long-term because if you were to simply move the groups to Isilon you would find that if you wanted to cutover to a DR site, those local groups wouldn't be there.  This same issue comes up in NAS migrations from/to pretty much any NAS platform without the use of VDM/VFilers. #6. Use emcopy, not robocopy.  Emcopy is significantly faster than robocopy, especially if you have a large count of small files, or wide and shallow directory trees.  In one example of 3 million 8KB files spread across 6 directories (in a tightly controlled lab), an incremental with Robocopy took 54 hours (server 2012 R2 version, default number of threads).  Emcopy with the default number of threads did the same job in less than 90 minutes.  Beyond that there are commercial tools from EMC Select partners that certainly can help make the whole process easier, especially if it's a big migration. Have a look at DataDynamics StorageX or Datadobi's DobiMiner N2N products.  They can make your life much easier. Hope this helps,  ~Chris Klosterman Advisory Solution Architect EMC Isilon Offer & Enablement Team chris.klosterman[NAME].com twitter: [NAME]
We are importing all our windows file server shares to our Isilon cluster.  however as the files are being copied over the original windows ACL's are being changed.  Ideally we would like all files and folders from the windows shares to be come over with their original permissions / ACL's untouched.  I have tried using  no_prop_inherit parameter as well as  Control flag options: dacl_protected and sacl_protected on the directory we are copying the files into but nothing seems to keep the files and directories from having their permissions modified when copied to the Isilon.  any insight would be appreciated!
How to stop ACL permissions inheritance?