When you use Distributed File System Replication (DFSR), all files in a replicated folder are re-replicated between servers even though the file contents are unchanged. This behavior may occur in a "ping pong" manner between servers continuously. When you examine the files closely, you find the following conditions are true:
- The files are not visibly changed.
- The "Last Modified" date was not changed.
- Files are moving to the DFSR ConflictedAndDeleted folder.
- Users may notice that their recent file changes are being removed, and the file seems to be an older version.
Additionally, the DFSR debug logs show entries that resemble the following for each replicated file:
20090629 19:12:57.725 2532 USNC 2453 UsnConsumer::UpdateIdRecord ID record updated
+ RecordLength: 96
+ MajorVersion: 2
+ MinorVersion: 0
+ FileRefNumber: 0xF000000005E74
+ ParentFileRefNumber: 0x5000000000127
+ USN: 0x2ba89c0
+ TimeStamp: 20090629 19:12:57.709 Eastern Standard Time
+ Reason: Basic Info Change Close Named Data Extend Stream Change
+ SourceInfo: 0x0
+ SecurityId: 0x0
+ FileAttributes: 0x20
+ FileNameLength: 32
+ FileNameOffset: 60
+ FileName: samplefile.rtf
The Reason text in this example includes "Stream Change." On the next update, the Reason text may change to "Data Truncation."
Windows Server 2008 R2 includes a new File Server Resource Manager (FSRM) component that is called "Classification Management." This component is used to select files that are based on rules in order to perform scheduled tasks. As part of its typical operation, Classification Management writes alternate data streams to files. These will cause the file hash to change and DFSR to re-replicate the file unnecessarily.If scheduled Classification rules are used on multiple servers, it may cause the "ping pong" effect in which each server replicates all files in each direction.
This behavior is by design.
We do not recommend that you use FSRM Classification rules with DFSR replicated folders.
If you use FSRM Classification Rules with DFSR replicated folders, we recommend that you configure the rules and run them before you configure DFSR. We also recommend that you only apply the rules to one server and not multiple servers. Scheduled FSRM rules should not run during regular working hours. FSRM Classification Rules should not be applied to latent DFSR servers where incoming changes are not yet replicated because in this case user file changes may be lost.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about what is new in File Server Resource Manager in Windows Server 2008 R2, please visit the following Microsoft TechNet Web site:
For more information about Distributed File System Replication, visit the following Microsoft TechNet Web site, and see the "Frequently Asked Questions" topic: