W
Wandersick
Hi there,
We are having a strange problem with Robocopy /SECFIX and wonder if it is by design.
BACKGROUND
We are performing a cross-forest Windows file server migration between two trusted domains with robocopy in which file and folder permissions also need to be migrated along with data.
We found that with /SEC, /COPYALL or /COPY
ATSOU, file permissions are carried across from source (a network mapped drive) to destinations (a local drive), but folder permissions are not, unless /SECFIX parameter of robocopy is also applied.
PROBLEM
We found using /SECFIX loses the goodness of robocopy -- copying only deltas; all files and folders in the destination would be re-copied from source and shown in robocopy log as "modified" instead of "same". This is undesirable as we often rerun the script to copy delta during different stages of the migration project.
What is weird is that this will not happen on a subsequent run of /SECFIX. That is, on the next run of the same command, it will show all file as "same". However, in the next run it will show "modified" again. Therefore, we get this loop:
Same > Modified > Same > Modified > Same ...
Which is depicted in the pictures below:
Same:
Modified:
And on and on...
Note 1: The command in the example is: robocopy d:\css-designer c:\css-designer /mir /copyall /b /secfix
Note 2: There is no need for a network-mapped drive to reproduce this issue; local drives would do
Note 3: We tried robocopy in Windows Server 2012 R2 and Windows 10. No difference.
Continue reading...
We are having a strange problem with Robocopy /SECFIX and wonder if it is by design.
BACKGROUND
We are performing a cross-forest Windows file server migration between two trusted domains with robocopy in which file and folder permissions also need to be migrated along with data.
We found that with /SEC, /COPYALL or /COPY
ATSOU, file permissions are carried across from source (a network mapped drive) to destinations (a local drive), but folder permissions are not, unless /SECFIX parameter of robocopy is also applied.PROBLEM
We found using /SECFIX loses the goodness of robocopy -- copying only deltas; all files and folders in the destination would be re-copied from source and shown in robocopy log as "modified" instead of "same". This is undesirable as we often rerun the script to copy delta during different stages of the migration project.
What is weird is that this will not happen on a subsequent run of /SECFIX. That is, on the next run of the same command, it will show all file as "same". However, in the next run it will show "modified" again. Therefore, we get this loop:
Same > Modified > Same > Modified > Same ...
Which is depicted in the pictures below:
Same:
Modified:
And on and on...
Note 1: The command in the example is: robocopy d:\css-designer c:\css-designer /mir /copyall /b /secfix
Note 2: There is no need for a network-mapped drive to reproduce this issue; local drives would do
Note 3: We tried robocopy in Windows Server 2012 R2 and Windows 10. No difference.
Continue reading...