DFS Replication never starts on 2 volumes, works on 2 volumes

Ken Simon 26 Reputation points
2023-04-10T20:32:10+00:00

Scenario:

2 Windows Server 2019 servers. We are attempting to replicate 8 folders. On the "current server", these are on 4 volumes, 2 folders per volume. On the "destination" server they are all on the same server. The current server has had a DFS (Domain based) namespace containing these folders for a few years now, but no replication configured. (The server was set up with the knowledge that DFS was coming. It was set up so that file paths would not need to change once the second server was added.) Last week we went to set up DFS Replication. We added the folder structure and shares on the new server, being careful that the permissions matched. We installed DFS Namespaces and Replication on the new server. Added the folders to the namespaces, disabling the targets on the new server so clients did not start looking at them. Added replication groups. 4 of the replicated folders worked fine. These 4 folders exist on 2 of the volumes. All good there. The other 4 folders, on the other 2 volumes have never started replication. We see a 4102 warning on the new destination server, but nothing on the existing server. There are no indications at all in the source machine event log that anything has happened at all. On originating server, "wmic /namespace:\root\microsoftdfs path DfsrReplicatedFolderInfo get ReplicatedFolderName,state" returns:

ReplicatedFolderName  State
Folder1					4
Folder2					4
Folder3					4
Folder4					4

On the receiving member the command shows the following:

ReplicatedFolderName  State
Folder1					4
Folder2					4
Folder3					4
Folder4					4
Folder5					2
Folder6					2
Folder7					2
Folder8					2

Also, on the sending member, the \System Volume Information\DFSR folder is NOT created on these 2 volumes, and the "DFSRPrivate" Junction does not show up in the replicated folder. Both of these show up on the receiving member.

A propagation report for the affected replication groups shows "Reference member returned no replicated folders." under the sending member. No Errors are reported. The receiving member shows "This member is waiting for initial replication for replicated folder <folder name>"

Basically nothing we expect is showing up on the sending member, so replication never actually stops.

All servers are in the same IP subnet in the same site.
All volumes are formatted NTFS.

I have attempted deleting the replication group and re-adding. I ensured the DFSR\Private{GUID} folder was removed from the receiving member befoer re-creating the replication group. Obviously, I could not do this on the sending member.
I used "DFSRDIAG POLLAD /MEM:<mem name>" from the domain controller to all affected file servers in the group as well as both domain controllers between any and all changes.

I looked at the DFSR logs in c:\windows\debug. That was not useful.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,491 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,237 questions
{count} votes