![]() /Z ensures robocopy can resume the transfer of a large file in mid-file instead of restarting.For across-network share operations this seems to be much more reliable - just don’t rely on the file timings to be completely precise to the second. This means the granularity is a bit less precise. /FFT uses fat file timing instead of NTFS.Beware that this may delete files at the destination. /MIR specifies that robocopy should mirror the source directory and the destination directory.I ended up with the following command for mirroring the directories using robocopy: robocopy \\SourceServer \Share \\DestinationServer \Share /MIR /FFT /Z /XA:H /W:5 As source and destination became larger and larger, more memory was required to perform the initial comparison - until a certain point where it’d just give up. ViceVersa would initially scan the source and destination and then perform the comparison. In comparison to ViceVersa, robocopy goes through the directory structure in a linear fashion and in doing so doesn’t have any major requirements of memory. That means it’ll not just copy files, it’ll also delete any extra files in the destination directory. What makes robocopy really shine is not it’s ability to copy files, but it’s ability to mirror one directory into another. That means robocopy will survive a network error and just resume the copying process once the network is back up again. If an error occurs it’ll wait for 30 seconds (configurable) before retrying, and it’ll continue doing this a million times (configurable). You give it a source and a destination address and it’ll make sure all files
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |