Hi
We’re migrating some data from Windows file servers to CIFS shares on a 9.1p13 cluster (NTFS security style on the vols). We’re getting errors on some files and folders using Robocopy and the common thread seems to be objects with orphaned SIDs for the owner or DACL entries. We’ve tried other tools with the same results. Robocopy to another Windows file share works fine.
Has anyone else seen this behaviour? We’re assuming that the CIFS server is stopping the copy because it can’t resolve the SID. Is there any way to control that behaviour and just wrtie the DACL with the unresolved SID?
Thanks Steve
Is the sid actually unresolvable?
On Wed, Sep 12, 2018 at 9:33 AM Stephen Stocke scstocke@gmail.com wrote:
Yes, these are SIDs from deleted users. Usually when some folder has been setup so that Creator/Owner is assigned rights. When the user that created the file/folder leaves, and their account is deleted, the ACE with the unresolved SID remains. It seems that when Robocopy tries to copy the DACL for the file/folder, the filer doesn’t accept it because the SID cannot be resolved. (Speculation based on what we are observing.)
We’re running a separate project to clean these orphaned SIDs up but would like to get the data migrated in the interim ‘as-is’ if possible.
Get Outlook for iOShttps://aka.ms/o0ukef
________________________________ From: Basil basilberntsen@gmail.com Sent: Wednesday, September 12, 2018 5:11 pm To: Stephen Stocke Cc: toasters@teaparty.net Subject: Re: Copying NTFS Data with Orphaned SIDs
Is the sid actually unresolvable?
On Wed, Sep 12, 2018 at 9:33 AM Stephen Stocke <scstocke@gmail.commailto:scstocke@gmail.com> wrote: Hi
We’re migrating some data from Windows file servers to CIFS shares on a 9.1p13 cluster (NTFS security style on the vols). We’re getting errors on some files and folders using Robocopy and the common thread seems to be objects with orphaned SIDs for the owner or DACL entries. We’ve tried other tools with the same results. Robocopy to another Windows file share works fine.
Has anyone else seen this behaviour? We’re assuming that the CIFS server is stopping the copy because it can’t resolve the SID. Is there any way to control that behaviour and just wrtie the DACL with the unresolved SID?
Thanks Steve _______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
You may have to reset the security.. Are you using /copyall option? If not, that may work. I usually used that in the past as it copies the security, as well as the owner of the file.
From: toasters-bounces@teaparty.net on behalf of Stephen Stocke scstocke@gmail.com Date: Wednesday, September 12, 2018 at 9:29 AM To: Basil basilberntsen@gmail.com Cc: "toasters@teaparty.net" toasters@teaparty.net Subject: Re: Copying NTFS Data with Orphaned SIDs
Yes, these are SIDs from deleted users. Usually when some folder has been setup so that Creator/Owner is assigned rights. When the user that created the file/folder leaves, and their account is deleted, the ACE with the unresolved SID remains. It seems that when Robocopy tries to copy the DACL for the file/folder, the filer doesn’t accept it because the SID cannot be resolved. (Speculation based on what we are observing.)
We’re running a separate project to clean these orphaned SIDs up but would like to get the data migrated in the interim ‘as-is’ if possible.
Get Outlook for iOShttps://aka.ms/o0ukef
________________________________ From: Basil basilberntsen@gmail.com Sent: Wednesday, September 12, 2018 5:11 pm To: Stephen Stocke Cc: toasters@teaparty.net Subject: Re: Copying NTFS Data with Orphaned SIDs
Is the sid actually unresolvable?
On Wed, Sep 12, 2018 at 9:33 AM Stephen Stocke <scstocke@gmail.commailto:scstocke@gmail.com> wrote: Hi
We’re migrating some data from Windows file servers to CIFS shares on a 9.1p13 cluster (NTFS security style on the vols). We’re getting errors on some files and folders using Robocopy and the common thread seems to be objects with orphaned SIDs for the owner or DACL entries. We’ve tried other tools with the same results. Robocopy to another Windows file share works fine.
Has anyone else seen this behaviour? We’re assuming that the CIFS server is stopping the copy because it can’t resolve the SID. Is there any way to control that behaviour and just wrtie the DACL with the unresolved SID?
Thanks Steve _______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
-
Basil -
Klise, Steve -
Stephen Stocke