Distributed File System Replication DFSR The content set was not found error
well i've reached end of rope one. our replication server worked fine months no issues. of sudden stopped working. tried think of, disabling/enabling replication server, deleting/readding replication group, making sure one set primary, reinstalling dfs, deleting system volume information\dfsr folder ect. nothing working.
what wierd fails on our d: drive, meaning if setup replication on folder within c: drive, works perfect! if setup replication folder on our d: drive, not work. problem affects 1 of our servers. replication works on other servers, , on the affected server if replication folder setup on drive. on affected server, debug log shows error:
20121210 15:21:05.293 1940 srtr 957 [warn] server_establishsession failed establish replicated folder session. connid:{cc5e21cc-29a0-410e-8108-b98936753a7a} csid:{7d55e528-165e-4ea8-a009-f907bf9e1838} error:
+ [error:9028(0x2344) upstreamtransport::establishsession upstreamtransport.cpp:808 1940 c content set not found]
+ [error:9028(0x2344) outconnection::establishsession outconnection.cpp:532 1940 c content set not found]
+ [error:9028(0x2344) outconnection::establishsession outconnection.cpp:476 1940 c content set not found]
other servers report:
+ [error:9027(0x2343) downstreamtransport::establishsession downstreamtransport.cpp:4179 7628 c failure reported remote partner]
+ [error:9028(0x2344) downstreamtransport::establishsession downstreamtransport.cpp:4179 7628 c content set not found]
we noticed system volume information\dfsr folder not recreated d: drive, recreated on c: drive on same server. we've troubleshooted far can , stuck. problem seems occur replicated folder on d: drive. saw kb looked similar, seemed hyperv/snapshot related.
i think started after did clean install of server 2008 r2 several months ago, used same data (d:) drive can't sure becuase didn't notice until becuase server replicating backup purposes.
help!!!!!!!!!!
thanks reply. fixed after days of troubleshooting. issue resolved after backing affected drive, formatting it, deleting partition, readding partition, restoring data. more details below.
to view dfsr logs view last dfsr*.log log file generated at:
c:\windows\debug\
content set not ready
means 1 of servers has either not received new configurations yet, or initial replication has not finished. run repadmin /syncall , dfsrdiag pollad on servers force configuration changes, wait until finished.
content set not found
serious error can happen number of reasons. happened after upgrading motherboard and performing inplace upgrade, i suspect can happen other reasons well. issue caused volume guid mismatch between dfsr configuration/database, , actual volume guid of disk. issue affected single drive on single server. if added replication folder drive on same server, replication worked without issue.
attempt #1
take screenshots of dfsr configurations, remove affected server dfsr configurations.
run repadmin /syncall , dfsrdiag pollad on servers
rename x:\system volume information\dfsr\database_*\ folder on affected disk. may have grant ownership , add permissions administrators group, rename folder command prompt ie: rename d:\system volume information\dfsr\database_2dss_sdf23_234s_2342 d:\system volume information\dfsr\database_2dss_sdf23_234s_2342_old
restart dfs replication service.
add test replication group & folder run repadmin /syncall , dfsrdiag pollad.
dfsrprivate folder should added test folder on each server. if not, issue still occuring.
if folder appears, issue resolved. readd affected server replication group & folders run repadmin /syncall , dfsrdiag pollad on servers force configuration changes, wait until finished.
dfsr perform re-syncronization, transfer files changed.
attempt #2
if attempt #1 failed, remove test replication group & folder run repadmin /syncall , dfsrdiag pollad
ensure affected server removed other replication groups & folders.
backup affected volume.
format affected volume.
delete affected volume partition.
readd volume partition.
reboot server.
restore data newly added partition.
reboot server.
add test replication group & folder run repadmin /syncall , dfsrdiag pollad.
dfsrprivate folder should added test folder on each server. if not, issue still occuring.
if folder appears, issue resolved. readd affected server replication group & folders run repadmin /syncall , dfsrdiag pollad on servers force configuration changes, wait until finished.
dfsr perform re-syncronization, transfer files changed.
Windows Server > File Services and Storage
Comments
Post a Comment