Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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 need to copy 15 .bak files, each 115-120GB. My copy process is going to be from a production server. How can I do this with Robocopy? or How can I do this with Power shell?

share|improve this question

closed as off topic by Chris S Mar 29 '12 at 15:21

Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

Have you made any attempt at all of figuring this out on your own? Why on earth do you want to use PowerShell for it? – pauska Mar 29 '12 at 14:21
If this is a one time copy, just copy them using xcopy and don't spend any more time thinking about it. if you need to build a process to automate this for the future, robocopy or a powershell script may make more sense. – uSlackr Mar 29 '12 at 14:27

You haven't said which version of Windows you are using. If you're using Server 2008 R2, for files that big, I would use XCOPY with the /J switch:

"Copies using unbuffered I/O. Recommended for very large files."

If Using 2003/2008 R1, you might want to take a copy of ESEUTIL.exe and use that with the /Y switch.

Either of these methods will let you copy the files in an unbuffered manner, thereby preventing your server from falling over due to memory or pool depletion.

I have a customer who kept taking out one of their cluster nodes when they copied large SQL DB files around (even locally). Getting them to use eseutil has prevented further outages.

share|improve this answer
Why not robocopy? – Pacerier Apr 24 '15 at 17:37
Robocopy has not always had the /J option for unbuffered I/O. In fact, it still doesn't appear to be documented for Windows 2012: – Adam Thompson Apr 27 '15 at 9:51
I remembered that the specification for robocopy is a pdf article, not that link you mentioned. – Pacerier May 24 '15 at 16:02

OK :

robocopy /?

ROBOCOPY :: Robust File Copy for Windows

Started : Thu Mar 29 10:23:30 2012

          Usage :: ROBOCOPY source destination [file [file]...] [options]

         source :: Source Directory (drive:\path or \\server\share\path).
    destination :: Destination Dir  (drive:\path or \\server\share\path).
           file :: File(s) to copy  (names/wildcards: default is "*.*").

You will get much better advice, and learn a lot, if you try the simple things yourself and then ask questions when you're confused or get stuck.

There's little difference between copying big files, and copying little ones. Obviously the big ones take longer, and that might cause problems if you have a limited amount of time to do it in. But you didn't say that was the case. If there's details you haven't included in your question, then please edit it to include them.

share|improve this answer
+1 on trying first – uSlackr Mar 29 '12 at 14:28

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