DFS Error : Found 2 <DfsrReplicatedFolderConfig> objects with same ReplicationGroupGuid
After recovering from a crashed virtual server we started getting the following error when checking DFS backlogs ::
Found 2 <DfsrReplicatedFolderConfi
There are 4 Server 2008 R2 servers connected in a mesh for the DFS structure. We only get the error when checking the backlogs on 1 of the servers. The DFS seems to still be in synch and new files are synchronized to all servers constantly.
Found 2 <DfsrReplicatedFolderConfi
There are 4 Server 2008 R2 servers connected in a mesh for the DFS structure. We only get the error when checking the backlogs on 1 of the servers. The DFS seems to still be in synch and new files are synchronized to all servers constantly.
ASKER
The virtual servers VHD expanded to the point it filled the physical storage and the server crashed. We had to run the DFS for 2 days without this server as part of it. During that time we compressed the VHD file, expanded the storage space and then were able to get the virtual server up and running again.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes we've found the same instructions on multiple sites. They have not had any impact on the problem.
Can you check whether the DFS-R replication somehow references two connections to or from this system?
i.e. connection
server A to this system
system to server a
system to server A
There should be a GUID of the duplicate.
to which system does that GUID belong. That may simplify
Difficulty is whether there are files on the recovered VM that have yet to replicate out.
one option is to use robocopy with the /L flag (run through but do not actually copy.
to see if there are files here that need to go look at the staging folder on this VM, and see if there are outsdanding .....
i.e. connection
server A to this system
system to server a
system to server A
There should be a GUID of the duplicate.
to which system does that GUID belong. That may simplify
Difficulty is whether there are files on the recovered VM that have yet to replicate out.
one option is to use robocopy with the /L flag (run through but do not actually copy.
to see if there are files here that need to go look at the staging folder on this VM, and see if there are outsdanding .....
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Arnolds answer was part of the solution but a few other items were required.
Did you readd the recovered VM back DFS-R group/DFS without removing the old reference???