Hello.
I am experiencing some strange behavior of DFSR on a new member after DFSR Cloning.
So the situation is next: there are 4 different members for the replication group RG01 - SRV01, SRV02, SRV03 and SRV04.
SRV01 - is the upstream server (users change files on that server), SRV02, SRV03 and SRV04 - are downstream servers for that RG01 group. All servers are configured in a full-mesh topology. All servers are Windows Server 2012 R2. The size of RG01 folder is up to 2TB.
SRV01, SRV02 and SRV03 are fully synced for that RG01 group and all changes are propagated between them immediately. I've performed a DFSR Cloning for the new member SRV04 using this step-by-step guide:
https://blogs.technet.microsoft.com/filecab/2013/08/21/dfs-replication-initial-sync-in-windows-server-2012-r2-attack-of-the-clones/
The DFSR Cloning process went according to the guide.
This is the second time I've performed DFSR Cloning and the first one was successful.
The problem that I am talking about is the slow synchronization of this new member SRV04 with other members.
Below is what I was able to investigate by myself:
1. There are no events in Event Viewer on SRV04 that should be mentioned. There were only lots of 4412 events "The DFS Replication service detected that a file was changed on multiple servers. A conflict resolution algorithm was used to determine the winning file. The losing file was moved to the Conflict and Deleted folder." after adding this SRV04 to the RG01 group which is pretty much normal according to the guide.
2. On other servers there were also lots of events 4412 and events 4304 "The DFS Replication service has been repeatedly prevented from replicating a file due to consistent sharing violations encountered on the file. The service failed to stage a file for replication due to a sharing violation."
3. For some unknown reason I've found almost 21.5k files or folders in DfsrPrivate\PreExisting folder on SRV04 after the cloning process which is so weird because I am 100% sure that these files weren't modified on downstream server during the cloning process.
4. DFSR backlog between SRV01, SRV02 and SRV03 servers are empty. Backlog from SRV01 to SRV04 is always more than 1.5k files. When there are too many changes on upstream server during the daytime the backlog count grows up to 30-40k files and it only grows during that time. It looks like that it is reducing only during the night, when there are almost no activity on upstream server. At night the backlog is reducing to 1.5-2k files (but I've never seen it completely empty in the past 7 days).
5. "dfsrdiag replicationstate" command on SRV04 shows 768 scheduled files in queue (256 files from each of 3 inbound connections) all the time. They are always there. It looks like that filenames in the this output change from time to time, but it is still 768 files scheduled. "dfsrdiag pollad" command doesn't change anything.
6. I can see a lot of entries in C:\Windows\debug\Dfsr0100.log file on SRV04 like these:
20160926 12:58:34.804 11736 MEET 4274 Meet::ProcessUid Uid related found uidRelatedGvsn:{394700C7-AA12-4FC0-A143-3EBFC065AE46}-v34390 updateName:522125 uid:{7A2FC06E-B6EB-4864-8F0E-8CE82B131573}-v61362 gvsn:{2FEE1F47-6FAC-475B-8810-C56DDB83090C}-v70913144 connId:{C16EF5A3-EA5D-49CB-9674-757E9EB9D5EB} csName:RG01
20160926 12:58:34.804 11736 MEET 6356 Meet::LocalDominates Remote version dominates localgvsn:{394700C7-AA12-4FC0-A143-3EBFC065AE46}-v34390 updateName:522125 uid:{7A2FC06E-B6EB-4864-8F0E-8CE82B131573}-v61362 gvsn:{2FEE1F47-6FAC-475B-8810-C56DDB83090C}-v70913144 connId:{C16EF5A3-EA5D-49CB-9674-757E9EB9D5EB} csName:RG01
20160926 12:58:34.804 11736 MEET 6225 Meet::CheckInSync -> WAIT Related record not in sync with file system. relatedRecordUid:{7A2FC06E-B6EB-4864-8F0E-8CE82B131573}-v61362 updateName:522125 uid:{7A2FC06E-B6EB-4864-8F0E-8CE82B131573}-v61362 gvsn:{2FEE1F47-6FAC-475B-8810-C56DDB83090C}-v70913144 connId:{C16EF5A3-EA5D-49CB-9674-757E9EB9D5EB} csName:RG01 csId:{C953FA71-E2FB-40AF-ABEF-0E5A8107FD7F}
I am pretty much sure that sync issues and these entries are interconnected, but I don't know why are they came all the time and what can I do.
7. SRV01, SRV02 and SRV04 are also configured as members for RG02 group on separate drive volumes which works perfectly fine (initial sync was performed to configure them).
That is pretty much all I was able to find during my research. And I need your help to solve this issue because basically I don’t know what should do and what all these messages in Dfsr0100.log mean. Please advice. Thank you in advance.
I am experiencing some strange behavior of DFSR on a new member after DFSR Cloning.
So the situation is next: there are 4 different members for the replication group RG01 - SRV01, SRV02, SRV03 and SRV04.
SRV01 - is the upstream server (users change files on that server), SRV02, SRV03 and SRV04 - are downstream servers for that RG01 group. All servers are configured in a full-mesh topology. All servers are Windows Server 2012 R2. The size of RG01 folder is up to 2TB.
SRV01, SRV02 and SRV03 are fully synced for that RG01 group and all changes are propagated between them immediately. I've performed a DFSR Cloning for the new member SRV04 using this step-by-step guide:
https://blogs.technet.microsoft.com/filecab/2013/08/21/dfs-replication-initial-sync-in-windows-server-2012-r2-attack-of-the-clones/
The DFSR Cloning process went according to the guide.
This is the second time I've performed DFSR Cloning and the first one was successful.
The problem that I am talking about is the slow synchronization of this new member SRV04 with other members.
Below is what I was able to investigate by myself:
1. There are no events in Event Viewer on SRV04 that should be mentioned. There were only lots of 4412 events "The DFS Replication service detected that a file was changed on multiple servers. A conflict resolution algorithm was used to determine the winning file. The losing file was moved to the Conflict and Deleted folder." after adding this SRV04 to the RG01 group which is pretty much normal according to the guide.
2. On other servers there were also lots of events 4412 and events 4304 "The DFS Replication service has been repeatedly prevented from replicating a file due to consistent sharing violations encountered on the file. The service failed to stage a file for replication due to a sharing violation."
3. For some unknown reason I've found almost 21.5k files or folders in DfsrPrivate\PreExisting folder on SRV04 after the cloning process which is so weird because I am 100% sure that these files weren't modified on downstream server during the cloning process.
4. DFSR backlog between SRV01, SRV02 and SRV03 servers are empty. Backlog from SRV01 to SRV04 is always more than 1.5k files. When there are too many changes on upstream server during the daytime the backlog count grows up to 30-40k files and it only grows during that time. It looks like that it is reducing only during the night, when there are almost no activity on upstream server. At night the backlog is reducing to 1.5-2k files (but I've never seen it completely empty in the past 7 days).
5. "dfsrdiag replicationstate" command on SRV04 shows 768 scheduled files in queue (256 files from each of 3 inbound connections) all the time. They are always there. It looks like that filenames in the this output change from time to time, but it is still 768 files scheduled. "dfsrdiag pollad" command doesn't change anything.
6. I can see a lot of entries in C:\Windows\debug\Dfsr0100.log file on SRV04 like these:
20160926 12:58:34.804 11736 MEET 4274 Meet::ProcessUid Uid related found uidRelatedGvsn:{394700C7-AA12-4FC0-A143-3EBFC065AE46}-v34390 updateName:522125 uid:{7A2FC06E-B6EB-4864-8F0E-8CE82B131573}-v61362 gvsn:{2FEE1F47-6FAC-475B-8810-C56DDB83090C}-v70913144 connId:{C16EF5A3-EA5D-49CB-9674-757E9EB9D5EB} csName:RG01
20160926 12:58:34.804 11736 MEET 6356 Meet::LocalDominates Remote version dominates localgvsn:{394700C7-AA12-4FC0-A143-3EBFC065AE46}-v34390 updateName:522125 uid:{7A2FC06E-B6EB-4864-8F0E-8CE82B131573}-v61362 gvsn:{2FEE1F47-6FAC-475B-8810-C56DDB83090C}-v70913144 connId:{C16EF5A3-EA5D-49CB-9674-757E9EB9D5EB} csName:RG01
20160926 12:58:34.804 11736 MEET 6225 Meet::CheckInSync -> WAIT Related record not in sync with file system. relatedRecordUid:{7A2FC06E-B6EB-4864-8F0E-8CE82B131573}-v61362 updateName:522125 uid:{7A2FC06E-B6EB-4864-8F0E-8CE82B131573}-v61362 gvsn:{2FEE1F47-6FAC-475B-8810-C56DDB83090C}-v70913144 connId:{C16EF5A3-EA5D-49CB-9674-757E9EB9D5EB} csName:RG01 csId:{C953FA71-E2FB-40AF-ABEF-0E5A8107FD7F}
I am pretty much sure that sync issues and these entries are interconnected, but I don't know why are they came all the time and what can I do.
7. SRV01, SRV02 and SRV04 are also configured as members for RG02 group on separate drive volumes which works perfectly fine (initial sync was performed to configure them).
That is pretty much all I was able to find during my research. And I need your help to solve this issue because basically I don’t know what should do and what all these messages in Dfsr0100.log mean. Please advice. Thank you in advance.