DFS Replication issue Server 2012 R2
We run a single DC domain, but for the last few weeks we have been getting this error:
I checked in the DFS Management snap-in and found that there is a replication group for the Domain System Volume for contains our DC and server that has NEVER been on our network.
Not sure how this can happen but never in the history of the company has there been a second DC.
How can I go about removing this replication, if serves no purpose and shouldn't be there int he first place.
Log Name: DFS Replication
Source: DFSR
Date: 2015-10-20 09:03:20 AM
Event ID: 4012
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: dc01.domain.za
Description:
The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 111 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected.
To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group.
Additional Information:
Error: 9061 (The replicated folder has been offline for too long.)
Replicated Folder Name: SYSVOL Share
Replicated Folder ID: D63839C2-FA50-43C2-93E3-23AC87296296
Replication Group Name: Domain System Volume
Replication Group ID: 47FB958A-E93C-4740-9CA7-E63E0E86AC9B
Member ID: 081FF782-1C9C-4DCE-AC36-243FE36CBB09
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="DFSR" />
<EventID Qualifiers="49152">4012</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords >
<TimeCreated SystemTime="2015-10-20T07:03:20.0000 00000Z" />
<EventRecordID>716</EventRecordID>
<Channel>DFS Replication</Channel>
<Computer>dc01.domain.za</Computer>
<Security />
</System>
<EventData>
<Data>D63839C2-FA50-43C2-93E3-23AC87 296296</Da ta>
<Data>111</Data>
<Data>C:\Windows\SYSVOL\domain</Data >
<Data>9061</Data>
<Data>The replicated folder has been offline for too long.</Data>
<Data>SYSVOL Share</Data>
<Data>Domain System Volume</Data>
<Data>47FB958A-E93C-4740-9CA7-E63E0E 86AC9B</Da ta>
<Data>081FF782-1C9C-4DCE-AC36-243FE3 6CBB09</Da ta>
<Data>60</Data>
</EventData>
</Event>
I checked in the DFS Management snap-in and found that there is a replication group for the Domain System Volume for contains our DC and server that has NEVER been on our network.
Not sure how this can happen but never in the history of the company has there been a second DC.
How can I go about removing this replication, if serves no purpose and shouldn't be there int he first place.
Check location of fsmo first
Then its fine to remove this server if its give no value to ur environment but first shut it down for a day
As error this server in ad topology
Maybe it was dc and depromoted
Then its fine to remove this server if its give no value to ur environment but first shut it down for a day
As error this server in ad topology
Maybe it was dc and depromoted
ASKER
The thing is that this server is not on the local LAN
Was it before ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No, the server was never part of the local LAN. The server it is referring to is situated in a different geographical location and there is no link of any kind between the servers, in fact the server in question is a DC on an entirely different domain.
So there's no reason nor no way there servers could ever have replicated at any point in time.
So there's no reason nor no way there servers could ever have replicated at any point in time.
Interesting.. if you go under ADSS do you see any new sites or replication partners?
ASKER
Nope, no new sites or replication partners.
Did a full backup of the server and deleted the server it was trying to replicate with, all seems fine today, no errors in the event log.
Did a full backup of the server and deleted the server it was trying to replicate with, all seems fine today, no errors in the event log.
ASKER
Thanks, just wanted to be 100% before deleting.
Would be interesting to find out how it got there.
ASKER
Is it safe to delete from here and will it resolve the problem?