Robocopy log (find failures)

[Jordan]

Just did a massive copy from one drive to another with RoboCopy. 250 GB
total. I copied and logged and at the end of the 40 MB log file I see that
I had 3 files fail out of the 750,000+ files.

Every file is listed in the log where it seems all of them show "new file".
I tried to do a seach on the file for "Fail" but I only find fail if it is
in the file name or the summary at the end. What are some things I can
search for to find what file has failed.

Normally I would just stick this in Excel and sort, but I can't put in 3/4
of a million rows into Excel.

 

[Pegasus \(MVP\)]

Just did a massive copy from one drive to another with RoboCopy. 250 GB
total. I copied and logged and at the end of the 40 MB log file I see
that I had 3 files fail out of the 750,000+ files.

Every file is listed in the log where it seems all of them show "new
file". I tried to do a seach on the file for "Fail" but I only find fail
if it is in the file name or the summary at the end. What are some things
I can search for to find what file has failed.

Normally I would just stick this in Excel and sort, but I can't put in 3/4
of a million rows into Excel.

You can easily sort a log file at the Command Prompt, using sort.exe

To find out what warning message you get, you could force an error,
then watch what happens. I did it just now by attempting to copy some
locked Outlook files. Here is the result:
==============
-------------------------------------------------------------------------------
ROBOCOPY :: Robust File Copy for Windows :: Version XP010
-------------------------------------------------------------------------------
Started : Mon Jul 28 16:49:06 2008
Source = d:\outlook\, Dest = d:\
Files : c*.*

Options : /COPYAT /R:1000000 /W:30
------------------------------------------------------------------------------
2 d:\outlook\
100% New File 1391 Current Archive.log
0.0% New File 9.4 m Current Archive.pst
2008/07/28 16:49:06 ERROR 33 (0x00000021) Copying File
d:\outlook\Current Archiv e.pst
The process cannot access the file because another process has locked a
portion of the file.
==============
Open your log file with MS Word, then look for the word "cannot" (for
example).