Hey,
I have something weird going on in my dfsr logs, some weeks ago one of the members has crashed. I have disabled every replicated folder for that particular member, waited some refreshed the config with dfsrdiag pollad and started to enable folders one by
one, waited to complete initial sync on each of them before enabling the next. It has finished without issues and replication works without problems in all ways. Though i noticed my DFSR log is flooded, here is a small excerpt
* FRS Log Sequence:33803 Index:1000 Computer:xxx TimeZone:Central Europe Daylight Time (GMT+-2:00) Build:[Jul 25 2012 12:47:00 built by: win8_rtm] Enterprise=0 DataCenter=-227758160
* Configuration logLevel:4 maxEntryCount:200000 maxFileCount:1000 logPath:\\.\C:\windows\debug\
+ 6683771, 6683773, 6683774, 6683780, 6683781, 6683785, 6683797,
+ 6683801, 6683803..6683805, 6683813, 6683814, 6683822, 6683824,
+ 6683827, 6683828, 6683837..6683841, 6683846..6683848, 6683855, 6683856,
numbers go on and on like 4000 lines before
+ 6945223, 6945227, 9538615..10079715}
+ {A85F415C-35F9-4A6A-BAB8-7F63D020BB96} |-> { 749763..11369499}
+ {7D601377-569C-43D3-8C7E-9E71255A9EAC} |-> { 532537..1491915, 1492051..1492082,
+ 1492285..1504243, 1526722..1526733, 1526911..1776247, 1777104, 1777105,
+ 1777109..1782858, 1782877, 1782879..1788977, 1791810, 1791811,
+ 1791833..1794598, 1794649..1794690, 1794695, 1794696, 1794702..1797727,
+ 1797733, 1797734, 1798332, 1798343, 1798347..1806484, 1806565,
+ 1806617..1808431, 1812297..1813389, 2511409..3455986, 3462947,
+ 3462952..3561129, 3561189..3561194, 3561200..3563698, 3563730,
+ 3563846..3672916, 3672953, 3672956, 3672965..3672978, 3673005, 3673006,
+ 3673008..3673010, 3673012..3707203, 3707236, 3707237, 3707250,
+ 3707252..5634833}
+ {019202B7-A87B-400E-ACEE-A7A33B71853B} |-> { 20..22656634}
+
20140506 10:18:53.111 6048 INCO 3371 InConnection::ReceiveVvUp Creating new session:4835 requestState:0000007FF26B0050 connId:{37C602A7-47DB-447B-944C-C4E5540867D6} csId:{A6CEB2CC-E3FF-4D2A-9E35-9C7BED476A7D} csName:Quality vvDown:{83C91A2C-F4E8-4C0A-A3C4-42A145EB6F3B}
|-> { 532537..1820469, 1820514,
+ 1820589..1909633, 2972930..4309797, 4686997..4715858, 5829286, 5829287,
+ 5829295, 5829311, 5829314, 5829316, 5829318, 5829319, 5829321, 5829322,
numbers for another 10000 lines
+ 6945223, 6945227, 9538615..10079715}
+ {A85F415C-35F9-4A6A-BAB8-7F63D020BB96} |-> { 749763..11369499}
+ {7D601377-569C-43D3-8C7E-9E71255A9EAC} |-> { 532537..1491915, 1492051..1492082,
+ 1492285..1504243, 1526722..1526733, 1526911..1776247, 1777104, 1777105,
+ 1777109..1782858, 1782877, 1782879..1788977, 1791810, 1791811,
+ 1791833..1794598, 1794649..1794690, 1794695, 1794696, 1794702..1797727,
+ 1797733, 1797734, 1798332, 1798343, 1798347..1806484, 1806565,
+ 1806617..1808431, 1812297..1813389, 2511409..3455986, 3462947,
+ 3462952..3561129, 3561189..3561194, 3561200..3563698, 3563730,
+ 3563846..3672916, 3672953, 3672956, 3672965..3672978, 3673005, 3673006,
+ 3673008..3673010, 3673012..3707203, 3707236, 3707237, 3707250,
+ 3707252..5634833}
+ {019202B7-A87B-400E-ACEE-A7A33B71853B} |-> { 20..22656634}
+
20140506 10:18:53.173 6048 DOWN 2869 AsyncRpcHandler::ProcessReceive Completion. connId:{37C602A7-47DB-447B-944C-C4E5540867D6} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:0000007F9B7BA320
20140506 10:18:48.790 5728 INCO 3364 InConnection::ReceiveVvUp Received VvUp connId:{27F91321-280E-4BA8-ABD8-EBC6ED3C99AB} csId:{A6CEB2CC-E3FF-4D2A-9E35-9C7BED476A7D} csName:Quality vvUp:{83C91A2C-F4E8-4C0A-A3C4-42A145EB6F3B} |-> { 532537..1820469,
1820514,
+ 1820589..1909633, 2972930..4309797, 4686997..4715858, 5829286, 5829287,
+ 5829295, 5829311, 5829314, 5829316, 5829318, 5829319, 5829321, 5829322,
In a single logfile there are only a few entries for normal file replication all other is a bunch of VvUp numbers (database version vector?)
Any ideas what's going on here, other than that DFSR works flawless replication is immediate, Eventlog, health and propagation logs show no problem (other than preexisting content taking up space on the rebuilt server).
I have tried to stop DFSR for some time on the server that crashed but logs keep getting flooded, so I'm not even sure at this point it has anything to do with the crashed member. There are 3 members currently, all kind of windows versions, 2008R2/2012/2012R2 in full mesh topology.