Issue with DFSR replication

Dino Ingram 1 Reputation point
2020-08-06T21:23:04.98+00:00

I have two servers in a replication group. connection status is enabled, topology is fully connected and verified. I put content in Folder1 on Server A. That content does not replicate to Folder1 on server B. However, if I but content in Folder1 on server B, it DOES replicate to Folder1 on Server A. It is not unilateral across the entire server. However, this is a problem because we are eventually doing away with Server A.

replication report does not show any issues related to this folder's files and shows no backlog.

The contents are not pre-existing, so they are not being excluded for that reason. Where should I look to resolve this.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,638 questions
Windows Server Storage
Windows Server Storage
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Storage: The hardware and software system used to retain data for subsequent retrieval.
643 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Fan Fan 15,326 Reputation points Microsoft Vendor
    2020-08-07T02:44:49.883+00:00

    Hi,
    Thanks for posting here! And the proper advice from Leon.
    Before going further, i would like to confirm the replication group was configured with 2 way and no read only flag was set ,right?
    If possible ,please share a screenshot and hide the private information.
    You created the replication group ]with both the replicated folder empty , and as a test you create files in both the folder,right?
    Was the server B was set to be the primary server when you created the group,?
    I would recommend you check the DFS Replication status firstly with the following command:
    Wmic /namespace:\root\microsoftdfs path dfsrreplicatedfolderinfo get replicationgroupname,replicatedfoldername,state
    0: Uninitialized
    •1: Initialized
    •2: Initial Sync
    •3: Auto Recovery
    •4: Normal
    •5: In Error
    DFSR Troubleshooting: Handy quick tips for your reference:
    https://social.technet.microsoft.com/wiki/contents/articles/31558.dfsr-troubleshooting-handy-quick-tips.aspx

    If there are any updates ,welcome to share here!
    Best Regards,

    1 person found this answer helpful.
    0 comments No comments

  2. Leon Laude 85,726 Reputation points
    2020-08-06T21:46:48.443+00:00

    Hi,

    You have posted in the general Windows Server forum, since your issue is related to DFS-R I suggest you ask over at the dedicated File Services forum over here:
    https://learn.microsoft.com/en-us/answers/topics/windows-server-storage.html

    ----------

    (If the reply was helpful please don't forget to accept as answer, thank you)

    Best regards,
    Leon

    0 comments No comments

  3. Dino Ingram 1 Reputation point
    2020-08-07T12:57:04.883+00:00

    Yes, two way replication. Server A was set to primary. I seeded server B with a a restore from server A BEFORE setting up full-mesh replication. Initial replication from A to B took several days, given the size. It has been working for SEVERAL MONTHS. Folder1 on Server A and Server B bot had content, when I discovered the issue yesterday. The content in Folder1 on Server A was not fully replicated to Folder1 on Server B.

    Replication status is "normal" using the WMIC command. I tested the replication process from a higher level folder. Repeated the same result. Created file on Server A in Folder2, (higher in the directory tree). It DID NOT replicate to Sever B in Folder2.

    However, again, creating a file in SeverB, Folder2, DID replicate to Server A Folder2.

    Screenshot attached. I'm aware of the replication errors. Those errors are due to open files. It is not related to the files that I am working with.
    16400-image.png