It seems that NTFS rules take precedence over Robocopy when copying folders from one volume to another. Is there a way around this?
Example: Copying a folder from one volume to another using the Robocopy /COPYALL switch should copy across all of the file info. This is equivalent to /COPY:DATSOU with the S being NTFS ACL's (SS64 Robocopy). However, when I execute the Robocopy command, the resulting ACL on the destination folder represents the parent, which is in line with the NTFS rule of moving files between volumes results in the destination inheriting permissions from its parent (GlobalScape.com).
Folder structure of the source is: \Sector\Customer\Project with each project folder having (amongst others) a Data In and Data Out folder. Each project folder will have slightly differing permissions based on which groups are working on the project.
Folder structure of the destination is similar but as the destination is an archive location for the source, some of the project folders are not there.
We want to copy the project Data In and Data Out folders which are in the source but not the destination across, maintaining the permissions and creating the project folder itself if it doesn't exist, and then copy all of the files in the Data In and Data Out folders which are older than 'x' maintaining permissions on the files too.
Is this a case of creating the destination folder structure first, setting the correct permissions and then copying the data?
0 Answers