However, it does not have the logging capabilities I needed. This is a great tool, except it cannot always copy opened files and is not good with incremental copying.įinally, I remembered the old, faithful xcopy utility that has always worked for me, even way before Microsoft rolled up PowerShell. I then decided to try the Copy-Item PowerShell cmdlet. There is verbose logging, which is nice, but the last thing I needed were hundreds of thousands of lines to analyze. Another problem was that there is no obvious way to log information about failed copies only. Even with the minimal number of retries set, it wasn’t acceptable. However, it didn’t work for me because it spends too much time trying to retry copying failed files. It is a very nice utility with a lot of options. For instance, if somebody changed already-copied files while the rest were still copying, the tool needs to be able to run an incremental sync at some point.įirst, I thought about utilizing robocopy. It is also worth mentioning that one of the requirements was to build a tool that can be used by end users to repeat process. What if the copy operation partly fails? There is no way of telling which files were copied and which were not. The biggest problem is not even the speed.

Drag and drop, yeah? With a few gigabytes of data and several thousands of files, drag and drop doesn’t look like a great idea. I was recently assigned a very simple task: copy the sales department folders from an old file server to a new one.

Robocopy force copy