I bet the difference is the /SEC (or /COPYALL) option requires a lot
more network traffic to retrieve the security information for each and
every file (even files that already exist on the destination) to see if
any changes in the security parameters are needed.  You could run
FILEMON (or it's replacement PROCMON) from Sysinternals (Microsoft) to
see the file activity on one end.  You could run it without the /SEC
option most of the time as the copied files will just get their security
from the parent directory by default, and then run it occasionally with
/SEC to fix up any permission oddities.

 

From: Ralph Smith [mailto:m...@gatewayindustries.org] 
Sent: Wednesday, July 14, 2010 12:13 PM
To: NT System Admin Issues
Subject: EXTERNAL:RE: Robocopy /SEC

 

About 24K files, 3.6GB see below.  It looks like all the time is in the
"Extras" column.

I don't see anything of interest in the event logs of either server or
in any DC. 

 

------------------------------------------------------------------------
------

 

                Total    Copied   Skipped  Mismatch    FAILED    Extras

     Dirs :      3981        75      3906         0         0        12

    Files :     24606       370     24236         0         0        57

    Bytes :   3.646 g  147.11 m   3.503 g         0         0    3.08 m

    Times :  34:31:10   0:32:41                       0:00:00  33:58:28

 

    Speed :               78651 Bytes/sec.

    Speed :               4.500 MegaBytes/min.

 

    Ended : Wed Jul 14 05:01:13 2010

 

 

 

 

Here's a log from before I added the /SEC switch:

 

------------------------------------------------------------------------
------

 

                Total    Copied   Skipped  Mismatch    FAILED    Extras

     Dirs :      3903         0      3903         0         0         0

    Files :     24231        14     24217         0         0         0

    Bytes :   3.613 g    5.63 m   3.607 g         0         0         0

    Times :   0:36:43   0:01:09                       0:00:00   0:35:33

 

    Speed :               85009 Bytes/sec.

    Speed :               4.864 MegaBytes/min.

 

    Ended : Thu Jun 17 19:06:44 2010

 

 

 

 

FWIW, I'm copying from a Win 2003 SP2 server to a Win 2008 server over a
VPN (DSL at one end, cable at the other)

The command line running on the remote server is:

c:\robocopy\robocopy D:\Data "\\MainOfficeServer\BranchNameShare" /MIR
/SEC /LOG:c:\robocopy\DailyBackupLog.txt /R:10 /w:10 /TS 

 

 

 

 

Ralph Smith

Gateway Community Industries

845-331-1261 x234

 

________________________________

From: David Lum [mailto:david....@nwea.org] 
Sent: Wednesday, July 14, 2010 10:03 AM
To: NT System Admin Issues
Subject: RE: Robocopy /SEC

 

How much data are you moving? I use /SEC or /COPYALL and I don't see a
24x increase in copying 4-5GB and thousands of files. Anything in the
event log of the source, target, or DC's?

David Lum // SYSTEMS ENGINEER 
NORTHWEST EVALUATION ASSOCIATION
(Desk) 971.222.1025 // (Cell) 503.267.9764

 

 

 

From: Ralph Smith [mailto:m...@gatewayindustries.org] 
Sent: Wednesday, July 14, 2010 6:19 AM
To: NT System Admin Issues
Subject: Robocopy /SEC

 

I've been using RoboCopy for years to copy files from remote offices
back to a server at the main office and it has worked great.  Recently I
had to for the first time use the backed up files when rebuilding a
server at one of those remote offices and realized that because I was
only using the /MIR switch I didn't have any of the security settings.
Not a big deal because I have them documented and was able to recreate
them.  However, I decided to add the /SEC switch for future backups.

 

What I have found is that whereas in the past it used to take on the
average 30 to 60 minutes every night, since adding /SEC it now runs for
24 hours or more, even though the actual copy time is only 30 minutes or
so.

 

Does anyone know if this is typical behavior when using RoboCopy with
/MIR /SEC?

 

Ralph 

 

 

Confidentiality Notice:

******************

This communication, including any attachments, may contain confidential
information and is intended only for the individual or entity to whom it
is addressed. Any review, dissemination, or copying of this
communication by an yone other than the intended recipient is strictly
prohibited. If you are no t the intended recipient, please contact the
sender by reply email, delete a nd destroy all copies of the original
message.

 

 

 

 

 

 

Confidentiality Notice:

******************

This communication, including any attachments, may contain confidential
information and is intended only for the individual or entity to whom it
is addressed. Any review, dissemination, or copying of this
communication by an yone other than the intended recipient is strictly
prohibited. If you are no t the intended recipient, please contact the
sender by reply email, delete a nd destroy all copies of the original
message.

 

 

 

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to