DFSR Replica issue with recursive folder generation

Tim Gowen 1 Reputation point
2023-08-07T07:56:48.9666667+00:00

Hi

I have two Windows 2022 server in a replica, and have had to repartition one of the two because the volumes were too big for shadow copy.

In the course of doing this work on the first member, I've noticed that a folder in one of the two servers (the one that's not yet been repartitioned), a particular subfolder is endlessly regenerating itself in the directory so that it creates a very deep level structure which I've been removing using a robocopy mirror command.

The folder structure doesn't appear in the namespace, only on the server itself.

I've tried stopping the replication service, rebooting the server... and I've tried to find out what is causing this issue. It's hard to believe that it's not caused by replication as nothing else is running on the server.

Windows Server Storage
Windows Server Storage
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Storage: The hardware and software system used to retain data for subsequent retrieval.
650 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. JimmySalian-2011 42,106 Reputation points
    2023-08-07T09:21:47.2933333+00:00

    HI Tim,

    Anything in the event logs that could point out issue related to the replication setup ? Ensure that each of the replicated folders has a unique root path and that they do not overlap. For example, D:\Sales and D:\Accounting can be the root paths for two replicated folders, but D:\Sales and D:\Sales\Reports cannot be the root paths for two replicated folders. So anything in the DFS health check via the DFS Management console?

    If you have Microsoft support contact worth checking it and whether you will have to reset the replica and set it again unless there is a way around to fix this after repartitioning.

    Hope this helps.

    JS

    ==

    Please accept as answer and do a Thumbs-up to upvote this response if you are satisfied with the community help. Your upvote will be beneficial for the community users facing similar issues.

    0 comments
  2. Tim Gowen 1 Reputation point
    2023-08-07T12:56:32.4266667+00:00

    Hi, thanks for replying.

    The path is E:\Catalogues\CollectionsAssets\Film_Sound\Sound\SC76 which doesn't seem too long or problematic as a filename.

    The NIC did have a DHCP assigned address which I have corrected to the assigned static IP against the DNS address

    The log shows these:

    The DFS Replication service detected invalid msDFSR-Subscriber object data while polling for configuration information.

    Additional Information:

    Object DN: CN=03c9e849-19a4-4888-bc3c-7d20744bb07d,CN=DFSR-LocalSettings,CN=DAMS-ASSETS-1,OU=Servers,DC=domain,DC=local

    Attribute Name: msDFSR-MemberReference

    Domain Controller: HERON-DC.domain.local

    Polling Cycle: 60 minutes

    And:

    The DFS Replication service encountered an error communicating with partner DAMS-ASSETS-2 for replication group Portfolio.

    Partner DNS address: dams-assets-2.domain.local

    Optional data if available:

    Partner WINS Address: dams-assets-2

    Partner IP Address: 172.16.2.80

    The service will retry the connection periodically.

    Additional Information:

    Error: 1753 (There are no more endpoints available from the endpoint mapper.)

    Connection ID: 7A63FB08-51BB-47B7-A67B-92F8136C1D9C

    Replication Group ID: B4C92C90-2315-4EB3-B54A-C346E4A13EAC

    I managed to locate a PID and kill it, but this killed Explorer and with the new explorer service I am seeing the folders again. However no DFSR errors since 8:40 this morning

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.