troubleshooting Question

DFSR comparing files but not replicating them

Avatar of NateWilliams
NateWilliamsFlag for United States of America asked on
Windows Server 2003
3 Comments1 Solution1201 ViewsLast Modified:
Hello all,

I have a rather unique issue here.  Firstly, my DFSR design.

I have a full mesh topology with 2 servers and 2 different replication groups.  We'll call them server1, server2, group1, and group2

Secondly, my issue,

Server1 Group1 replicates successfully
Server2 Group1 replicates successfully
Server1 Group 2 replicates sucessfully
Server2 Group 2 will not replicate.

In looking at the debug logs on Server2, I can change a file and it will compare to Server1 to see which one "wins". This is as far as it goes.  It does not copy.  There are no errors in the event log nor the debug log.  It appears to just simply sits in the backlog waiting to copy.  It was functioning normally this morning and stopped mid-day.

In looking at the debug logs on Server1, the file is not mentioned anywhere.

This has been running without issue for months so there shouldn't be a configuration issue.

I will be restarting server2 when I can get a small windows of downtime, but it will be a while.  I currently have about 12K files backlogged at the moment.  

Attached snipped is from the dfsr log file.

Any help is appreciated.  Thanks!

--Nate
##ADDING THE FILE TO THE REPLICATED FOLDER##

20100330 17:22:57.209  400 LDBX  3548 Ldb::Insert Inserting idRecord:
+	fid               0x13000000074EEB
+	usn               0x208f20000
+	uidVisible        0
+	filtered          0
+	journalWrapped    0
+	slowRecoverCheck  0
+	pendingTombstone  0
+	recUpdateTime     16010101 00:00:00.000 GMT
+	present           1
+	nameConflict      0
+	attributes        0x20
+	gvsn              {D9809A24-8DBC-4127-944C-05352E2DDB7F}-v1388548
+	uid               {D9809A24-8DBC-4127-944C-05352E2DDB7F}-v1388548
+	parent            {FBF35F2F-C712-4083-86A3-4F37D2375DD2}-v1
+	fence             16010101 00:00:00.000 
+	clock             20100330 22:22:57.209
+	createTime        20100330 22:22:57.209 GMT
+	csId              {FBF35F2F-C712-4083-86A3-4F37D2375DD2}
+	hash              00000000-00000000-00000000-00000000
+	similarity        00000000-00000000-00000000-00000000
+	name              eetest2.txt
+	
20100330 17:22:57.209  400 USNC  2448 UsnConsumer::CreateNewRecord ID record created from USN_RECORD:
+	USN_RECORD:
+	RecordLength:        88
+	MajorVersion:        2
+	MinorVersion:        0
+	FileRefNumber:       0x13000000074eeb
+	ParentFileRefNumber: 0x100000000001e
+	USN:                 0x208f20000
+	TimeStamp:           20100330 17:22:57.209 Central Standard Time
+	Reason:              Basic Info Change Close File Create 
+	SourceInfo:          0x0
+	SecurityId:          0x47f
+	FileAttributes:      0x20
+	FileNameLength:      22
+	FileNameOffset:      60
+	FileName:            eetest2.txt
+

##ALTERING THE CONTENTS TO TRIGGER COMPARISON##
20100330 17:30:08.319  400 LDBX  3665 Ldb::Update Updating idRecord:
+	fid               0x13000000074EEB
+	usn               0x20901d2a8
+	uidVisible        0
+	filtered          0
+	journalWrapped    0
+	slowRecoverCheck  0
+	pendingTombstone  0
+	recUpdateTime     20100330 22:30:05.084 GMT
+	present           1
+	nameConflict      0
+	attributes        0x20
+	gvsn              {D9809A24-8DBC-4127-944C-05352E2DDB7F}-v1388578
+	uid               {D9809A24-8DBC-4127-944C-05352E2DDB7F}-v1388548
+	parent            {FBF35F2F-C712-4083-86A3-4F37D2375DD2}-v1
+	fence             16010101 00:00:00.000 
+	clock             20100330 22:30:08.319
+	createTime        20100330 22:22:57.209 GMT
+	csId              {FBF35F2F-C712-4083-86A3-4F37D2375DD2}
+	hash              00000000-00000000-00000000-00000000
+	similarity        00000000-00000000-00000000-00000000
+	name              eetest2.txt
+	
20100330 17:30:08.319  400 USNC  2202 UsnConsumer::UpdateIdRecord ID record updated from USN_RECORD:
+	USN_RECORD:
+	RecordLength:        88
+	MajorVersion:        2
+	MinorVersion:        0
+	FileRefNumber:       0x13000000074eeb
+	ParentFileRefNumber: 0x100000000001e
+	USN:                 0x20901d2a8
+	TimeStamp:           20100330 17:30:08.319 Central Standard Time
+	Reason:              Close Data Extend 
+	SourceInfo:          0x0
+	SecurityId:          0x47f
+	FileAttributes:      0x20
+	FileNameLength:      22
+	FileNameOffset:      60
+	FileName:            eetest2.txt
+

Open in new window

ASKER CERTIFIED SOLUTION
Justin Owens
ITIL Problem Manager

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 3 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 3 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros