Disabled FRS replication on a DFS link, but the targets still list the replica set in their FRS conf
- by Graeme Donaldson
It's been a while since I've had to deal with the wonders of FRS, so I'm doing some testing to refresh my memory.
This is what I've done so far. I am stuck with FRS rather than DFS-R for the moment since not all of my link targets are running R2.
Created a domain-based DFS root, hosted on 4 servers.
Created a DFS link under the root, targeted at 2 servers. The shares on both servers were empty.
Dropped about 500MB of data into the target folder on one server and waited for replication to complete.
Added/removed/modified files on both targets and confirmed that changes are replicated within a few seconds.
Deleted the contents of the target folder on 1 server and waited for the other server to replicate the deletion.
All of this worked perfectly, so now I want to remove my DFS link since I only created it for testing purposes. This is where it gets weird. I'm pretty sure that in the past I've disabled replication on the DFS link and after a short amount of time each target would log an info event in the FRS event log, something along the lines of "this server is no longer a member of replica set X". I have waited about 3 hours and I haven't seen this happen.
ntfrsutl ds
tells me that the server is not a member of any set, which is expected because when I disable replication on the link, the AD attributes on the computer object are removed.
The weird part is...
ntfrsutl sets
still shows me the replica set, with all the properties, etc.
So it seems like the FRS-related attributes of the target server's AD object are gone, but the FRS service for some reason hasn't removed the replica set.
Can anyone see what I have done wrong?
