Jump to content


firstcom

Site Replication

Recommended Posts

We use SCCM 2012 R2 and have a "Central" ConfigManager server (site code FCC) as well as two primary servers: our main server that we use for almost everything (HQ1), and a disaster recovery ConfigManager server (DR1) that we'd like to replicate from what we do on HQ1.

So the hierarchy is:

FCC
/ \
DR1 HQ1

Under the monitoring tab, in the Site Node Status, it shows a red "X" between FCC and HQ1. It's apparently been this way for some time, but I'd like to get it resolved. When you hover over it, it shows for "Global Data Replication Status" that HQ1 to FCC and FCC to HQ1 is green and active. However, for "Site Data Replication Status" for HQ1 to FCC, it's red and shows a failed status.

When I right click and run a report for errors, nothing really stands out as problematic that's recent that would explain the communication/replication issue between HQ1 and FCC.

 

When I run the Link Analyzer tool, I see errors about "Site is NOT active, so not calling the DrsActivation procedures on DRSSite queue" and errors about the "IsSiteActive" rule being false.

 

5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : All links are initialized between subscriber HQ1 and publisher FCC.
5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : Getting results of rule: IsSiteActive execution
5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : Loading result Xml from rule:IsSiteActive
5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : rule:IsSiteActive has some dependent rules
5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : Working with parent rule:IsSiteActive -> dependent rule:DoesFileReplicationRouteExist
5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : Appending result xml
5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : Rule IsSiteActive result: failed.
5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : Rule: IsSiteActive failed. Stopped running replication link analysis rules.
5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : Completed replication link analysis thread.

I should note that everything seems to be working just fine with our primary server, HQ1, and even our central server, FCC. However, this warning has persisted for some time. Replication to DR1 hasn't been working, however, which I suspect may be related.

Can anyone tell me where to look to figure out why we're getting this warning/error, or how to resolve it?

 

Thank you!

Share this post


Link to post
Share on other sites

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Running rule: IsSiteActive.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Running rule: <IsSiteActive SourceSiteCode="FCC" TargetSiteCode="HQ1" ></IsSiteActive>

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for High_Priority_Site from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Collection_Membership from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Medium_Priority_Site from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for EndpointProtection_Site from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for General_Site_Data from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for CI_Compliance_Rule_Details from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for CI_Compliance_Status_Details_and_History from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Software_Inventory_and_Metering from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Status_Messages from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for MDM_Site from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for MDM_SiteSpecial from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for CFD_Site from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_1 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_2 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_3 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_4 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_5 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_6 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_7 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_8 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_9 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_10 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_11 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_12 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_13 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_14 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_15 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_16 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_17 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_18 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_19 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_20 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_21 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_22 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_23 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_24 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_25 from publisher HQ1.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is failed for replication group Operational_Data.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : RLA detected no re-initialization for the group Operational_Data in last 24 hours.

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : BCP in failed for Operational_Data for tables DrsSendHistorySummary.

5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : All links are initialized between subscriber HQ1 and publisher FCC.

5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : Getting results of rule: IsSiteActive execution

5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : Loading result Xml from rule:IsSiteActive

5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : rule:IsSiteActive has some dependent rules

5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : Working with parent rule:IsSiteActive -> dependent rule:DoesFileReplicationRouteExist

5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : Appending result xml

5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : Rule IsSiteActive result: failed.

5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : Rule: IsSiteActive failed. Stopped running replication link analysis rules.

5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : Completed replication link analysis thread.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.