The Storage Team Blog about file services and storage features in Windows and Windows Server.
A customer recently contacted us about how to recover from data corruption on a volume where replicated content was stored. He writes: “We have recently experienced data corruption on our hub server. This data was on a large volume, and I want to avoid a full restore. The data on the volume is collected from a few or our regional servers using DFS Replication. I want to use DFS Replication to ensure that all of the data on the hub server is updated with the “good” data from a regional server. Can I force a sync on a replicated folder, with a designated primary member, without deleting and recreating the replicated folder?”
Our DFS guru Ram Natarajan provided the following response to the customer:
There are 3 different ways that I can think of to do what you intend:
The following wmic command shows an example of how to invoke this method:
wmic /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo call Fence "e:\\cs1",TRUE,1
Where e:\cs1 is the replicated folder root (note that you have to escape ‘\’) and 1 is the fence value “Initial Sync” (loses to partner on conflicts).
The valid fence values that you can use with the above call are:
For all the above three methods, the prerequisite is to prevent DFSR on the affected member from replicating out files inadvertently with any of the partners while the recovery procedure is carried out. One safe and easy way of doing this would be to configure DFSR to replicate on a static port, and then block that port on the firewall on that machine – this will prevent DFSR on that machine from serving out any files while you complete the recovery procedure.