We help IT Professionals succeed at work.

DFS Replication Setup Issues

2,733 Views
Last Modified: 2017-10-03
We have installed and configured DFS on two servers, setting up 5 different folders to be included in the Replication Group. Both servers are running Windows Server 2012 R2.

2 of these folders have completed the initial synchronisation and seem to be working correctly. The other 3 look to be stuck in the "Awaiting Initial Sync" stage with the message "This member is waiting for initial replication for replicated folder NAME." from the health diagnostic report for these three folders.

We have tried removing the DFS role, rebooting and re-adding the DFS role but the situation remains the same. There are no errors in the Event Viewer, just informational messages stating that everything is working. Running the "Verify Topology" option in DFS Management reports that "The topology for replication group NAME is fully connects. Data can replicate throughout the topology".

Making changes to DFS settings in the DFS Management console correctly replicates to other servers relatively quickly - it is just the contents of these folders that do not seem to start.

Any suggestions on troubleshooting this to get the initial replication complete greatly received!
Comment
Watch Question

Dan McFaddenSystems Engineer
CERTIFIED EXPERT

Commented:
Can you run the following command from a PowerShell console (need admin rights):

1. Import-Module DFSR
2. Get-DfsrBacklog | sort ReplicationGroup, sendingmember | ft -a

Open in new window


This there any backlog?

Also, those DFSR targets may be missing a primary member.  Here is an article explaining the process to correct.

Link:  http://gsilt.blogspot.de/2016/06/dfs-waiting-for-initial-replication.html

Dan

Author

Commented:
Thanks for the response - I have run the command suggested from an elevated command prompt and it prompts for the source and destination server:

Entering the primary server as the source and the receiving server as the destination - the command returns no output, just returns to the Powershell prompt.

Entering the receiving server as the source and the primary server as the destination - this generates an error "Get-DfsrBacklog :  Skipping the replicated folder because it has an invalid version vector. Replicated folder: "NAME""

I have tried running the other command suggested to set the primary - the command completes, but there is still no data being replicated across any of these folders.
Dan McFaddenSystems Engineer
CERTIFIED EXPERT

Commented:
The "Get-DfsrBackLog" command usually does not require a source or destination server in the command.  But the user running the command needs to be a domain admin, no need to use "Run As Admin"  But it does need to be run from a computer with the DFSR PowerShell module installed.

1.  Do you have a domain in place?
2.  Are these servers domain member servers?
3.  Is there a DFS Namespace in use?
4.  Are the directories to be replicated exist on both servers?
5.  Are the shares associated with the directories in #4 setup on both servers?
6.  Do the NTFS permissions match on both servers?
7.  Do the Share permissions match on both servers?

Can you post the output of the following commands?

1.  Get-DfsrMember
2.  Get-DfsrFolder

Dan

Author

Commented:
I am running these commands logged on as a domain administrator and using the 'run as administrator' option to launch Powershell to cover off most permission related issues.

1. Yes, there is a domain in place.
2. These servers are member of the domain.
3. I have not deployed and DFS Namespaces yet, but I have added this role to these servers.
4. The directories exist primarily on the source server. As part of adding the folders to DFS I selected the option for this wizard to create the required folders on the destination server. This has added the top level folder for each of these folders to the destination server, but these remain empty.
5. The folders are shared from the source server and users still connect to this using \\servername\share but there is not a lot of data change. The folders are not shared on the destination server at this time.
6. The DFS wizard is set to copy the existing permissions as part of the sync (and this works for the 2 folders that are working) - the 3 problematic folders have no contents as of yet.
7. As above, the folders are only current shared from the primary server until we get the initial replication completed.

Get-DfsrMember returns:

GroupName                    : CIC-PFB RG
ComputerName                 : SERVER1
DomainName                   : domain.local
Identifier                   : f097870a-6df3-4f0c-b7a2-27165d9d288e
Description                  :
DnsName                      : SERVER1.domain.local
Site                         : Default-First-Site-Name
NumberOfConnections          : 2
NumberOfInboundConnections   : 1
NumberOfOutboundConnections  : 1
NumberOfInterSiteConnections : 2
NumberOfIntraSiteConnections : 0
IsClusterNode                : False
State                        : Normal

GroupName                    : CIC-PFB RG
ComputerName                 : SERVER2
DomainName                   : domain.local
Identifier                   : bff50003-807c-45a6-806d-52a9ebf6cacc
Description                  :
DnsName                      : SERVER2.domain.local
Site                         : PFB
NumberOfConnections          : 2
NumberOfInboundConnections   : 1
NumberOfOutboundConnections  : 1
NumberOfInterSiteConnections : 2
NumberOfIntraSiteConnections : 0
IsClusterNode                : False
State                        : Normal

Get-DfsReplicatedFolder returns:


GroupName              : CIC-PFB RG
FolderName             : ATLAS
DomainName             : domain.local
Identifier             : 4e85511b-baaa-4896-bbf6-9ac52e33a3f7
Description            :
FileNameToExclude      : {~*, *.bak, *.tmp}
DirectoryNameToExclude : {}
DfsnPath               :
IsDfsnPathPublished    : False
State                  : Normal

