Robocopy on Windows Server 2012 r2 syntax

Hello Experts,

I need to copy over an entire drive from one server to another. I wanted to use Robocopy and tried the following

robocopy \\servername\G$ \\servername\g$  

I get page file error (page in use)
so I tried
robocopy \\servername\G$ \\servername\g$  /XF pagefile.sys      but it only copied over some of the folders and data.

What is the correct syntax?

thanks!
Member_2_7964761Asked:
Who is Participating?
 
MacleanConnect With a Mentor System EngineerCommented:
robocopy \\servername\G$ \\servername\g$  x* /E /XF pagefile.sys if not mistaken.
Worst Case you can do it using a GUI such as Roadkills Unstoppable Copier, which allows you to pause & verify copy as well. Just download the portable version for Win7/8, works fine on all server versions.
0
 
Todd NelsonSystems EngineerCommented:
Do you need to copy permissions too?

Here is a good reference with examples and syntax...
0
 
QlemoDeveloperCommented:
Of course the servernames in your command are different?
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Member_2_7964761Author Commented:
Thanks! I will try this tomorrow. The one switch I don't see is to skip over files in use? (Page file in use) is this available?
0
 
NVITConnect With a Mentor Commented:
Your example shows you're copying to the root of the target server, which has an active pagefile.sys, which is open and locked.

Do you need to image instead?
0
 
serialbandConnect With a Mentor Commented:
robocopy \\servername1\G$ servername2\G$ /copyall /Mir /R:1 /W:1 /xf pagefile.sys

There is no robocopy switch to skip over in use files.  You can continue to run robocopy with files in use and just have it skip over them quickly.  Basically, you can run robocopy again and again until you get most of the files, except the few system files in use.  I don't understand why you would use a pagefile on G$, which I presume is a data drive.  If the server has enough RAM, a pagefile isn't really needed.

Normally, robocopy will just error out, wait 30 seconds and retry 3 times by default.  That's too much of a delay, hence /R:1 and /W:1.  You generally want to keep all permissions and mirror the entire tree structure, if it's a file share, hence /Copyall and /Mir.  Of course, you can still skip the huge pagefile that will always be changing.


If you really need to copy files in use, there's hobocopy https://github.com/candera/hobocopy
To use Hobocopy, you'll also need to turn on Volume Shadow copy.  It will copy all files, including those in use, by copying the shadow copy version of the in use file.
0
 
Member_2_7964761Author Commented:
Thanks for your help! Got them copied over but still missed a lot of files plus it took 2.5 hours.  We are looking for the best solution for DR.  Is it possible to mount a network drive. This is  possible on Windows server 2012 r2?
0
 
QlemoConnect With a Mentor DeveloperCommented:
Mounting a network drive and using it is possible, but won't help in the copy process. Only if access to the UNC path is scattered over a longer period, you might gain some performance, but while running RoboCopy the paths are in use full time, so that does not apply here.

Successive RoboCopy runs should not last that long. There is overhead per file to check, but the lengthy operation is the copy itself, and that will only happen for changed files (but copy those as a whole). So if you run RoboCopy now again, it should be finished in several minutes (instead of hours).
0
 
serialbandConnect With a Mentor Commented:
If it only took 2.5 hours for the entire copy, the successive robocopy will easily be under 5 minutes, if you have very few files changing and if you run it immediately after, unless you have numerous and constant file changes within that 2.5 hours.
0
 
MacleanSystem EngineerCommented:
Why not use DFS if you want DR for data. Its not the best solution out there perhaps, but its reliable enough, comes with windows and incrementally updates files as data changes, plus if server A fails, it will keep running on the name space using server B. I suppose this is for user data, not full system backups.
0
 
Member_2_7964761Author Commented:
Thanks for your help!
0
All Courses

From novice to tech pro — start learning today.