

MD5 is a fast hashing algorithm so it is more vulnerable to certain types of attack than a slow one, but you can't take a hash and algorithmically determine what input produced it.īUT an MD5 hash of a file is just a unique signature for that file. MD5 is not a secure hashing algorithm and is easily reversed.Ī hash cannot be reversed. Increase the folder size to say 6TB and 15,000,000 files/folders, you'll definitely see the differences. So 6 minutes quicker with EMCopy, with the same attributes being copied, same number of threads, and permissions. Security Descriptor Setting(s) done: : 63477Īmount of copied byte(s) : 30 GB (32 730 088 649 Byte(s)) Log file : /log:t:\emcopy_test_same_thread.log Total Copied Skipped Mismatch FAILED Extras Let me state that should not be a bench mark, many factors can change the outcome of these tests, but I ran the tests on the same system, and with the same processes running both times. Here is a test I did, just for this post, EMCopy vs.

There are down sides to multithreading though, e.g. Comparing EMCopy to RoboCopy with the same number of threads, EMCopy is 25-35% faster. RoboCopy does support 128 threads on new versions of Windows 2008R2 and above. Multithreading: EMCopy supports up to 256 threads.

I'll just give you a few quick points of what works better with EMCopy.

It is a free data migration tool, CLI only, and has a lot of features that just seem to work better than RoboCopy. What I have found on a long quest of trial and error is a utility called "EMCopy" from EMC. However, I've gotten to the point where RoboCopy is just not fast enough. First off, I love RoboCopy, I've used it for over a decade now, and I have no issues with it.
