topic Re: Robocopy command line in script acquires defaults? in Windows Server 2003

Robocopy command line in script acquires defaults?

Fred Hinchliffe — Tue, 13 Mar 2007 09:19:21 GMT

I assembled the following command line for execution in a VBS script:
Call oShell.Run("robocopy.exe " & sCopySource & " " & sCopyDestination & ssday & sopt)

where:
sopt = " /MIR /NP /LOG:e:\BackupCycles\carbon\robolog.txt"

When Robolog executes, I get a mish-mash of inconsistent options, most of which I did not ask for (as quoted from the log):
Options : *.* /S /E /COPY:DAT /PURGE /MIR /NP /R:1000000 /W:30

I understand the R and W, but why the S, E, PURGE ? Are they not redundant or even conflicting?

Re: Robocopy command line in script acquires defaults?

Marc Carney — Wed, 18 Apr 2007 10:54:10 GMT

Have a look through the Robocopy documentation which is very comprehensive and is free download.

I believe the /MIR is for mirror which implies some other options like /COPY:DAT /PURGE /S /E etc so perhaps it is just expanding the options in full for you.

Also, I remember that there is a switch for Robocopy that will save settings to registry creating a 'new' default. Perhaps it is reading the other settings /R: and /W: from whats in the registry on your PC.

Re: Robocopy command line in script acquires defaults?

Joel Belizario — Sat, 28 Apr 2007 03:57:19 GMT

Those retry and wait values are default for Robocopy if they are not specified explicitly in command line. I've had a number of copies still going when I've come back into the office for this reason... *doh*