When you have issue with DFS replication in Read-Only mode.
Following are the steps that we followed to fix the no replication issue.
First check if both the nodes Primary and read-only are healthy however in this scenario Primary server had a Dirty shutdown issue and we were getting event 2213 for Volume: X
Since we had to ensure that Primary server: XXX becomes primary we had to disable the membership of Secondary server.
Once the Primary server was recovered from the error state using the wmic command provided in the 2213 event itself then we enabled the membership of the Secondary server. Also created services time out registry to ensure that DFSR service gets more time when we do shutdown or restart of the server or the DFSR service.
Also we increased the value of WaittoKillservicestimeout registry.
Disabled offloads on the srevers using the below commands:
Disabled offload using commands on both the servers.
Pass these commands on both servers:
netsh int tcp set global chimney=disabled netsh int tcp set global rss=disabled netsh int ip set global taskoffload=disabled netsh int tcp set global autotuninglevel=disabled netsh int tcp set global congestionprovider=none netsh int tcp set global ecncapability=disabled netsh int tcp set global timestamps=disabled netsh advf set allp state off
created performance registry keys as both the servers are 2008 R2
Understanding DFSR Dirty (Unexpected) Shutdown Recovery: http://blogs.technet.com/b/filecab/archive/2012/07/23/understanding-dfsr-dirty-unexpected-shutdown-recovery.aspx
once we got state 4 on the Primary server then we enabled the secondary RO server membership.
Since the Primary server has lots of data and users are also making change at the same time so Secondary server will take lot of time to complete the sync.