Super User is a question and answer site for computer enthusiasts and power users. 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'm using Microsoft's imagex.exe for backup and restore in 2 configurations: A mirror raid of 2 500GB hard drives, and a mirror raid of 2 1TB hard drives. The second configuration is 30% slower even though in both configurations the number of files and their size is about the same.

My question are:

  1. What are the parameters that effect the speed of Microsoft's imagex.exe in general?

  2. Would a 1TB hard drive be slower than 500GB hard drive, even though they both contain the same amount of data?

Thank you

share|improve this question
Are they using the same controller? are they both the same speed in terms of interface and RPM? Are you doing this from within Windows or from a boot disc? I suspect a driver could be to blame if that's the case. If you're using the verify switch or compression, try with or without those options. What's the exact syntax you're using to call imagex? – MDT Guy Jan 15 '13 at 16:51
Thanks for your reply. It's a different configuration: The 1TB is through SATA3 on a recently released motherboard, the 500GB is through SATA2 running on a motherboard from a few years ago. Same RPM. I'm running the simplest commands "imagex /capture" and "imagex /apply". This is done through WinPE. – Tom Chakam Jan 16 '13 at 7:13
My only guess is that imagex takes longer because it's a bigger disk it has to scan, either that or there is some strange driver issue. – MDT Guy Jan 17 '13 at 22:54

Your Answer


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

Browse other questions tagged or ask your own question.