SCCM ConfigMgr 2012 Site to Site replication & SQL Replication Guide
Key Components - Site Replication Model
New (SQL) site to site replication model is the most challenging part of System Center 2012 Configuration Manager. Main pillars of SQL replication model.
Key components of new (SQL) replication model
· DRS – Data Replication Service
· SSB – SQL Service Broker
· RCM – Replication Configuration Management/Monitoring
· RG – Replication Group
· Replication Pattern
· Article Name/s
Pillars of SQL replication model
u DRS – Data Replication Service / SSB – SQL Service Broker
u 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.
u RCM - Replication Configuration Management/Monitoring
u RCM is a thread of SMSEXEC. This thread keeps an eye on Replication Configuration and Monitoring.
u RG – Replication Group
u Replication Groups are a set of tables that are monitored and replicated together. Replication groups are segregated and grouped in to THREE Replication Patterns.
u 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.
u Replication Pattern
u Replication Patterns are group rules based on those, the replication groups are segregated. Three replication patterns are available.
u a) Global – Global data is anything that is created by administrator. Two way replication between the CAS and Primaries. e.g Package Metadata
u b) Global_Proxy – This Replication data is based out secondary servers.
u c) Site – One way replication to the parent site / CAS. e.g Software Inventory/Hardware Inventory
u Article Name/s
u Replication Groups are further divided into Article Names based on ReplicationID . Each RG (Replication Group) has a unique Replication ID.
u 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
Force Site to Site Replication / re-init process
u EXEC spDrsSendSubscriptionInvalid
u e.g EXEC spDrsSendSubscriptionInvalid ‘PrimarySitecode′, ‘CentralSitecode’, ‘Configuration Data’
u Verifying site replication through SQL Server Management Studio
u 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′