Ran into this on my current engagement, here is the rundown:

 

source server windows 2008 (non R2) Destination Windows 2008 R2

Robocopy with the following commands:

robocopy \\”source server”\E$\”source path” \\”destination server”\d$\”destination path” /e /mir /XD “$RECYCLE.BIN” “System Volume Information” “pagefile.sys” /sec /MON:1 /np  /mt /tee /log:c:\logs\backup_log.txt

 

I used the version of robocopy that was included with windows and ran this on the destination server.  I used the “;NET USE \\”source server”\IPC$ /USER:”  command to specify the credentials prior to beginning the robocopy command.

 

I ended up having to do the following to get decent performance, install the following hot-fix (which allows you to specify which types of attributes and data streams to ignore with new command line arguments)

Significantly slower directory tree replication performance when you use the Robocopy command in Windows 7 or in Windows Server 2008 R2

http://support.microsoft.com/kb/2646535

 

I added the following command line switch to limit the number of retries in case a few files were locked (like system or app files which may have help up the replication due to the default setting being 1 million retries)

/r:10

 

after the hotfix i added this switch to improve the performance:

/NODCOPY

 

in addition i also broke up the job into multiple scripts which ran concurrently to improve efficiency.

I will post a few screen captures at the end. i will use Beyond Compare to analyze and publish the results.  We are cutting over a large file share from a colo environment to a managed services environment and i chose robocopy since that is the tool i always use. 9TB of data is copying as i write this. At the current rate it looks like it will take a week. prior to the hotfix and retries switches it looked like it may have finished in 2014. I wish i was joking.

 

I am still getting a few of these errors now and then:

Error 64 The specified network name is no longer available… which is driving me batty, it may be a bad filter driver from an old backup software or AV software or something else. At this point i am inclined to let it complete and then investigate.