axe77
asked on
DFS Replication not working
We have two file servers running DFS Replication in two different sites. Servers OS, Windows Server 2008 R2.
Although I had successfully set up the DFS replication between them, it seems not to work properly, experiencing a strange behavior. While running dfsdiag from serverA I get errors for validating namespace "The RPC server is unavailable" and for validating registry entries "The network path was not found". Dfsdiag runs successfully on serverB. I try to access the namespace \\serverA\data from serverB and vice-versa but it is not possible. I read many articles describing issues about the staging file size which in our case increased to 16GB. No success.
Please advise.
Although I had successfully set up the DFS replication between them, it seems not to work properly, experiencing a strange behavior. While running dfsdiag from serverA I get errors for validating namespace "The RPC server is unavailable" and for validating registry entries "The network path was not found". Dfsdiag runs successfully on serverB. I try to access the namespace \\serverA\data from serverB and vice-versa but it is not possible. I read many articles describing issues about the staging file size which in our case increased to 16GB. No success.
Please advise.
Are the two systems in the same domain? Do you have the two sites connected with a VPN?
Too many variations whose details are not included on what you tried and whether you reached some diagnostic causes for the issue at hand?
Too many variations whose details are not included on what you tried and whether you reached some diagnostic causes for the issue at hand?
ASKER
Thanx for your replies.
Two sites are connected through VPN which established via a dedicated leased line 100Mbps (up/down with 85ms latency).
The two systems are in the same domain but in different AD sites.
What I am trying to do is to have both fileservers synced as users travel all the time from one site to another.
Two sites are connected through VPN which established via a dedicated leased line 100Mbps (up/down with 85ms latency).
The two systems are in the same domain but in different AD sites.
What I am trying to do is to have both fileservers synced as users travel all the time from one site to another.
Do you have any errors?
ASKER
Event ID: 5014
Error: 1726 (The remote procedure call failed)
Error: 1726 (The remote procedure call failed)
http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/2b58b4a4-3e0a-460e-b4e9-fd550e5e9c3b/
RPC services running on both?
Time chek? Are the two systems have a time that is close enough within 5minutes accounting for timezone?
RPC services running on both?
Time chek? Are the two systems have a time that is close enough within 5minutes accounting for timezone?
ASKER
RPC is running on both servers, no DNS issues and time is completely synced
What connects the two sites? Make sure the issues not with an access restriction within a VPN.
ASKER
There is no network issue as it was my first thought at the very beginning.
I made some extra tests.
Pure replication works OK between two servers. I created a new share which then I added it in a new replication group, and the replication started immediately. Any changes is synced instantly.
The problem only occurs when a replication group is a member of a namespace. I tried to delete the staging folder in case there was a corruption. After I restarted the servers, the replication started and run for about 20 minutes or so. No success either.
I made some extra tests.
Pure replication works OK between two servers. I created a new share which then I added it in a new replication group, and the replication started immediately. Any changes is synced instantly.
The problem only occurs when a replication group is a member of a namespace. I tried to delete the staging folder in case there was a corruption. After I restarted the servers, the replication started and run for about 20 minutes or so. No success either.
Replication group deals with replication only, the publishing of the replicated directories should not be an issue unless the files are maintained open I.e. there is an anti-virus app that scans any file an access. A replication attempt in this case will fail because the file will be seen as in use.
ASKER
Firewall or antivirus S/W are off
http://blogs.technet.com/b/askds/archive/2009/03/23/understanding-dfsr-debug-logging-part-1-logging-levels-log-format-guid-s.aspx
Those items are disabled where?
Workstations where the drives are mapped?
Those items are disabled where?
Workstations where the drives are mapped?
ASKER
If you mean Firewall and AV are disabled on both servers.
The drives are mapped through Group Policies by using the DFS namespace (i.e. \\domain.com\data\Users)
The drives are mapped through Group Policies by using the DFS namespace (i.e. \\domain.com\data\Users)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
DNS checked... no issue
I made two changes:
1. Enable IPv6
2. Delete DFSrPrivate folder
Now seems that something moving out there... watching and revert.
I made two changes:
1. Enable IPv6
2. Delete DFSrPrivate folder
Now seems that something moving out there... watching and revert.
DFSrProvate is a required directory structure dealing with staging/deleted/conflict etc.
ASKER
DFSrPrivate folder recreated automatically as soon as the server restarted.
What is the status of replication at this point?
ASKER
The replication seems to be in progress. I have got many messages in the Event Viewer verifying this. Nevertheless, I made a test to create a file in serverA which it has not been appeared in serverB yet.
Still waiting...
Still waiting...
Run the DFS report to see how many files need to be replicated.
upstream/downstream on each end. The lowest on one is the rule for both.