Browse by Tags
All Tags »
DFSR Debug Logging (RSS)
Ned here. A short while ago I got an excellent question from one of our readers via our email form . To paraphrase: “We are designing our new DFS Replication topology for data collection of remote backups. We plan on replicating this data during off hours.
Read More...
Ned again. As promised, here is the complete list of links for the recent 21-part DFSR Debug Log analysis series as well as downloadable versions of the series in Word 2007, Word 2003-97, XPS, and PDF formats. I have also included the debug logs I referenced
Read More...
In this final scenario we will see a file being replicated successfully, but where the replication appears to be very slow. A bandwidth throttle has been configured within the DFSR replication group schedule to restrict traffic to 128Kbps. This is useful
Read More...
In this scenario we will see a pair of files being created on an upstream server. One of the files is marked with the TEMPORARY attribute and one has an extension of TMP which is being filtered by DFSR. This will show the common scenarios of files which
Read More...
In this scenario we will see an attempted file replication. The downstream partner is running the File Server Resource Manager role with file screens configured and these screens are not matched to the DFSR file filters. The debug log has been set to
Read More...
In this scenario we will see a DFSR server attempt to contact its DC through LDAP to read the current replication topology. LDAP lookups are being blocked by ‘firewall/network/DC down’ so there are no responses. ( ldapblocked - Dfsr00008 - 2008.log )
Read More...
In this scenario we will see a file created on the upstream server and attempted replication with its downstream partner. RPC traffic is being blocked between the machines by an incorrectly configured firewall. This is a common scenario and basic understanding
Read More...
In this scenario we will see a file modified and how that change is replicated between servers, specifically in regards to RDC similarity usage. The debug log has been set to severity 5 for deeper details than usual. This is useful to understand how efficient
Read More...
In this scenario we will see a new replication group and replicated folder created, where data has been pre-seeded (i.e. pre-staged) on both servers. This is a common scenario, where data has existed on a few servers and been kept in sync through other
Read More...
In this scenario we will see file that is locked by an application, preventing replication from occurring. The upstream replicated folder will contain a file that does not yet exist on the downstream member. This is useful to understand as one of the
Read More...
In this scenario we will see a new Replication Group and Replicated Folder created. The upstream replicated folder will contain a few files that do not yet exist on the downstream member. This is useful to understand as one of the most common troubleshooting
Read More...
In this log we will see the DFSR service being started and follow the process of initialization up to the point where the service is fully functional. This is useful to understand in order to troubleshoot issues where problems within Active Directory,
Read More...
In this scenario we will see a folder added and how that change is replicated between servers. This is useful to understand in order to troubleshoot issues where problems within the USN journal, the DFSR JET database, and the network (including RPC) are
Read More...
In this scenario we will see a file that has been changed on two servers in between replication convergence and how that conflict resolution is replicated between servers. This is useful to understand in order to troubleshoot issues (or perception of
Read More...
In this scenario we will see a file renamed and how that change is replicated between servers. This is useful to understand in order to troubleshoot issues where problems within the USN journal, the DFSR JET database, and the network (including RPC) are
Read More...
