Tag Info

New answers tagged


It appears to me that Robocopy is A) buggy, and B) hooks into the kernel in some way that can make the entire system incredibly unstable when it bugs out. We've seen this happen quite often (especially with the MT option) when syncing over reasonably high-speed WAN links (20Mbps - 100Mbps). So I'm pretty sure it's not a NIC driver having traffic volume ...


Create a file named directories.txt: C:\dir1 C:\dir2 C:\dir3 C:\dir4\subdir Then write a Powershell script named RobocopyDirsFromList.ps1: Foreach ($Directory In Get-Content .\directories.txt) { robocopy "$Directory" "h:\UserHome" /E /SEC /Copy:DATSOU /log:c:\logfile.txt } Note: I've not tested this, please test first.


I was able to manage this problem with the commandline tool strarc.exe from LTR-Data. This tool copies the files, as far as I understand, on a lower layer than robocopy. All attributes, ACL's are exact on the destination like the source - even the timestamps. The junctions where also correct copied. The command is $srcDisk = "Y:" $dstDisk = "Z:" cmd /c ...


robocopy F:\ E:\ /E /v /S /COPY:DAT /DCOPY:T /R:2 /W:0 /NP > C:\teste\logbackup20141206.txt To Copy all content from drive F: to drive E: I use the command above.


I am not aware of any version of robocopy that supports copying the Compressed attribute. (I just tested with the version that ships with Windows Server 2012 R2 just to be sure that a version newer than my Windows 7 laptop still did not include this behavior.) If you're going to use robocopy you'll need to script something to follow-up behind it compressing ...

Top 50 recent answers are included