GroupName              : CIC-PFB RG
FolderName             : PUBLIC
DomainName             : domain.local
Identifier             : 93f7ad37-e8f5-4f8f-b1ed-3dbf8997fcd1
Description            :
FileNameToExclude      : {~*, *.bak, *.tmp}
DirectoryNameToExclude : {}
DfsnPath               :
IsDfsnPathPublished    : False
State                  : Normal

GroupName              : CIC-PFB RG
FolderName             : POSEIDON
DomainName             : domain.local
Identifier             : a69c2a2d-06a4-4510-9e12-f1b1e6b3999a
Description            :
FileNameToExclude      : {~*, *.bak, *.tmp}
DirectoryNameToExclude : {}
DfsnPath               :
IsDfsnPathPublished    : False
State                  : Normal

GroupName              : CIC-PFB RG
FolderName             : ScheduledTasks
DomainName             : domain.local
Identifier             : ae98b4d4-4da4-4931-b50f-65690ac3dbb4
Description            :
FileNameToExclude      : {~*, *.bak, *.tmp}
DirectoryNameToExclude : {}
DfsnPath               :
IsDfsnPathPublished    : False
State                  : Normal

GroupName              : CIC-PFB RG
FolderName             : Network
DomainName             : domain.local
Identifier             : 3916329a-6869-43db-89bb-ec2f1859f4ba
Description            :
FileNameToExclude      : {~*, *.bak, *.tmp}
DirectoryNameToExclude : {}
DfsnPath               :
IsDfsnPathPublished    : False
State                  : Normal

GroupName              : CIC-PFB RG
FolderName             : Users
DomainName             : domain.local
Identifier             : 5469d90c-6839-479e-9b79-6bb9b54c40fa
Description            :
FileNameToExclude      : {~*, *.bak, *.tmp}
DirectoryNameToExclude : {}
DfsnPath               :
IsDfsnPathPublished    : False
State                  : Normal
Dan McFaddenSystems Engineer
CERTIFIED EXPERT

Commented:
I would verify the following on both servers:
** I rarely trust wizards...

1.  That the physical directories exist on both servers.
2.  That the NTFS permission match on both servers.
3.  That the shares are setup the same on both servers.
4.  That the Share permissions are the same on both servers.
5.  The shares can be accessed via UNC paths on both servers.

The directory structures must be properly setup (physical folders and shares) before DFSR will function properly.  My experience has always to verify everything manually before enabling DFSR.

Dan

Author

Commented:
I get the reluctance to trust wizards fully :) I have checked this now and added the shares for these folders just to ensure that this is configured as suggested.

1. The root directories exist on the destination server.
2. The root directories have inherited the correct NTFS permissions from the source and these are identical on both servers.
3. There are identical shares on both the source and destination server to all of the folders configured in DFS.
4. The share permissions in both the source and destination locations are identical.
5. I have checked that these shares are accessible via UNC from a couple of different servers on the network.
Dan McFaddenSystems Engineer
CERTIFIED EXPERT

Commented:
What does the output of this command say for the Replication Groups?

dfsradmin membership list /rgname:<YourReplicationGroupName> /attr:RfName,MemName,LocalPath

Open in new window


Dan

Author

Commented:
Running that command returns:

RfName                 MemName     LocalPath
ATLAS                    SERVER1          D:\Data\ATLAS
ATLAS                    SERVER2          D:\Data\ATLAS
Network                SERVER1          D:\Network
Network                SERVER2          D:\Network
POSEIDON            SERVER1          D:\Data\POSEIDON
POSEIDON            SERVER2          D:\Data\POSEIDON
PUBLIC                  SERVER1          D:\Data\PUBLIC
PUBLIC                  SERVER2          D:\Data\PUBLIC
ScheduledTasks  SERVER1          D:\ScheduledTasks
ScheduledTasks  SERVER2          D:\ScheduledTasks
Users                    SERVER1           D:\Users
Users                    SERVER2           D:\Users
Dan McFaddenSystems Engineer
CERTIFIED EXPERT

Commented:
Are there any errors or warnings in the "DFS Replication" Event Log, on either server?  

Its under Computer Management > Event Viewer > Applications and Services Logs > DFS Replication.

Dan
Dan McFaddenSystems Engineer
CERTIFIED EXPERT

Commented:
There may also be more information in the DFSR debug log.  It is located at the following location:

C:\Windows\debug\Dfsrxxxxx.log

Dan

Author

Commented:
The only non-informational entries in the Event Viewer are on the destination server are warnings that appear when the image based backup runs on the source server:

The DFS Replication service is stopping communication with partner SERVER1 for replication group CIC-PFB RG due to an error. The service will retry the connection periodically.
 
