If it is, you could try skipping junction points with /XJD to see if that allows you to stop the loop(s) it's getting stuck in. Since you have a log, you could try looking at the bottom of it and see if the directory structure is repeating itself. If you shrink the height, or better yet, minimize the command prompt window, you can greatly speed up the copy when you have a bunch of small files.ฤก8 hours is very long for the amount you're trying to copy, so it's possible that you either have an insane amount of small files that you're trying to copy, or you have some recursion in your directory structure. It will slow things down a little bit if you have an extreme amount of small files (tens of thousands or more), but it can also help you determine if there's a problem. Personally, I always use the /TEE option along with the /V and /LOG: options when using robocopy so that I can monitor what is going on, (and if a crash happens, I can go back and see if there were issues as well). As you've stated, other files will be ignored since they have the same modified date/time as the source files. When it first creates a file, it sets the "Modified" time to, so basically as long as your clock is set correctly, it will see that time and restart the copy process. Unless you use the /XN option, robocopy will delete whatever the last file it was working on and start the copy again. I've used robocopy for years now, and know that you can stop a copy in the middle of a file and restarting will swiftly get back to where it left off.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |