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 do not appear to ever replicate for unknown reasons.

 

(tempfilesupstream - Dfsr00008 - 2008.log)

 

These are two Windows Server 2008 servers called 2008x86SRV10 and 2008x86SRV11 in the contoso.com domain. The log is from 2008x86SRV10 where the file is created. The files are realtemp.doc (which has temp attribute set) and pseudotemp.tmp (which is filtered by DFSR).

 

<Upstream> 20080908 13:43:09.067 3856 USNC  1244 UsnConsumer::ProcessUsnRecord Skipping USN_RECORD with FILE_ATTRIBUTE_TEMPORARY flag: ß the USN journal update process will mark when files are filtered for any reason. In this case the file is structurally temporary due to an attribute.

+       USN_RECORD:

+       RecordLength:        88

+       MajorVersion:        2

+       MinorVersion:        0

+       FileRefNumber:       0x80000000000B6

+       ParentFileRefNumber: 0x70000000000B3

+       USN:                 0x268e058

+       TimeStamp:           20080908 13:43:09.052 Pacific Standard Time

+       Reason:              Close Security Change

+       SourceInfo:          0x0

+       SecurityId:          0x0

+       FileAttributes:      0x120 ß 0x20 (file) & 0x100 (temporary)

+       FileNameLength:      24

+       FileNameOffset:      60

+       FileName:            realtemp.doc ß the file called ‘realtemp.doc’

+      

<Upstream> 20080908 13:43:09.083 3856 USNC  1294 UsnConsumer::ProcessUsnRecord Filtered USN_RECORD: ß In this case the USN update is filtered because the file has a name matching the DFSR file filters (by default, ~*, *tmp, *.bak)

+       USN_RECORD:

+       RecordLength:        88

+       MajorVersion:        2

+       MinorVersion:        0

+       FileRefNumber:       0x50000000000B4

+       ParentFileRefNumber: 0x70000000000B3

+       USN:                 0x268e160

+       TimeStamp:           20080908 13:43:09.083 Pacific Standard Time

+       Reason:              Close Rename New Name

+       SourceInfo:          0x0

+       SecurityId:          0x0

+       FileAttributes:      0x20 ß file, not a folder

+       FileNameLength:      28

+       FileNameOffset:      60

+       FileName:            pseudotemp.tmp ß file ends with extension of TMP and is filtered


Understanding DFSR debug logging (Part 1: Logging Levels, Log Format, GUID’s)
Understanding DFSR debug logging (Part 2: Nested Fields, Module ID's)
Understanding DFSR debug logging (Part 3: The Log Scenario Format, File Added to Replicated Folder on Windows Server 2008)
Understanding DFSR debug logging (Part 4: A Very Small File Added to Replicated Folder on Windows Server 2008)
Understanding DFSR debug logging (Part 5: File Modified on Windows Server 2003 R2)
Understanding DFSR debug logging (Part 6: Microsoft Office Word 97-2003 File Modified on Windows Server 2008)
Understanding DFSR debug logging (Part 7: Microsoft Office Word 2007 File Modified on Windows Server 2008)
Understanding DFSR debug logging (Part 8: File Deleted from Windows Server 2003 R2)
Understanding DFSR debug logging (Part 9: File is Renamed on Windows Server 2003 R2)
Understanding DFSR debug logging (Part 10: File Conflicted between two Windows Server 2008)
Understanding DFSR debug logging (Part 11: Directory created on Windows Server 2003 R2)
Understanding DFSR debug logging (Part 12: Domain Controller Bind and Config Polling on Windows Server 2008)
Understanding DFSR debug logging (part 13: A New Replication Group and Replicated Folder between two Windows Server 2008 members)
Understanding DFSR debug logging (Part 14: A sharing violation due to a file locked upstream between two Windows Server 2008)
Understanding DFSR debug logging (Part 15: Pre-Seeded Data Usage during Initial Sync)
Understanding DFSR debug logging (Part 16: File modification with RDC in very granular detail (uses debug severity 5))
Understanding DFSR debug logging (Part 17: Replication failing because of blocked RPC ports (uses debug severity 5))
Understanding DFSR debug logging (Part 18: LDAP queries failing due to network (uses debug severity 5))
Understanding DFSR debug logging (Part 19: File Blocked Inbound by a File Screen Filter Driver (uses debug severity 5))
Understanding DFSR debug logging (Part 20: Skipped temporary and filtered files (uses debug severity 5))
Understanding DFSR debug logging (Part 21: File replication performance from throttling (uses debug severity 5))
 

-          Ned Pyle