Additional Information:
Error: 9036 (Paused for backup or restore)
Connection ID: F38D38AD-F017-4674-BF7C-F3A9D23A98D2
Replication Group ID: 4A6D9514-F8C3-419B-8FD5-7C1AECBC5BD3

This occurs twice a day when the VSS portion of the backup runs on SERVER1 and is immediately followed by:
The DFS Replication service successfully established an inbound connection with partner SERVER1 for replication group CIC-PFB RG.

There are no warnings or errors on the source server at all.
Dan McFaddenSystems Engineer
CERTIFIED EXPERT

Commented:
That is to be expected.  In the debug logs?

Dan

Author

Commented:
In the DFSR debug log there are some recurrence of errors that look like the following:

20170314 12:16:49.186 6196 ISYN    68 InitialSyncManager::ReturnToken InitialSync sync step not finished yet. Wake up other session tasks.
20170314 12:16:49.186 6408 DOWN  4062 DownstreamTransport::EstablishSession Failed on connId:{F38D38AD-F017-4674-BF7C-F3A9D23A98D2} csId:{4E85511B-BAAA-4896-BBF6-9AC52E33A3F7} rgName:CIC-PFB RG Error:
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 6408 C A failure was reported by the remote partner]
+      [Error:9028(0x2344) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 6408 C The content set was not found]
20170314 12:16:49.186 6408 INCO  7114 InConnection::RestartSession Retrying establish contentset session. connId:{F38D38AD-F017-4674-BF7C-F3A9D23A98D2} csId:{4E85511B-BAAA-4896-BBF6-9AC52E33A3F7} csName:ATLAS
20170314 12:16:49.186 6408 INCO  1021 [WARN] SessionTask::Step (Ignored) Failed, should have already been processed. Error:
+      [Error:9027(0x2343) InConnection::TransportEstablishSession inconnection.cpp:7701 6408 C A failure was reported by the remote partner]
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4076 6408 C A failure was reported by the remote partner]
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 6408 C A failure was reported by the remote partner]
+      [Error:9028(0x2344) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 6408 C The content set was not found]
20170314 12:16:49.186 6408 ISYN    68 InitialSyncManager::ReturnToken InitialSync sync step not finished yet. Wake up other session tasks.
20170314 12:18:09.193 6408 DOWN  4062 DownstreamTransport::EstablishSession Failed on connId:{F38D38AD-F017-4674-BF7C-F3A9D23A98D2} csId:{93F7AD37-E8F5-4F8F-B1ED-3DBF8997FCD1} rgName:CIC-PFB RG Error:
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 6408 C A failure was reported by the remote partner]
+      [Error:9028(0x2344) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 6408 C The content set was not found]
20170314 12:18:09.193 6408 INCO  7114 InConnection::RestartSession Retrying establish contentset session. connId:{F38D38AD-F017-4674-BF7C-F3A9D23A98D2} csId:{93F7AD37-E8F5-4F8F-B1ED-3DBF8997FCD1} csName:PUBLIC
20170314 12:18:09.193 6408 INCO  1021 [WARN] SessionTask::Step (Ignored) Failed, should have already been processed. Error:
+      [Error:9027(0x2343) InConnection::TransportEstablishSession inconnection.cpp:7701 6408 C A failure was reported by the remote partner]
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4076 6408 C A failure was reported by the remote partner]
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 6408 C A failure was reported by the remote partner]
+      [Error:9028(0x2344) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 6408 C The content set was not found]
20170314 12:18:09.193 6408 ISYN    68 InitialSyncManager::ReturnToken InitialSync sync step not finished yet. Wake up other session tasks.
20170314 12:18:09.194 1980 DOWN  4062 DownstreamTransport::EstablishSession Failed on connId:{F38D38AD-F017-4674-BF7C-F3A9D23A98D2} csId:{4E85511B-BAAA-4896-BBF6-9AC52E33A3F7} rgName:CIC-PFB RG Error:
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 1980 C A failure was reported by the remote partner]
+      [Error:9028(0x2344) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 1980 C The content set was not found]
20170314 12:18:09.194 1980 INCO  7114 InConnection::RestartSession Retrying establish contentset session. connId:{F38D38AD-F017-4674-BF7C-F3A9D23A98D2} csId:{4E85511B-BAAA-4896-BBF6-9AC52E33A3F7} csName:ATLAS
20170314 12:18:09.194 1980 INCO  1021 [WARN] SessionTask::Step (Ignored) Failed, should have already been processed. Error:
+      [Error:9027(0x2343) InConnection::TransportEstablishSession inconnection.cpp:7701 1980 C A failure was reported by the remote partner]
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4076 1980 C A failure was reported by the remote partner]
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 1980 C A failure was reported by the remote partner]
+      [Error:9028(0x2344) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 1980 C The content set was not found]
Systems Engineer
CERTIFIED EXPERT
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
Thanks for that, I'll run through those steps later today and see if that improves things.

Thanks for your help on this so far.
Dan McFaddenSystems Engineer
CERTIFIED EXPERT

Commented:
Any additional information on this question?

Dan
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.