Link to home
Create AccountLog in
Avatar of BluecubeTechnology
BluecubeTechnology

asked on

DFS-R Backlog file list

I have a problem with DFS Replication. I can see that our users have dumped a whole heap of files (approx. 12,000) into a couple of replicated folders and the system is backlogging these files. The backlog is not growing very quickly which suggests that DFS is still working to a degree. However when I run a DFS Backlog report it only gives me the first 100 files. Ideally I want get a list of *all* the backlogged files as I want to move them to a non-DFS replicated folder and then re-introduce them to replication slowly.

Anybody know how to get a complete list of backlogged files?
SOLUTION
Avatar of MarkieS
MarkieS
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of BluecubeTechnology
BluecubeTechnology

ASKER

Thanks for the reply, the TRACE32.exe has been helpful in getting at the logs.

I've increased the staging area size to 10GB for the affected folders but this doesn't appear to have got things moving. I've also checked the bandwidth between the office and datacentre and I'm not getting anything like the amount of traffic that would suggest the line is saturated (it's a 40MB EFM circuit).

This is an extract from the live log:

+	present                         1
+	nameConflict                    0
+	attributes                      0x20
+	ghostedHeader                   0
+	data                            0
+	gvsn                            {2909EAD2-DA4D-4F28-9CB2-7028EB48070D}-v2014664
+	uid                             {2909EAD2-DA4D-4F28-9CB2-7028EB48070D}-v2014664
+	parent                          {2909EAD2-DA4D-4F28-9CB2-7028EB48070D}-v2003432
+	fence                           Default (3)
+	clockDecrementedInDirtyShutdown 0
+	clock                           20131121 16:02:37.218 GMT (0x1cee6d318ff22d9)
+	createTime                      20131121 11:06:57.230 GMT
+	csId                            {4D219D40-1196-4B26-9CD6-41DFC0B14D54}
+	hash                            00000000-00000000-00000000-00000000
+	similarity                      00000000-00000000-00000000-00000000
+	name                            3109001 - <File_Name>.xlsx
+	 Error:
+	[Error:9027(0x2343) RpcFinalizeContext downstreamtransport.cpp:1117 25016 C A failure was reported by the remote partner]
+	[Error:9027(0x2343) DownstreamTransport::RdcGet downstreamtransport.cpp:5269 25016 C A failure was reported by the remote partner]
+	[Error:9024(0x2340) DownstreamTransport::RdcGet downstreamtransport.cpp:5269 25016 C The file meta data is not synchronized with the file system]
20131218 11:28:39.602 25016 INCO  6582 InConnection::LogTransferActivity Failed to receive RAWGET uid:{2909EAD2-DA4D-4F28-9CB2-7028EB48070D}-v2014664 gvsn:{2909EAD2-DA4D-4F28-9CB2-7028EB48070D}-v2014664 fileName:3109001 - Coca-cola - Supreme Control.xlsx connId:{B8966922-E91B-4B56-807F-CC46EA43CA52} csId:{4D219D40-1196-4B26-9CD6-41DFC0B14D54} stagedSize:0 Error:
+	[Error:9027(0x2343) DownstreamTransport::RdcGet downstreamtransport.cpp:5346 25016 C A failure was reported by the remote partner]
+	[Error:9027(0x2343) RpcFinalizeContext downstreamtransport.cpp:1117 25016 C A failure was reported by the remote partner]
+	[Error:9027(0x2343) DownstreamTransport::RdcGet downstreamtransport.cpp:5269 25016 C A failure was reported by the remote partner]
+	[Error:9024(0x2340) DownstreamTransport::RdcGet downstreamtransport.cpp:5269 25016 C The file meta data is not synchronized with the file system]
20131218 11:28:39.602 25016 INCO  2831 InConnection::ProcessErrorStatus (Ignored) Remote error connId:{B8966922-E91B-4B56-807F-CC46EA43CA52} state:CONNECTED Error:
+	[Error:9027(0x2343) DownstreamTransport::RdcGet downstreamtransport.cpp:5346 25016 C A failure was reported by the remote partner]
+	[Error:9027(0x2343) RpcFinalizeContext downstreamtransport.cpp:1117 25016 C A failure was reported by the remote partner]
+	[Error:9027(0x2343) DownstreamTransport::RdcGet downstreamtransport.cpp:5269 25016 C A failure was reported by the remote partner]
+	[Error:9024(0x2340) DownstreamTransport::RdcGet downstreamtransport.cpp:5269 25016 C The file meta data is not synchronized with the file system]

Open in new window



Unfortunately I'm not sure how to interpret these errors. Some searching has suggested that this due to temp files not being replicated but the file attributes for this file (0x20) and others I have looked at do not indicate the temporary attribute is set, so I think that line of investigation is a dead end.
ASKER CERTIFIED SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Good to hear you're running again
Because connections are buffered and processed on the TOE (TCP\IP Offload Engine) chip, resource limitations happen more often then they would if processed by the ample CPU and memory resources that are available to the operating system.  This limitation of resources on the TOE chip can cause communication issues.