DFS-R WMI duplicate results - Wmic /namespace:\root\microsoftdfs path dfsrreplicatedfolderinfo

Question

_{Wednesday, September 28, 2016 7:22 AM}

Hello everyone,

I am facing a very weird issue with DFS-R. Recently I had to recreate two Replication Groups (Data Collection) in order to restore file replication after a disaster with one of the servers. Everything went well during the whole process and both servers are already in sync with each other. However, when I run a WMI query (Wmic /namespace:\root\microsoftdfs path dfsrreplicatedfolderinfo get replicationgroupname,replicatedfoldername,state) to see the status of the Replication Groups, I see duplicate values for a given RG with a status of '0' (Uninitialized). I have already checked everything I could... If I open the DFS Management console I don't see any duplicate Replication Groups there; the contents of the XML configuration files under "C:\System Volume Information\DFSR" & "E:\System Volume Information\DFSR" - being the latter one where the replicated data resides - are OK (no duplicate entries); and on registry (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\DFSR), I also only see what's really configured (again, no duplicate values).

I strongly suspect it's some sort of left over on the WMI repository that was not handled properly by DFS-R when the Replication Groups were re-created, but as I've never had to delete spefic instances from WMI, I am wondering whether someone out there has already faced the same issue or has any clues on how to get rid of these disturbing duplicate results being returned on "Wmic /namespace:\root\microsoftdfs path dfsrreplicatedfolderinfo get replicationgroupname,replicatedfoldername,state".

Just wanted to emphasize that replication is working fine between the two boxes (in both directions), the only issue being faced here is the duplicate thing.

Thanks in advance! :-)

All replies (8)

_{Monday, October 10, 2016 3:39 PM ✅Answered}

I managed to figure out what was wrong by myself. As it turns out, those duplicate entries being returned upon "Wmic /namespace:\root\microsoftdfs path dfsrreplicatedfolderinfo get replicationgroupname,replicatedfoldername,state" were due to leftovers in the folder dedicated to the Staging area. When the Replication Groups were recreated, the contents of the Staging folder were not manually deleted and DFS-R didn’t manage to handle that very well. In order to resolve it, I created a new folder for Staging, pointed the DFS Replication Group within DFS Management Console to the new folder, gave it over 12 hours (I was really precautious here due to the size and criticality of the data in scope) to ensure DFS-R had fully recognized the new configuration, stopped DFS Replication service, deleted the old Staging folder and, finally, restarted DFS Replication service. Now everything is back on track and looking good. :-)

Wellington Ozorio

_{Wednesday, September 28, 2016 8:21 AM}

Hi Wellington Ozorio,

Thanks for your post.

If possible, could you please post the screenshot for your issue?

You may you have seen the duplicate values for a given RG with the  WMI  commands. But in the DFS Management console, there's no such results, right?

Is there any message in the event viewer?

As far as I know,  DFS Replication group information saves in the AD metadata. DFS namespace server information saves in the remoteServerName attributes which is under the CN=Dfs_Configuration in the Active Directory object.

You may use ADSIedit.msc to check the object of on the DCs to remove the Phantom DFS namespace information. If there's no duplicated RG, in theory, the replication group shouldn't be duplicated.

a. Open ADSIedit.msc.

b. Connect to Default Naming Context (the domain name)

c. Expand and locate the container, which show the DFS root information

Best Regards,

Mary

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Thursday, September 29, 2016 9:17 AM}

Hi Mary,

Thanks for your reply.

Here is the screenshot of the issue:

As can be seen above, the last two lines (in state 0) are a duplication of the second line (in state 4).

On DFS Management console, I do not see the duplicate Replication Groups. Even if I run "dfsradmin rg list", I do not see any duplication (see screenshot below). There is no error on EventViewer, and nothing evident on DFS-R debug logs which could explain the issue.

I did not mention this in my initial question, but I had also checked the configurations of the Replication Groups in question on AD through ADSI Edit, and there is no duplicate instance there either. Anyways, below is also available a screenshot of ADSI Edit.

Please note that I only see duplicate Replication Groups (using the WMI query) on one of the servers. That's why I believe there is some sort of left over on the WMI repository of the problematic server.

Best regards,

Wellington

Wellington Ozorio

_{Friday, September 30, 2016 2:01 AM}

Hi Wellington,

I could only say in theory, if your dfs replication environment is healthy. WMI info should be correct.

But according to your description, that seems to be as you said.

And if possible, could you please delete the  problematic  dfs replication folder, then check the WMI info, still shows?

Best Regards,

Mary

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Friday, September 30, 2016 2:46 PM}

Hi Mary,

I cannot delete the Replication Group again, because now it's working fine (files are being replicated back and forth). It's a production environment with nearly 10 million files and both servers are communicating with each other over a low speed WAN link (MPLS). If I delete the Replication Group, it will take at least 2 weeks for replication to catch up (customer rely on DFS-R to have files backed up on the hub server) and I am not sure it will work, since the RG in question was recently re-created.

Any other suggestions?

BR,

Wellington

Wellington Ozorio

_{Monday, October 3, 2016 1:23 AM}

Hi Wellington,

Thanks for your reply.

I'm afraid you may need to  consider to contact Microsoft Customer Support Services (CSS) so that a dedicated Support Professional can help you on this issue. Your issue seems to be strange and couldn't find the good direction to do the troubleshoot. 
Appreciate your support and understanding
 To obtain the phone numbers for specific technology request please take a look at the web site listed below.
 https://www.microsoft.com/en-us/worldwide.aspx

Best Regards,

Mary

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Tuesday, October 11, 2016 1:16 AM}

Hi Wellington,

Glad that you figure out finally by yourself and many thanks that you sharing your solution for anyone else in similar scenario to have a reference.

Best Regards,

Mary 

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Friday, October 27, 2017 4:32 PM}

Seeing the same thing.  Can you walk though in a little more detail what you did to fix.  Specifically moving the staging area etc?