Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Inbound changes do not replicate during initial sync to Read-Only DFSR member

Inbound changes do not replicate during initial sync to Read-Only DFSR member

View products that this article applies to.

Symptoms

After pre-seeding data on a Read Only DFSR member, you may notice that some files are out of sync on the Read Only member after initial sync has completed. This issue will only affect files that have been modified after the data has been pre-seeded, and before the initial sync process has completed.

When examining impacted files or folders on the Read Only member, you may notice that the files appear older and/or different in content/size.

Looking at the dfsr debug logs (%systemroot%\debug\dfsr0000*.log) on downstream (read only) member, you will see the following entries during initial sync for files that are newer on upstream partner:

20121109 17:05:57.683 4072 MEET  4274 Meet::ProcessUid Uid related found uidRelatedGvsn:{C5B5CBC3-EAFF-4C3B-9F5F-BC5C27EC44A8}-v115 updateName:123.txt uid:{C5B5CBC3-EAFF-4C3B-9F5F-BC5C27EC44A8}-v113 gvsn:{C5B5CBC3-EAFF-4C3B-9F5F-BC5C27EC44A8}-v115 connId:{9B55B14E-8254-4D00-97C5-4264D07946AE} csName:MyRG
20121109 17:05:57.683 4072 MEET  4406 Meet::ProcessUid -> DONE Local version dominates localGvsn:{C5B5CBC3-EAFF-4C3B-9F5F-BC5C27EC44A8}-v115 updateName:123.txt uid:{C5B5CBC3-EAFF-4C3B-9F5F-BC5C27EC44A8}-v113 gvsn:{C5B5CBC3-EAFF-4C3B-9F5F-BC5C27EC44A8}-v115 connId:{9B55B14E-8254-4D00-97C5-4264D07946AE} csName:MyRG csId:{2A4DAFDB-8328-470E-8150-F75F787E48B2}
20121109 17:05:57.683 4072 MEET  1843 Meet::InstallStep Done installing file updateName:123.txt uid:{C5B5CBC3-EAFF-4C3B-9F5F-BC5C27EC44A8}-v113 gvsn:{C5B5CBC3-EAFF-4C3B-9F5F-BC5C27EC44A8}-v115 connId:{9B55B14E-8254-4D00-97C5-4264D07946AE} csName:MyRG

↑ Back to the top

Cause

During conflict resolution algorithm, DFSR incorrectly identifies the local Read Only pre-seeded version of the file as the winning copy. As a result, the up to date version of the file is not copied down.

↑ Back to the top

Resolution

You could use the following methods to prevent the issue from occurring:

Method 1
Allow for initial sync to complete before making any changes to files

Method 2
Do not pre-seed data on RO, allow the data to replicate across.

↑ Back to the top

Keywords: kb

↑ Back to the top

Article Info
Article ID : 2783674
Revision : 1
Created on : 1/7/2017
Published on : 1/24/2013
Exists online : False
Views : 286