Windows 10: 2 node DFS only replicating one way

I have 2 nodes server A2012r2 and server B2022. Server A is an old file server we are replacing and server B will be the new file server. Once users are migrated over to server B we will shut down server A. I have set up a DFS share between the 2 servers. It appears that all the data from server A is now on server B. If I add a file to server A it is on Server B almost instantly 10GB connection. however, if I add a file to server B it never makes it to sever B. both servers show 0 files backlog. I am new to DFS and the lack of any good monitoring is a little crazy to me. what steps shoul

:)

 

DFS Replication

I have 2 servers with DFS Replication only enabled. Unknown to me when one of the servers failed (couple of months?) but I noticed today that DFS was displaying a message that the connection was no longer replicating--both ends showing disabled. I re-enable
both sides and the topology test now passes. My question is, will all changes which occurred while they were disabled now "catch up" ? Also, did DFS automatically disable them because one side was down for too long ? I made a change to a test text file
and it did replicate but not sure about files which changed during the server down time.

Thanks

 

Correct way to permanently decommission FS1 without effecting the DFS namespace and replication?

Hi, we are looking to decommission our old DFS file server (FS1). FS1 was the original file server where we setup the DFS and replicated to FS2 and FS3. We had all three servers replicating the correctly
for the past few months. Now we have decided it’s time to decommission FS1. We shutdown FS1 to see if the everything would still function. With FS1 offline, FS2 and FS3 are still replicating without issue.

Can you tell me the correct way to permanently decommission FS1 without effecting the DFS namespace and replication? When I open DFS Management on FS2 I see an error on our namespace. “The namespace cannot
be queried. The specified domain either does not exist or could not be connected”.

Environment: 3 File servers, 1 namespace, 3 replications

FS1 – Server 2008 R2 (Need to decommission but original creator of DFS namespace)

FS2 – Server 2012

FS3 – Server 2012

1 Namespace

\\domain.com\dfs

3 Replications

\\domain.com\dfs\profiles

\\domain.com\dfs\smfiles

\\domain.com\dfs\test

 

Restarting Members of DFS Replication Groups on Server 2016 Standard

Restarting Members of DFS Replication Groups:

Hello Guys,

I would like to understand Best Practice for restarting members of Replication Groups, and would be delighted for the support, as i am unable to locate this information on Microsofts extensive documents base: DFS Replication overview | Microsoft Docs

We have two Replication Groups configured for sharing their own respective folders, these groups each contain five members of a meshed group.

What I would like to understand what is the best way to undertake a restart of a member for say a Windows Update (ETA to complete relatively unknown) ?

I have witnessed some mention that shutting down the DFS Replication Service on a member and restarting the server should be sufficient. However, according to this article (If i am understanding correctly: Microsoft DFS Deployment Considerations & Best Practises | Experts Exchange) it
states:

>For any reason if DFSR replicated folder replication need to be stopped, change replication schedule to No Replication. Do not stop DFSR service. It may leads to DFSR database goes in journal wrap state and take much time to recover.

So am i having to completely stop replication across all groups to restart the member, surely this is overkill?

I have also noticed there to be the option of Disabling the Member but im not completely sure what scenario this is used for.

Any assistance is gratefully received.

Thanks

Mark