OK...We have been struggling with a number of issues with 2 Server 2012 instances with DFS-R installed on them, publishing to a DFS namespace hosted by our DCs.
We finally decided to roll back to Server 2008 R2 due to all the problems, especially when one of the 2012 servers literally died!
Unfortunately, due to the sudden nature of the removal of the DFS member, it was never gracefully removed from the replication group. Now the server has been rebuilt, with 2008 R2 instead, I'm a little nervous of the next steps!
All the data is still untouched/unchanged on the data drive on the rebuilt server. Prior to starting this, we had changed DFS Replication to occur between 22:00-06:00 only, so this was changed to never replicate, and the member was disabled in the replication group. However - this was after the server was ungracefully "removed"...
The server has been rebuilt with the same name and same IP as the 2012 instance was; but i haven't installed DFS-R on the new server yet. Obviously the 2012 server is reporting a topology error as it can't find the other server. Previous to this due to other problems, the server had been removed from the DFS Namespace targets group - so the main (only) target was the server that remains unchanged. Also, the master server in the replication group again is the one that hasn't been touched yet.
Can anyone advise me on the next step here? Will I get away with trying to reconnect the server, or would it be safer to rename the server to something else with a new IP and add it as a new member of the DFS-R group? We are going to have to rebuild the other server as well after this, so i obviously need to make sure this is working properly first!