none
DFSR backlog is not decreasing RRS feed

  • Question

  • I have 2 DFS servers on Windows 2012 R2. One at the Prod site and the other at the DR site.

    The Health report shows the status of the replicated folders is Normal. The Get-dfsrbacklog command shows UpdateTime                  from 3 days ago: 11/12/2019

    The DFS Replication Event log on the DR server is showing an error about the DFSR service. The Prod server only has event logs until 11/13 and the DR has logs for today but nothing unusual.

    I ran this command and everything has State = 4.

    wmic /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo get "replicationgroupname,replicatedfoldername,state"

    Friday, November 15, 2019 6:42 PM

All replies

  • The DR server does have an event ID 5014 at 11/14/2019 12:19 AM. It has the code "Error: 9033 (The request was cancelled by a shutdown)"

    This is followed by an event ID 5004 saying The DFS Replication service successfully established an inbound connection with partner Prod.

    Friday, November 15, 2019 6:53 PM
  • The Prod server got Event ID 4312 and 4308 a few minutes ago. There are no other events since 11/13/2019
    Friday, November 15, 2019 7:15 PM
  • Hi,

    Has the DR server been restarted/shutdown, the event ID 5014 indicated this at least, and after some time the DR server has successfully started the DFS Replication service.

    For the event ID 4312:

    If the volume contains a Windows paging file, replication fails and logs DFSR event 4312 in the system event log.

    For the event ID 4308:

    There could be many reasons to this one check the links below if they could give any insight:

    The DFSR Diagnostics Report shows "sharing violations" events in Windows Server even though the files have already been replicated

    Common DFSR Configuration Mistakes and Oversights

    Other than that from the events you've provided it looks like your DFS Replication is functional, you can also create a diagnostics health report and check the overall status and backlog.

    As you probably know the backlog is the number of files waiting to be replicated to the downstream partner. If data on both server are up-to-date, you can try doing a new initial replication so that it will remove the backlog.

    You could also try the following command:
    dfsrdiag backlog /rgname:<replication group name> /rfname:<replication folder name> /sendingmember:<servername> /receivingmember:<servername>

    The above command should show you the file names which are waiting to be replicated.

    In worst case scenario, you can simply delete the replication group (this will not delete any data), and re-create it.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, November 15, 2019 11:06 PM
  • Hi,

    How is your current situation ?

    Just checking in to see if the information provided by Leon was helpful. P

    lease let us know if you would like further assistance.

     

    Best Regards,

    Fan

     


    Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Monday, November 18, 2019 5:51 AM
  •  Hi,

    Was your issue resolved?

    Welcome to share your current situation.

    Please feel free to let us know if you need further assistance.

    Best Regards,

    Fan


    Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Wednesday, November 20, 2019 7:01 AM