robocopy /MIR /E /R:0 /W:0 /NP /COPYALL M/T:128 /LOG:c:\temp\file.log

The COPYALL is important, it will copy the access rights and the audit of your files. If you don't use this param, DFSR will think your files are differents.

/MIR will delete the files which are on the destination server and not on the source server. So be carefull

2) when the robocopy is finished, you can recreate your replication which your source server as primary.

During the initial replic, the database of DFSR will be created in the directory c:\System Volume Information\DFSR\database_xxx_xxxx. Until the databases ar increasing, the replication will not begin.

3) The replic can take very long time, with 1000 000 files my initiale replic took 24 h.

4) The replication is finished when the event log id 4104 appears on the destination server. To be sure, you can test with creating a file on a server and check his replication on the other. You must test too the other side.

If you want to follow your initial replication you can look the backlog of your replication :

fsrdiag backlog /rgname:<name of your replication group> /rfname:<name of your shared directory> /sendingmember:<source server> /receivingmember:<dest server> /v

To be sure it's the good server as primary server, you can verify with :

dfsradmin membership list /rgname:<> /attr:IsPrimary,MembershipGuid,memname

The logs of the replication are in c:\windows\debug\.

With this method you could have an operationnal dfsr without loose files during the replication.

If you prefer and don't want to do an pre-replication:

• You can stop the service and deactivate him.

• Configure your source server as primary with this command :

  dfsradmin membership set /rgname:<> /rfname:<> /memname: /isprimary:true

and verify :

dfsradmin membership list /rgname:<> /attr:IsPrimary,MembershipGuid,memname

This method explain to dfsr in case of conlict with 2 files, the primary server will win and his file will be the reference. I can't affirm you will not loose files during replication. And the dfsr will take a very long time to re-sync all your files.

So I recommend the first method.

ALTRI LINK UTILI:

BEST PRACTICE: Microsoft DFS Deployment Considerations & Best Practises | Experts Exchange (experts-exchange.com)

Powershell command: https://docs.microsoft.com/en-us/powershell/module/dfsr/?view=winserver2012r2-ps

https://kitkatneko.wordpress.com/tag/dfsr/

https://gallery.technet.microsoft.com/scriptcenter/PowerShell-DFS-Replication-e1c8d772

https://social.technet.microsoft.com/wiki/contents/articles/438.dfs-replication-survival-guide.aspx