locked
Secondary-Site Cross-Forest - no DB-replication RRS feed

  • Question

  • Hi @ll

    I have set up a secondary site in a remote location that is also in a different forest. Although the Databaes Replication shows an active link, no actual replication is going on.

    I have a Site to Site VPN-connection using Threat Management Gateway 2010 Standard; I have already allowed all protocols towards / from the SCCM servers to make sure, it's not an FW-issue.

    The "Site Data Replication Status" is "Not Applicable", the rcmctrl logfile shows:

    DRS sync started.  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:40:14.649-120><thread=1192 (0x4A8)>
    DRS change application started.  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:41:12.504-120><thread=5060 (0x13C4)>
    Launching 3 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue.~~  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:41:12.507-120><thread=5060 (0x13C4)>
    The asynchronous command finished with return message: [spDRSActivation finished at 16.07.2012 16:41:12. End execute query finished at 16.07.2012 16:41:12.].~~  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:41:12.508-120><thread=5060 (0x13C4)>
    The asynchronous command finished with return message: [spDRSActivation finished at 16.07.2012 16:40:25. End execute query finished at 16.07.2012 16:40:25.].~~  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:41:12.508-120><thread=5060 (0x13C4)>
    There are 3 Drs Activations sprocs running.  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:41:12.509-120><thread=5060 (0x13C4)>
    DRS sync started.  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:41:14.958-120><thread=1192 (0x4A8)>
    Wait for inbox notification timed out.  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:42:04.034-120><thread=3332 (0xD04)>
    Cleaning the RCM inbox if there are any *.RCM files for further change notifications....  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:42:04.034-120><thread=3332 (0xD04)>
    Initializing RCM.  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:42:04.034-120><thread=3332 (0xD04)>
    Processing Replication  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:42:04.041-120><thread=3332 (0xD04)>
    Running configuration EnsureServiceBrokerEnabled.~~  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:42:04.049-120><thread=3332 (0xD04)>
    Running configuration EnsureServiceBrokerQueuesAreEnabled.~~  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:42:04.050-120><thread=3332 (0xD04)>
    Processing replication pattern global_proxy.~~  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:42:04.081-120><thread=3332 (0xD04)>
    Summarizing all replication links for monitoring UI.~~  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:42:04.106-120><thread=3332 (0xD04)>
    The current site status: ReplicationActive.~~  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:42:04.138-120><thread=3332 (0xD04)>
    Processing Replication success.  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:42:04.139-120><thread=3332 (0xD04)>
    Rcm control is waiting for file change notification or timeout after 120 seconds.  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:42:05.145-120><thread=3332 (0xD04)>
    DRS change application started.  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:42:12.812-120><thread=5060 (0x13C4)>
    Launching 3 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue.~~  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:42:12.815-120><thread=5060 (0x13C4)>
    There are 3 Drs Activations sprocs running.  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:42:12.819-120><thread=5060 (0x13C4)>
    DRS sync started.  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:42:15.492-120><thread=1192 (0x4A8)>
    DRS change application started.  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:43:13.132-120><thread=5060 (0x13C4)>
    Launching 3 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue.~~  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:43:13.137-120><thread=5060 (0x13C4)>
    The asynchronous command finished with return message: [spDRSActivation finished at 16.07.2012 16:42:26. End execute query finished at 16.07.2012 16:42:26.].~~  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:43:13.139-120><thread=5060 (0x13C4)>
    The asynchronous command finished with return message: [spDRSActivation finished at 16.07.2012 16:43:12. End execute query finished at 16.07.2012 16:43:12.].~~  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:43:13.140-120><thread=5060 (0x13C4)>
    There are 3 Drs Activations sprocs running.  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:43:13.140-120><thread=5060 (0x13C4)>
    DRS sync started.  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-16-2012 16:43:15.809-120><thread=1192 (0x4A8)>

    This seems to repeat until forever. I am quite sure that the solution is just "a click ahead", but I am completely stuck here...

    Monday, July 16, 2012 2:47 PM

