SCCM SQL Based Replication Guide

16
SCCM SQL Based Replication

New (SQL) based site to site replication model is the most challenging but very interesting part (at least for me) of System Center 2012 Configuration Manager. So, I thought of sharing the some points which are main pillars of SQL replication model. Also find very useful blog posts about SQL based replication from Umair Khan here. This SCCM SQL Based Replication Guide gives you an end to end coverage of issues.

Microsoft ConfigMgr Team released another extensive guide for SCCM ConfigMgr – SQL based related troubleshooting – here

Sudheesh SQL Troubleshooting Guide – here

Key components of new (SQL) based replication model

1. DRS – Data Replication Service

2. SSB – SQL Service Broker

3. RCM – Replication Configuration Management/Monitoring

4. RG – Replication Group

5. Replication Pattern

6. Article Name/s

Also some tips:: how to :: force or re-init site to site replication, verify the site to site replication……

Before going into deep dive, I would like to thank Saud Al-Mishari, Microsoft PFE who was the speaker of MMS 2012 session “CD-B407”. This post is inspired from his session.

DRS – Data Replication Service / SSB – SQL Service Broker

To replicate the data between configmgr sites, Configuration Manager uses Database Replication Service (DRS). The DRS intern uses SQL Server Service Broker (SSB) to replicate data between the sites.

More Details about DRS – TechNet Article

More Details about SSB – SQL Team Article

RCM –  Replication Configuration Management/Monitoring

RCM is a thread of SMSEXEC. As the name suggests, this thread keeps an eye on Replication Configuration and Monitoring. You can refer to rcmctrl.log file to get more details about RCM related activities.

RG – Replication Group

Replication Groups are a set of tables that are monitored and replicated together. Replication groups are segregated and grouped in to THREE Replication Patterns.

To get the full list of RG along with replication schedule – Run the SQL query – Select * from vReplicationData

Each RG (Replication Group) has a unique Replication ID. In CM 2012 RTM release, all the transport is based on DRS.

SQL Based Replication Guide

Replication Pattern

Replication Patterns are group rules based on those, the replication groups are segregated. Three replication patterns are available. More Details about Data Replication – TechNet Blog

SQL Based Replication Guide

a) Global – Global data is anything that is created by administrator. Two way replication between the CAS and Primaries. e.g Package Metadata

image

b) Global_Proxy – This Replication data is based out secondary servers.

image

c) Site – One way replication to the parent site / CAS. e.g Software Inventory/Hardware Inventory

image

Article Name/s

Replication Groups are further divided into Article Names based on ReplicationID . Each RG (Replication Group) has a unique Replication ID.

Run the SQL query to get the list of Article Names “ Select * from vArticleData

e.g  Add_Remove_Programs_64_DATA, Add_Remove_Programs_64_HIST, Add_Remove_Programs_DATA, BoundaryGroup, BoundaryGroupMembers etc…

SQL Based Replication Guide

Force Site To Site Replication / re-init process

You can use <site_Code>.SHA file or Preinst.exe /syncchild, If you want to force site to site replication in SCCM / ConfigMgr 2007. Fortunately/Unfortunately, these methods are NOT going to work in CM 2012 Smile

/SYNCCHILD option to sync child sites has been deprecated. This functionality is
not longer required in System Center 2012 Configuration Manager.

image

If you need to perform a manual sync between the CAS and Primary server, same like dropping .SHA file in the inbox or syncchild…..

You can use the stored procedure (sproc) spDrsSendSubscriptionInvalid with suitable parameter to force the site to site replication.

Word of caution – This will start the re replication between the sites and may cause of lot of Network Traffic…..

EXEC spDrsSendSubscriptionInvalid,,

e.g  EXEC spDrsSendSubscriptionInvalid 'PR1', 'CAS', 'Configuration Data'

image

How to verify the site to site replication from SQL Server Management studio ?

Run the SQL query to check out Transmission Queue for a particular site (in my example it’s site PR1)

SELECT TOP 1000 *, casted_message_body =
 CASE message_type_name WHEN 'X'
 THEN CAST(message_body AS NVARCHAR(MAX))
 ELSE message_body
 END
 FROM [CM_CAS].[sys].[transmission_queue] where to_service_name = 'ConfigMgrDRS_SitePR1'

