File Migration Series – Tool Update

Hello there,

This was supposed to be the fun part of the File Migration Series  – meaning the actual file migration.  After the last part of it – which you can find here, I started to test the tool – Robocopy more, and I was not happy.  While it worked, it had issues and I thought maybe I should try another tool.  I was not able to use SecureCopy – the trial is limited in its number of files.  I know customers that use SyncBack so I thought I would try it.  I will put both Robocopy and SyncBack to the test and see how it goes.

Source and Destination Info

We have 136,982,688.21 KB and 16,920 files. Like in real life that will vary just a little bit. Z: is a Synology storage appliance, and Y: is my DataGravity appliance.


As per the last article in this series I am using the same command line – which is seen below.

robocopy z:\ y:\ /Copy:DATSO / MT:12 /R:5 /V /E /TEE /w:5 /log:test.log

Using the Robocopy that is part of Windows 7 SP1 fully patched to today.  Note: if you care about the folder dates add the /dcopy:T flag to the command above.


We will use version and we will enable the copy of ACL’s as seen in the screenshot below.


Otherwise we will work in the Unattended mode but no other modifications.

Results – Robocopy

Try 1 – 32 minutes – 16,929 files and 130.637 GB

Try 2 – 30 minutes – 16,930 and 130.638 GB

Note: a bunch of files not copied with path exceeded errors.  Between each try I deleted the destination folder structure.

Results – SyncBack Pro

Try 1 – 4 hours and 5 minutes – 16,906 files and 136,961,428.39 KB

Try 2 – 1 hour and 47 minutes – 16,920 files and 136,982,688.21 KB

Note: not sure why the difference in times, but am working with support.  Between each try I deleted the destination folder structure.


I should mentioned that I will be doing all of my other work, and testing like this using SyncBackPro.  See here where I mention that and some of the why – which is important.  This is a direct result of doing a bunch of this file migration testing as well as actual file migration work.


=== END ===

Leave a Reply