3

I have a DFS Namespace currently in auto-recovery due to an unexpected server crash. There's about 600GB of data and it's consisting of small files for the most part.

It's been in auto-recovery for over 72 hours now.

I can run Get-WmiObject -computername computername -Namespace "root\MicrosoftDFS" -Query "SELECT * FROM DfsrReplicatedFolderInfo"

To confirm that it is in State 3, which correspond to being in auto-recovery mode and also confirm that there's enough CPU, network and disk usage by the dsfrs.exe to know that it's doing "something".

Is there any way to get some sort of idea as to when it might complete and how much work there's still left to do either in time or a percentage of completion?

jfrobishow
  • 71

2 Answers2

2

Have a look at the DFSR debug log at %windir%\debug\DFSRn.log (Where n will most likely be 01000, depending on how long DFSR has been running and what your maximum log files are configured to be. In any case it will be the highest number and the only file not GZipped.)

If recovery is still at the first stage, you will see many entries that say

2312 JRWP   763 JournalWrapTask::MarkTopDown LDB Updating ID Record:

after the timestamp.

If it's in the second stage, you will see

3936 DIRW  1986 DirWalkerTask::WalkImmediateChildren Validating:

followed by

3936 DIRW  2713 DirWalkerTask::Unmark LDB Updating ID Record:

As for how far it is through each stage, I don't think Microsoft has implemented any way of viewing this.

A J Wilson
  • 338
0

I believe that you are asking information about the DFS Replication backlog. If so, you can monitor it via dfsrdiag command. For additional information, I suggest checking the following serverfault question: How to monitor DFSR backlog more efficiently than dfsrdiag

Once you are able to retrieve DFS-R backlog counters, you will be able to verify how fast they are decreasing and estimate how long they will take to reach zero.

Anderson Medeiros Gomes
  • 2,537