I have installed NAS4free with one ZFS filesystem and share it out via CIFS/SMB.
I am new to NAS4free.
How if I migrate files using Robocopy (/COPYALL) from our current windows 2003 server to the shared CIFS/SMB, I am getting the following error
ERROR 1307 (0x0000051B) Copying NTFS Security to Destination Directory
This security ID may not be assigned as the owner of this object.
How do I migrate/copy the windows files with it's permission retain to the shared CIFS/SMB?
Thanks.
This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
Robocopy from windows to CIFS/SMB error
-
stevenfoo
- NewUser

- Posts: 3
- Joined: 09 Apr 2013 10:41
- Status: Offline
-
PaganGod
- Status: Offline
Re: Robocopy from windows to CIFS/SMB error
I have this same problem. I'd love to know what the trick is.
-
KimmoJ
- Starter

- Posts: 42
- Joined: 02 Feb 2016 15:02
- Status: Offline
Re: Robocopy from windows to CIFS/SMB error
This has to do specifically with the O privilege or owner. Setting the owner to something other than the copying user is a specific privilege of some kind. /COPYALL = /COPY:DATSOU - where OU is "Owner" and "Audit", respectively. S is NTFS security or ACL's.
I'm having this issue now, I can copy everything just fine with /COPY:DATS but that doesn't move the owner information across, and for some copies you absolutely need both O and U (though the audit one is unnecessary and not handled by Samba last I heard - but you do need DATSO if you need to keep track of ownership). So now I need to figure out why not even the domain administrator account has the right to set owner on files on the Nas4Free. Administrator should have that right.
I'm having this issue now, I can copy everything just fine with /COPY:DATS but that doesn't move the owner information across, and for some copies you absolutely need both O and U (though the audit one is unnecessary and not handled by Samba last I heard - but you do need DATSO if you need to keep track of ownership). So now I need to figure out why not even the domain administrator account has the right to set owner on files on the Nas4Free. Administrator should have that right.
-
KimmoJ
- Starter

- Posts: 42
- Joined: 02 Feb 2016 15:02
- Status: Offline
Re: Robocopy from windows to CIFS/SMB error
I got this sorted by doing a number of things, not all of them necessarily connected to the problem... had to resort to some trial and error. Essentially, you need to turn on all the switches for permissions and ACL's and the like in the CIFS shares, as well as make sure that Administrator owns the share. I also enabled kerberos delegation rights in the AD object for the NAS itself, not sure if that was a required step or not, but now I'm Robocopying away with the O switch intact and can proceed with my own deployment.
-
sherman
- Starter

- Posts: 41
- Joined: 27 Dec 2014 15:16
- Status: Offline
Re: Robocopy from windows to CIFS/SMB error
Hello
can someone please check this or confirm that setting all ACL and ntfs suppport settings in ZFS Dataset and CIFS share work with COP DATSO?
I can not at the moment but am highly interested in using this.
can someone please check this or confirm that setting all ACL and ntfs suppport settings in ZFS Dataset and CIFS share work with COP DATSO?
I can not at the moment but am highly interested in using this.