Re: FRS Only replicates on inbound connection, no changes go out.
- From: Mike Drechsler - SPAM PROTECTED EMAIL <mike-newsgroup@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 22 Aug 2005 03:26:06 GMT
Mike Drechsler - SPAM PROTECTED EMAIL wrote:
garry wrote:
Hi run frsdiag and look at the constat txt file and see when they last joined. A quick win is to delete the connection obnjects under sites and serivces on both sides then run repadmin /kcc on both servers then see if they have joined correctly now. You may have to stop and start ntfrs as well
"Mike Drechsler - SPAM PROTECTED EMAIL" wrote:
I have a pair of servers in a small network that will only do file replication in one direction.
Any changes made on the main server are replicating over to the offsite server but changes made on the offsite server do not make it back to the main server.
The strange thing is that if you investigate with Sonar. There are no files backlogged on either server. I installed Ultrasound and the only things it show are a few sharing violations on one of the DFS replicas but all other items appear to be ok. I cleaned up some of the sharing violations but it does not help. There are 2 other DFS links and the sysvol that show no errors but none will send changes back to the main server. I tried doing a D2 restore on the sysvol on the offsite server but this did not help. I have restarted both servers many times. Both are running Windows 2000 Server Std. All patches from windows update are installed and I even tried the hotfix in KB article 815473 but that didn't fix the replication problem (though I do get the event log entries for those sharing violations now).
I get an event 13508 for the DFS link that has the sharing violations but not for sysvol or the other 2 DFS links. Files from the main server still replicate to the DFS link getting the 13508 event so it doesn't seem to amount to much. The main server shows the same 13508 for the same DFS link but nothing else.
Replication between the two servers has worked fine in the past. It just started doing this around July 27. The only events I recall from that time was one of the servers ran out of hard drive space around then, but it's been fixed and there is plenty of free space on both now. The other event was a power outage but the UPS has shutdown software running so the servers would have shut themselves down.
-- WARNING! Email address has been altered for spam resistance. Please remove the -deletethispart-. section before replying directly. Mike Drechsler (mike-newsgroup@xxxxxxxxxxxxxxxxxxxxxxxxxxxx)
That is a good idea, something I had not tried before. I did as you suggested and waited for the autogenerated connection objects to show up on the other server. Then I tried creating files in the sysvol folder of both servers and waiting to see if it would replicate. Unfortunately, it's still only going in one direction.
Now the interesting bit that doing all this has revealed to me is in the constat file:
Replica: DOMAIN SYSTEM VOLUME (SYSVOL SHARE) (057026ff-1bcb-4c05-ab8c86d344b069be)
Member: REMOTESERVER ServiceState: 3 (ACTIVE) OutLogSeqNum: 182 OutlogCleanup: 182 Delta: 0
Config Flags: Multimaster Online Root Path : c:\winnt\sysvol\domain Staging Path: c:\winnt\sysvol\staging\domain File Filter : *.tmp, *.bak, ~* Dir Filter :
Send Cleanup Cos
Partner I/O State Rev LastJoinTime OLog State Leadx Delta Trailx Delta LMT Out Last VVJoin
DOM\MAINSRV$ In Joined 7 Sun Aug 21, 2005 21:00:27
DOM\MAINSRV$ Out Unjoined 7 Sun Aug 21, 2005 21:00:27 OLP_INACTIVE 182 0 182 0 0 0 Sun Aug 21, 2005 18:15:01
The OLP_INACTIVE status seems to indicate that the main server is somehow refusing to accept changes, though I was not able to find any hints on how to solve this. Perhaps a non authoritative (D2) restore on this machine? I had been assuming that this computer was fine since it was sending out changes properly, perhaps my logic was reversed and it's more important to think about which server is not taking the updates.
Any hints from anyone before I do something crazy?
Oh one other thing. All the DFS shares do not show this unjoined status, only the sysvol shows this status. All DFS entires show that both in and outbound replication is joined and the status shows OLP_ELIGIBLE but all 3 DFS replicas also only replicate changes into the remote server but not out from it just like sysvol.
-- WARNING! Email address has been altered for spam resistance. Please remove the -deletethispart-. section before replying directly. Mike Drechsler (mike-newsgroup@xxxxxxxxxxxxxxxxxxxxxxxxxxxx) .
- Follow-Ups:
- Re: FRS Only replicates on inbound connection, no changes go out.
- From: Ace Fekay [MVP]
- Re: FRS Only replicates on inbound connection, no changes go out.
- References:
- FRS Only replicates on inbound connection, no changes go out.
- From: Mike Drechsler - SPAM PROTECTED EMAIL
- RE: FRS Only replicates on inbound connection, no changes go out.
- From: garry
- Re: FRS Only replicates on inbound connection, no changes go out.
- From: Mike Drechsler - SPAM PROTECTED EMAIL
- FRS Only replicates on inbound connection, no changes go out.
- Prev by Date: Re: FRS Only replicates on inbound connection, no changes go out.
- Next by Date: Re: FRS Only replicates on inbound connection, no changes go out.
- Previous by thread: Re: FRS Only replicates on inbound connection, no changes go out.
- Next by thread: Re: FRS Only replicates on inbound connection, no changes go out.
- Index(es):
Relevant Pages
|
Loading
