Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums

none
Robocopy in Server 2012 - /mt switch removed.

 > 

    Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I search the internet high and low and find no questions on why this is not operational or working in Server 2012.

    Was multi-threading not a useful feature?  Figured I might as well start a thread to hopefully get insight for others that may ask that same question now and in the future.

    Technet reference.

    Robocopy

    /MT[:N]

    Creates multi-threaded copies with N threads. N must be an integer between 1 and 128. The default value for N is 8.

    The /MT parameter cannot be used with the /IPG and /EFSRAW parameters.

    Redirect output using /LOG option for better performance.

    Note

    The /MT parameter applies to Windows Server 2008 R2 and Windows 7.

    Tuesday, January 29, 2013 9:36 PM
    |

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    In Windows 2012, with "robocopy /?", we could still find /MT[n:], so it should still be supported and the article may not add this new information.

    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.

    Wednesday, January 30, 2013 9:02 AM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Confirmed.  I ran some tests with the /mt switch and it is supported.  I opened Task Manager in 2012 and watched the THREAD count and it moved accordingly.  Defaulted to 2 threads so I increased it.  Performance is MAJORLY affected from default to increasing thread count.  Memory usage is seriously optimized and different from Win 7 / 2008 R2 as it uses very little memory even at 128 Threads. 

    One word, if you go too high, you will lose network connections on big files that will use multiple connections to the servers.  I am guessing this is a CONFIGURED network limitation.  So, 64+ threads fails on many files indicating that the network connection is no longer available and then succeeds on other files after the failure.

    So, very impressive memory utilization over the past versions.  Documentation on the 2012 site needs to be updated and not just COPY/PASTED from 2008.

    Thursday, January 31, 2013 2:48 PM
    |

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    In Windows 2012, with "robocopy /?", we could still find /MT[n:], so it should still be supported and the article may not add this new information.

    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.

    Wednesday, January 30, 2013 9:02 AM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Confirmed.  I ran some tests with the /mt switch and it is supported.  I opened Task Manager in 2012 and watched the THREAD count and it moved accordingly.  Defaulted to 2 threads so I increased it.  Performance is MAJORLY affected from default to increasing thread count.  Memory usage is seriously optimized and different from Win 7 / 2008 R2 as it uses very little memory even at 128 Threads. 

    One word, if you go too high, you will lose network connections on big files that will use multiple connections to the servers.  I am guessing this is a CONFIGURED network limitation.  So, 64+ threads fails on many files indicating that the network connection is no longer available and then succeeds on other files after the failure.

    So, very impressive memory utilization over the past versions.  Documentation on the 2012 site needs to be updated and not just COPY/PASTED from 2008.

    Thursday, January 31, 2013 2:48 PM
    |