Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've had Robocopy running for about 24 hours's moving 2.6million images across a network, and is probably less than 10% of the way through. Is there a faster way to do this?

share|improve this question
Not enough information in your post to help. How big are the images? (lots of small file access?). How fast is the network. How heavily loaded is the network. Are the disks maxed out? etc etc. – Hennes Oct 16 '12 at 20:45
sorry, assumed that wouldn't be relevant. Images are 100k ish, network is gigabit I think, network is under no load, no load on disks – Paul Oct 16 '12 at 20:50
2.6 millions files of any kind are going to take a while to move, be they 512b .ico files or 2GB Ghost images. That's enough for an answer. – sysadmin1138 Oct 16 '12 at 20:52
@sysadmin1138 - I was just writing the same comment. The overhead in switching files during a file copy is high, but that said, 260,000 in 24 hours is certainly on the low side. – Mark Henderson Oct 16 '12 at 20:53

Probably. Depending on the version of robocopy you have, there is a multithreaded copy option, /MT:16, where the number is the number of individual threads to run. From experience it works much, much better with UNC-described network locations as mapped drive-letters force serialization that undoes the multithreading.

share|improve this answer
Like \\vpsa\images ? – Paul Oct 16 '12 at 20:56
@IP Exactly like that. If you're doing local-to-local you don't need to bother, but you're not so you'll need UNC for whichever side is the network location. – sysadmin1138 Oct 16 '12 at 20:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.