First published on TechNet on Sep 07, 2010 Ned here again. Previously I discussed options for performing a hardware or OS replacement within an existing DFSR Replication Group. As part of that ...
Updated Jan 07, 2021
Version 3.0
Blog Post
NedPyle Hey Ned I just want to thank you for these articles on DFSR as it's helping me a ton here! I have a question that I can't seem to find anywhere so was hoping you could answer? I am adding in 2 new DFSR servers to my existing DFSR environment (decommissioning the old 2012 R2 boxes) and then using the new ones once everything is done. I followed the attack of the clones article on exporting dfsrclone and then preseeding my new server and import dfsrclone and add server to replication. Tested it in a test environment.
My 2 issues are as follows in my production environment. I preseeded a server volume of about 500G robocopy command exactly as you have it in your article Robocopy.exe "X:\" "\\new-server\X$" /E /B /COPYALL /R:6 /W:5 /MT:64 /XD DfsrPrivate /TEE /LOG+:preseed.log. The issue is I had about 50G of data that failed and from what I can tell they all say "access denied" error 5 and error 32 but mostly error 5.
If I import my dfsrclone to my new server for this volume knowing it had 50G of failed files, will those just have to replicate since they weren't able to be preseeded? is that all my issue is? just waiting for things to sync? if that is the case I should be fine. Just making sure I don't have to have a perfect preseed for things to continue. Waiting is ok for replication. We are in no rush to get things going on the new servers. Just eventually need to phase out the old here.
Thanks for any response! I'm surprised nobody has commented on these as they are great articles!