Share via

Configuration Manager - Database Replication Link is being configured

Bojan Zivkovic 621 Reputation points
2026-02-07T11:14:36.8333333+00:00

Hi, I am installing secondary site and current status of replication link - Link is being configured. How long does it take to complete, or something is wrong here?

User's image

Without this step completed, MP/DP roles cannot be installed on secondary site server.

Microsoft Security | Intune | Configuration Manager | Deployment
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Bojan Zivkovic 621 Reputation points
    2026-02-07T13:34:34.5366667+00:00

    I did something and now link is active, however Child Site under Replication Status is still empty:

    User's image

    0 comments No comments

  2. Marcin Policht 82,360 Reputation points MVP Volunteer Moderator
    2026-02-07T12:06:24.72+00:00

    “Link is being configured (initializing data between the parent and child site)” is the normal phase where the database replication and file-based replication are seeded between the primary and the new secondary site. The duration varies a lot depending on database size, number of packages and applications already in the environment, SQL performance on both sides, disk I/O, latency between sites, and available bandwidth. In small or clean environments it can finish in 30–90 minutes. In medium environments it is common to see several hours. In large environments or slow WAN links it can legitimately run for 12–24+ hours during initial seeding.

    It is only a concern if the status shows no progress for a long period or logs stop updating. To verify progress, on the primary site server review rcmctrl.log, sender.log, despooler.log, and distmgr.log. On the secondary site server review rcmctrl.log and sitecomp.log. In SQL Server Management Studio you can also run:

    select * from vReplicationDataStatus
    

    and

    exec spDiagDRS
    

    to see replication health and whether data is actively moving. If you see backlog counts decreasing or timestamps updating in logs, the process is working normally even if slow.

    Also confirm there are no bottlenecks such as limited SQL memory, blocked ports (TCP 4022 for SQL Service Broker and SMB 445 for file replication), antivirus scanning the inboxes or SQL data folders, or insufficient disk I/O. Check sender queue on the primary site:

    Get-CMReplicationLinkStatus
    

    If logs show repeated errors, queues not moving for multiple hours, or spDiagDRS reports failed replication groups, then something is wrong. Otherwise, if logs are active and data is moving, waiting is expected and MP or DP role installation will remain blocked until initialization completes.


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin


Your answer

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