Dear all,
We had a major grid-wide power out about 3 weeks ago. It outlasted our UPS and was also at 3am so the servers on site went down hard.
After this we brought the servers back up and DFSR appeared to be running with clean event logs.
I got a single report from a peripatetic user that her files didn't appear at a separate site and run a file propagation test which failed. Checking the server's diagnostic reports I discovered a 400k (est) backlog from the site. I brought DFSR down cleanly, brought it back up and this time in the event log it recorded a 'dirty shutdown' error and attempted an automatic repair/rebuild. Did work, no files shifted.
I ended up running some manual commands to intervene:
wmic /namespace:\\root\microsoftdfs path dfsrmachineconfig set StopReplicationOnAutoRecovery=FALSE
AND
wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="<volume-GUID>" call ResumeReplication
Which did result in DFSR coming back up and process some files after about 3 days. But it seems to run in batches of about 50-75k and then 'go back to sleep'. It's very slow and is causing both a technical and political nightmare for me.
Can someone please offer some advice or technical help please? This is killing us.
Many thanks,
William