• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 367
  • Last Modified:

DFS Replication issues

I was replicating data between two 2008 servers, one of those servers just became a 2012 server. Before the OS upgrade, I did remove the member that was being upgraded.
I then readded the new member to the existing replication and now all data is stuck in the
DfsrPreExisting folder and doesnt seem to replicating to the new upgraded 2012 server.
First question is whY, second being how do I fix this?
Is there a different process to accomplish this other than what I have done?

1 Solution
Radhakrishnan RSenior Technical LeadCommented:

Could you have a look at this section "Before you can deploy DFS Replication, you must configure your servers as follows" from this link http://social.technet.microsoft.com/Forums/windowsserver/en-US/8b660aa6-1577-4799-93f2-28411eea42da/compatibilityinteroperability-between-windows-server-2012-dfs?forum=winserverfiles

Hope this helps
progjmAuthor Commented:
I have the replication working on another folder between these two servers with no issues. The only difference it was a new DFS member configuration rather then just adding a member to an existing folder setup
progjmAuthor Commented:
Was able to locate a script to move the files back into the original folder from the PreExisting. But I still dont understand what happened? They relocated into the PreExisting folder and never transferred to the new server folder
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Look at the replication topology, and whether there are two connections
A to B and B to a.
Use DFS management to generate the report on the replication group, you might be missing something.
Is 2012 server got restarted unexpectedly any time ?

In that case replication will not start automatically, this is new feature with 2012
In 2008 R2 this behaviour is implemented with hotfix, otherwise replication will resume automatically upon unexpected reboot.

Please try below

Run commands in below post to resume replication


Also ensure that you have run below command on 2012 server
wmic /namespace:\\root\microsoftdfs path dfsrmachineconfig set StopReplicationOnAutoRecovery=FALSE

Then delete existing replicated folder from 2012 server, reboot it once and try establishing new replica

Did both servers have the data when you added the win2k12 as a replication member with the win2k8 as the master(in this scenario, the master replica member means it is the authoritative source of what data exists in the directory)?
progjmAuthor Commented:
I will take a look at that link.
There was no data in the replicated folder on the new server, only the original.
You said you added the new server into the existing replication group.  The only possible reason the original server's data is moved to existing would be when the other system is configured as the master/authoritative on the data.

Test it out. Create a folder on system A and add a file there. Then create a replication group with server B as the master and add server A and that folder as another member and you should see the file on server A moved to the existing folder as happened to your setup.
progjmAuthor Commented:
ahh that would make sense, so it was looking at itself and moved the items to pre-existing?
I had not tried this myself but it appears Microsoft does not recommend mixing 2008 and 2012 DFS clients...


Also, I am not sure if this is the firs 2012 servers in your environment but have you already extended your schema to include the 2012 Schema extensions?

progjmAuthor Commented:
Thank you for the help guys!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now