That error usually occurs when the copy program try to apply securitu settings (file owner, ACLs ...) And the destination serveur (CIFS server on the VNXe cannot resolve the SID for the owner or one of the ACEs It can be that #1 SID is unknown because user was removed fronm AD or #2 that target cannot resolve SID  The params you're referring to in NS-land will I believe suppress that error when a SID cannot be resolved (first param) and (second param) store unknown SID as it is If that second param is not set then unknown SID in owner will be repladed by the user running the copy and dropped in ACEs  Those params do not exist on VNXe  Are you seeing unknown SIDs on the source for those files in either owner or ACEs (properties/security and advanced/owner) if that is the case then more likely the users were removed from AD If not make sure both systems are in same domain (or that they are not Standalone) or make sure you can manually apply ACLs with AD users on target w/out error  Claude
I am trying to do a data migration for a customer of CIFS shares from CIFS shares on NX4 to new VNXe using Robocopy.  ROBOCOPY \\ds_temp\tsprofile file://\\ds\tsprofile\\dsfile://\\ds\tsprofile\tsprofile  /COPYALL /B /SEC /MIR /R:0 /W:0 /LOG:MyLogfile.txt /NFL /NDL  For each and every file that is getting migrated, I am getting the message "Security ID Structure is Invalid."   As I researched this topic, this error message seems to be generated by the VNXe.  A little more research shows that, in NS-land, there were DART attributes that could be set to remedy these types of security/ACL settings and attributes.  However, we don't believe that these attibutes were modified from their defaults on the NX4.  So, it's almost as if the default CIFS security attributes on the NX are different than what the VNXe is expecting.  Can someone shed any light on this issue?  Thanks, Eric
Data Migration from NX to VNXe