Using DFS-Replication and not using DFS-Namespace
File server A (2012) and server B (2019) in the replication group and are in the same physical location. They are also DCs, just an FYI.
File server A is the primary member
Topology is Full Mesh
Multipurpose Replication group
The data size is about 1 TB.
We have a number of share folders on server A and B.
Users have their drives mapped to server B as its a newer server and Server A is there as just in case.
The shares are identical on both servers A and B and DFS-R is used to keep the data in sync on both servers and DFS-R is in "Full Mesh" mode and setup as "multipurpose replication group".
Today, server A's data partition where all the shares are, crashed so although the server A's OS is fine and running, the shares are not accessible on it.
Users are not impacted as their share drives are mapped to Server B.
Server A's data partition will be fixed in a couple days.
How would I go about restoring server A's data and have the DFS-R sync normally after fixing the data partition?
Do I simply re-create the folders and share them on Server A and let DFS-R take care of the data restore automatically from Server B or do I restore Server A's data using backup and let DFS-R sync the changed files since the crash? I would prefer to have DFS-R take care of the data restore automatically.
And since server A was the primary member when DFS-R was first setup and thus authoritative, is there anything I need to do differently in order to accomplish that? I need the data on Server B to be used.
It's in Full mesh so I'm not sure if server A being the primary member matters.
And since server A's data partition is down, should I manually stop the DFS service on both servers for now to avoid any new issues or remove server A from the replication group or does it not matter?