From: Mike N. 

On Wed, 12 Apr 2006 07:14:42 +0300, "Antti Kurenniemi"
 wrote:

>If you're just copying files and not the OS, simply plug in the second drive
>and drag&drop in the explorer.

    I've found that RoboCopy is fault tolerant and allows directory
exclusions.   Xcopy has a nasty habit of giving up on a single failure.

> No app really makes copying any faster/slower
>than disk access allows, so it's pointless to make it any more complex a
>case than need be.

    In the case of going from Drive->drive, there may be some benefit to
overlapping the read / write operations on different threads to keep both
drives operating at full throughput.


    I finally got a chance to do a very unscientific benchmark.

  Dual processor 2.1 Ghz, SCSI drives (I forget which type of bus), 1 G
RAM, both drives 15,000 RPM.   Windows Server 2003.   RoboCopy from Server
2003 resource kit.

  Data: 7.3 G of stuff from the apps directory, Borland 2005, Visual Studio
2003 and 2005 files, etc.

RoboCopy 11:01
XCopy   11:10
Explorer: 11:45

    Not a huge difference between RoboCopy and XCopy, but the addtional
control of RoboCopy will be worth it.

    In this case, I'm guessing that either all 3 methods use multithread
copy operations or none of them do.

--- BBBS/NT v4.01 Flag-5