SOLVED: How to Robocopy On Server 2012 With Data Deduplication
This was surprisingly tricking issue to deal with. If you are copying TO or FROM a Deduplicated file share you must make certain:
Do NOT robocopy the a partition or volume – only robocopy shares\folders. This is because the dedup information is stored in the SYSTEM VOLUME INFORMATION folder and at folder can not be migrated with robocopy. It needs to be built on the partition\volume that the dedup exists on.
Make sure you do NOT use /XJ switch. XJ is Exclude Junction points and junction points (JP’s) are tied into the deduplication process. In previous versions of Windows, starting with Vista, I have needed to use /XJ because if robocopy hit tried to copy a JP’s the destination disk would fill up with thousands of nested folders matching the name of the JP. Worse this problem was not readily recoverable by deleting those folders, even using the old POSIX commands. The only solution, according to Microsoft Partner Support (and from my experience) was to reformat the disk… not cool.
Microsoft Partner Support also indicated that you should use the /ZB (backup mode) switch but our experience thus far has not borne this out as a requirement.
Just wanted to thank you for this post. I recently moved over to a new backup platform that (behind the scenes) after mounting their restore point apparently uses Robocopy to copy the files. Upon doing so, *LOTS* of files were being skipped for an unknown reason. Upon looking at the switches in the logs that the backup was using - I noted it was using /XJ. Once you take this out and manually run the same command without - all of my files were being restored. This post led me to that conclusion. Thank you!!!
The solution to your thousands of nested folders due to ugly junction points can actually be solved using robocopy.
View Comments
Just wanted to thank you for this post. I recently moved over to a new backup platform that (behind the scenes) after mounting their restore point apparently uses Robocopy to copy the files. Upon doing so, *LOTS* of files were being skipped for an unknown reason. Upon looking at the switches in the logs that the backup was using - I noted it was using /XJ. Once you take this out and manually run the same command without - all of my files were being restored. This post led me to that conclusion. Thank you!!!
The solution to your thousands of nested folders due to ugly junction points can actually be solved using robocopy.
mkdir empty
robocopy empty bad /mir
All junction points removed like magic.
That is an awesome solution. Thanks,