Over the years of usage, I have found this syntax the one I keep going back to over and over again:
Be careful with some of the options if you are just trying it out, as some of them move the data (deleting the files and folders in the source location or the target location). There are quite a few options when it comes to file server migrations using Robocopy, and you might not know where to start.
#EMCOPY SWITCHES HOW TO#
So, chances are if you start a command prompt on your computer and type “robocopy /?” you’ll see the help dump of information to your screen on how to use the utility. Beginning in 2008 (and thereafter), it was bundled with both desktop and server operating systems starting with Vista and Server 2008.
#EMCOPY SWITCHES WINDOWS#
Back then and until 2008, it was available with the Windows Resource Kit download. Robocopy has existed since NT4 days in 1996, so this is likely not the first time you are hearing of it. When the need arises to duplicate the data for the migration to the new server, I always go back to old faithful- Robocopy (Robust File Copy for Windows). However, this process only works elegantly when the file share data exists on a volume that isn’t where Windows or any applications are installed. It is also generally very quick as there is no need to copy terabytes of data from one server to another. This maintains NTFS permissions if both servers are members of the same Active Directory domain. Sometimes if the server doesn’t have any other roles or functions installed other than just a file server, then I could simply unshare the shares on the original server, detach the virtual hard disk from it, attach the virtual hard disk to the new server, and reshare the shares. With various flavors of Windows Server operating systems going out of support this year, I have found myself with a decent number of file server migrations from one system to another. All materials that appear on the KA web site are distributed and transmitted "as is," without warranties of any kind, either express or implied, and subject to the terms and conditions stated in this disclaimer.This blog is part 1 of a 2-part series.
KA also assumes no liability for improper or incorrect use of materials or information contained on its web site.
KA assumes no liability for any damages or loss of any kind that might arise from the use of, misuse of, or the inability to use the KA web site and/or the materials contained on the web site.
#EMCOPY SWITCHES PROFESSIONAL#
Information provided on the KA web site should not be used as a substitute for IT or other professional advice. KA also retains the right to change any content on its web site without prior notice. KA, however, cannot guarantee the quality, content, accuracy, or completeness of the information, text, graphics, links, and other items contained on its web pages because the material comes from a variety of sources, collected and maintained for different purposes. KA attempts to provide accurate, complete, and timely information. Knowledge Ascent (KA) makes information available on its web site to enhance public knowledge and promote a better understanding of the IT environment. If you have any issues with your system I highly recommend you contact the technical support of the vendor. If you have a doubt call technical support, I do not assume any liability for any errors or omissions in those articles, I also make no representations as to the accuracy or completeness of any information on this site or found by following any link on this siteĬontent published here is tested in my own lab and is not reviewed or approved by any vendor.
The site reflects my knowledge and opinions, I do recommend that you test what you learn in the lab environment before implementing it in production. The focus is on hands-on work, technical documentations and architecting solutions. It is not targeting sales or intending to promote any specific technology or vendor. This site is targeting Solution Architects, Implementation Engineers and Systems Administrators.