Answers

  • Finally, I found it out!

    The reason was much simpler. The secondary site server (which is located in another domain) had no NTFS-permissions to the inboxes of the primary site. From primary to secondary, the permissions were OK...

    • Marked as answer by Hildi Monday, August 27, 2012 9:46 AM
    Monday, August 27, 2012 9:46 AM

All replies

  • The first step should be to run Replication Link Analyzer.

    May be some more details from the below query 

    select * from RCM_ReplicationLinkStatus

    Have you already checked Replication Troubleshooting Guide

     

    Anoop C Nair - @anoopmannur :: MY Site:  www.AnoopCNair.com :: FaceBook:  ConfigMgr(SCCM) Page :: Linkedin:  Linkedin<

    Monday, July 16, 2012 4:05 PM
  • I have set up a secondary site in a remote location that is also in a different forest.

    You did not mention anything about a trust. Secondaries are only supported in remote forests if there's a two-way forest trust.

    Torsten Meringer | http://www.mssccmfaq.de

    Monday, July 16, 2012 6:04 PM
  • @Anoop

    The SQL statement returns

    SiteOwner    SiteSending    SiteReceiving    ReplicationID    TransportType    UpdateTime    Status    StatusName    LastSyncFinishTime    SnapshotApplied    SnapshotAppliedTime    LinkDownTime
    AAA    BBB    AAA    21    3    2012-07-16 18:35:27.117    2    Active    2012-07-16 18:29:28.780    1    2012-06-14 21:49:38.403    NULL
    AAA    BBB    AAA    22    3    2012-07-16 18:35:27.123    2    Active    2012-07-16 18:32:30.983    1    2012-06-14 21:51:59.823    NULL
    AAA    AAA    BBB    21    3    2012-07-16 18:35:27.120    2    Active    2012-07-16 18:30:18.560    NULL    NULL    NULL
    AAA    AAA    BBB    22    3    2012-07-16 18:35:27.123    2    Active    2012-07-16 18:32:45.003    NULL    NULL    NULL

    IMHO that does not look too bad?

    @Torsten Meringer

    I did not mention that a two-way-forest trust is established and works properly. There are no AD-related replication issues, DNS is stable, too. Sorry, could have made that clear from scratch.

    This is replmgr.log on the primary site:

    ~Waiting for outbound replication files...  $$<SMS_REPLICATION_MANAGER><07-16-2012 16:33:45.032-120><thread=2788 (0xAE4)>
    ~Waiting for incoming replication files...  $$<SMS_REPLICATION_MANAGER><07-16-2012 17:34:01.791-120><thread=3092 (0xC14)>
    ~Scanning high priority outbound replication directory.  $$<SMS_REPLICATION_MANAGER><07-16-2012 17:34:01.816-120><thread=2788 (0xAE4)>
    ~Did not find any replication files.  $$<SMS_REPLICATION_MANAGER><07-16-2012 17:34:01.816-120><thread=2788 (0xAE4)>
    ~Scanning normal priority outbound replication directory.  $$<SMS_REPLICATION_MANAGER><07-16-2012 17:34:01.816-120><thread=2788 (0xAE4)>
    ~Did not find any replication files.  $$<SMS_REPLICATION_MANAGER><07-16-2012 17:34:01.816-120><thread=2788 (0xAE4)>
    ~Scanning low priority outbound replication directory.  $$<SMS_REPLICATION_MANAGER><07-16-2012 17:34:01.820-120><thread=2788 (0xAE4)>
    ~Did not find any replication files.  $$<SMS_REPLICATION_MANAGER><07-16-2012 17:34:01.820-120><thread=2788 (0xAE4)>
    ~Waiting for outbound replication files...  $$<SMS_REPLICATION_MANAGER><07-16-2012 17:34:01.842-120><thread=2788 (0xAE4)>
    ~Waiting for incoming replication files...  $$<SMS_REPLICATION_MANAGER><07-16-2012 18:34:18.011-120><thread=3092 (0xC14)>
    ~Scanning high priority outbound replication directory.  $$<SMS_REPLICATION_MANAGER><07-16-2012 18:34:18.057-120><thread=2788 (0xAE4)>
    ~Did not find any replication files.  $$<SMS_REPLICATION_MANAGER><07-16-2012 18:34:18.057-120><thread=2788 (0xAE4)>

    This is the secondary site server

    ~Did not find any additional replication files.  $$<SMS_REPLICATION_MANAGER><07-16-2012 21:07:59.901-120><thread=280 (0x118)>
    ~There are jobs to site AAA of the same priority waiting to be sent, won't send this batch.  $$<SMS_REPLICATION_MANAGER><07-16-2012 21:07:59.901-120><thread=280 (0x118)>
    ~There are jobs to site AAA of the same priority waiting to be sent, won't send this batch.  $$<SMS_REPLICATION_MANAGER><07-16-2012 21:07:59.901-120><thread=280 (0x118)>
    ~Waiting for outbound replication files...  $$<SMS_REPLICATION_MANAGER><07-16-2012 21:07:59.901-120><thread=280 (0x118)>
    ~Waiting for incoming replication files...  $$<SMS_REPLICATION_MANAGER><07-16-2012 21:12:33.392-120><thread=2468 (0x9A4)>
    ~Scanning high priority outbound replication directory.  $$<SMS_REPLICATION_MANAGER><07-16-2012 21:12:59.909-120><thread=280 (0x118)>
    ~Did not find any replication files.  $$<SMS_REPLICATION_MANAGER><07-16-2012 21:12:59.909-120><thread=280 (0x118)>
    ~Scanning normal priority outbound replication directory.  $$<SMS_REPLICATION_MANAGER><07-16-2012 21:12:59.909-120><thread=280 (0x118)>
    ~Did not find any replication files.  $$<SMS_REPLICATION_MANAGER><07-16-2012 21:12:59.909-120><thread=280 (0x118)>
    ~Scanning low priority outbound replication directory.  $$<SMS_REPLICATION_MANAGER><07-16-2012 21:12:59.909-120><thread=280 (0x118)>
    ~Did not find any replication files.  $$<SMS_REPLICATION_MANAGER><07-16-2012 21:12:59.909-120><thread=280 (0x118)>
    ~There are jobs to site AAA of the same priority waiting to be sent, won't send this batch.  $$<SMS_REPLICATION_MANAGER><07-16-2012 21:12:59.909-120><thread=280 (0x118)>
    ~There are jobs to site AAA of the same priority waiting to be sent, won't send this batch.  $$<SMS_REPLICATION_MANAGER><07-16-2012 21:12:59.909-120><thread=280 (0x118)>
    ~Waiting for outbound replication files...  $$<SMS_REPLICATION_MANAGER><07-16-2012 21:12:59.909-120><thread=280 (0x118)>

    So there is data, but it is not being sent - is there a setting to be made on the secondary site server?


    • Edited by Hildi Monday, July 16, 2012 7:17 PM
    Monday, July 16, 2012 6:42 PM
  • Just an updates as the issue is still not solved:

    The Initialization Status of the Replication Group in SQL is still "required", the StatusUpdateTime is NULL. How can I initialize the Replication Groups?

    Help is very much apprechiated :-(

    Thursday, August 16, 2012 11:01 AM
  • Finally, I found it out!

    The reason was much simpler. The secondary site server (which is located in another domain) had no NTFS-permissions to the inboxes of the primary site. From primary to secondary, the permissions were OK...

    • Marked as answer by Hildi Monday, August 27, 2012 9:46 AM
    Monday, August 27, 2012 9:46 AM