Windows 10: DFS replication stopped working from a previously virtualized server

We have a Windows Server file server running as a Hyper-V VM, whose one of the functions is replication destination as part of DFS service. This server was temporary virtualized failover to Azure , then re-committed snapshot restored to the Hyper-V server. Everything works on the server except the replication, which simply does not occur despite lack of any errors from the DFS service. I've done all checks I could find on the DFS settings, all the settings are fine and no errors are found by troubleshooters, all connections are fine as confirmed by DFS backlog and DFS diag PowerShell comma

:)

 

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

 

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

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

 

how to sync dfs namespace server into work folders??

we have data in DFS name space server, we need to sync DFS server with work folder, how to integrate DFS to work folder?? if its possible suggest the way to do it.