image

You can verify the transmission logs through vLogs view.

Word of Caution – Avoid using “ select * from vLogs ” query in production environment !!

Select top 1000 * from vLogs order by LogTime desc

You can verify site replication through the rcmctrl.log at CAS and Primary servers.

rcmctrl.log  @ CAS server.

See the log file entry “Created miniJob to send compressed copy of DRS INIT BCP Package to site PR1”

image

rcmctrl.log @ Primary server (PR1)

image

imageSome Random SQL Queries which will help to troubleshoot further on this type of issues. Make sure you have proper SQL backup before updating the SQL DB.

select * from RCM_ReplicationLinkStatus where SnapshotApplied <>1

Select * from Sites where SiteCode in ('CAS','H00')

Update ServerData set SiteStatus = 125 where SiteCode = 'CAS'

Exec spFakeSiteOutOfMaintenance 'CAS'

Select * from rcm_drsinitializationtracking where initializationstatus not in (6,7) order by initializationstatus desc

Exec SpDiagDRS

Update RCM_DrsInitializationTracking set InitializationStatus = 6 where SiteRequesting='H00' and SiteFulfilling='CAS'

Update Sites set Status =1 and DetailedStatus =125 where sitecode = 'CTO'

EXEC spDrsSendSubscriptionInvalid 'H00', 'CAS', 'Replication Configuration'

16 COMMENTS

  1. Looks as if the content was just taken from Saud Al-Mishari sessions on MMS and TechEd. Too bad that you did not mention that.

    • Hello noname – You’ve missed it mate (whoever you may)… And if you dont have time to read the full post then it’s better NOT to read…. Half information is very dangerous……I think, you didn’t read the FULL post 🙂 It’s not very good thing to hide the identity….

  2. Anoop,

    In trying to fix a replication problem, I executed EXEC spDrsSendSubscriptionInvalid , , on our CAS and Primary:

    http://blogs.msdn.com/b/minfangl/archive/2012/05/16/tips-for-troubleshooting-sc-2012-configuration-manager-data-replication-service-drs.aspx

    At this point, I’m showing that the replication link has failed – The two replication groups that are failing are “Configuration Data” and “CI_Compliance_Rules_Details”, which were the two replication groups that I expired with the above command.

    Do you have any ideas what is going on at this point?

  3. EXEC spDrsSendSubscriptionInvalid ‘PR1′, ‘CAS’, ‘Configuration Data’
    When I run it, the replicationgroup degraded. How to fix it?Thanks!

  4. Hi
    I am facing an SCCM DRS issue in production environment . I was hoping if anyone can provide me an insight on how to troubleshoot it . we have 1 sccm cas & 1 sccm primary in hierarchy, Recently we did SQL databases migration for both , from an dedicated SQL server to CAS & Primary server respectively . Since then the sccms are in read only mode . database replication link between them have failed , upon restarting the SSB queues in SQL & reinitializing the replication for failed replication groups (global data) database replication link in cas became active for couple of hours but then again failed during this time child to parent link status in primary for still displaying failed .

    Additional details :
    Out of 34/54 (global data) replication groups in SQL 3 have failed , around 10 are degraded rest are active but showing an earlier date when sql was not migrated .

    Thanks

      • Is it readonly mode or maintenance mode?
        Have you tried Replication link analyser? If so, what is the result you’re getting ?
        RCM inbox folder is having backlog ?
        Also, check the status of the site using following query … Select * from Sites where SiteCode in (‘CAS’,’PRI’)

  5. Hi Anoop
    Super article. I have an issue for database replicating from Primary to CAS in a single primary and CAS scenario for both global and site data. From CAS to primary replication is working fine.
    When checked the vlogs the description for all replication group is “Not sending changes to sites CAS, since last 2 syncs to these sites have not completed” Kindly help me since iam troubleshooting this issue for long days

  6. We have CAS and 5 primary site setup.there is no issue with 4 primary sites to CAS replication issue.but 1 primary which is managing more than 80000 clients having replication issue with CAS. it is looking fine in weekend but in weekdays is almost showing failed status. Prompt reply will be appreciated.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.