This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi,
I have (had!) two file servers running DFS with Domain based replication between them (the folder structures were the same). One server was 2012 and the other 2012R2. The R2 server has failed and is switched off. I am just installing a new server with 2019 and am looking for some help on how to rebuild the server to ensure that the good data replicates to the new server without losing data (I do have backup though.)
Can someone give me a few pointers please?
Should I pause replication at the moment to make sure that the system does not keep trying to replicate to the bad server?
e.g., after I building the new server, do I seed the new directories before configuring DFS (using Robocopy perhaps?)
When do I install DFS on the new server?
When do I configure replication?
When do I remove the old server from the replication group?
As you can tell, I am a bit out of my depth here, so any help would be greatly appreciated!
regards
Dave
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
Hi Frank,
thanks a lot for the comprehensive reply, some questions though please . . . .
Step 5, if the data is all also held on the other DFS server, is it really necessary to restore from backups?
Does step 6 not cover this? (I realize that using replication to copy the data might be slow, hence my question about pre-seeding with Robocopy)
regards
Dave
Hello dave_home,
Thank you for posting in Microsoft Community forum.
1.Please back up all the data on both DFSR server.
2.The DFSR server (2012 server) with all good data should be the primary member.
3.You can remove the failed DFSR server.
[SOLVED] Removing server from DFS-R? - Windows Server (spiceworks.com)
4.Then install DFSR role on new 2019 server and configure DFSR replication group, keep the same replication directory as the 2012 server.
5.After the configuration and if all the configuration is correct, then all the data on the 2012 server should be replicate to new 2019 DFSR server automatically.
I hope the information above is helpful.
If you have any question or concern, please feel free to let us know.
Best Regards,
Daisy Zhou
Hi Daisy,
thanks a lot for the info, yes, it is helpful.
I still have a query on whether to just let the data replicate, or whether to "pre-seed" the new server's DFS directories using Robocopy?
Are there any advantages / disadvantages in doing that?
regards
Dave
Hello dave_home,
Thank you for your reply.
I still have a query on whether to just let the data replicate, or whether to "pre-seed" the new server's DFS directories using Robocopy?
A: Both should be OK. And if you "pre-seed" the new server's DFS directories using Robocopy and then let the DFS Replication take over will be faster.
Here is a similar thread.
DFS Migration Steps - Microsoft Q&A
Best Regards,
Daisy Zhou
