Today I will be sharing very details view of the replications.  In Last Article We have seen about SCCM Replication Failure : The Replication Group re-initialization stuck between ConfigMgr Central Site and Primary Sites  .   Let discuss more about All global and site data replications are failed from Primary to CAS and vice versa, follow the below steps to fix the issue.

Issue: If all global and site data replications are failed from Primary to CAS and vice versa, follow the below steps to fix the issue.

Note: Use these resolution steps only if all replications are still showing as failed after you perform below steps

To reinitiate site data, run on CAS

        EXEC spDrsSendSubscriptionInvalid <ReceivingSiteCode/Subscriber>, <SendingSiteCode/Publisher>, <ReplicationGroupName>

        Ex: EXEC spDrsSendSubscriptionInvalid 'PE1', 'CAR', ‘CI_Compliance_Rule_Details'

To reinitiate Global data, run on Primary

EXEC spDrsSendSubscriptionInvalid <ReceivingSiteCode/Subscriber>, <SendingSiteCode/Publisher>, <ReplicationGroupName>

Ex: EXEC spDrsSendSubscriptionInvalid 'CAR', 'PE1', ‘Configuration Data’

Steps to validate:

Run spdiagdrs and verify if any messages are pending in outgoing messages queue and see which DRS replications are failed for global and site.

Run below queries on CAS and primary DB to see if any backlogs.

Select * from DrssendHistory where ProcessedTime is NULL

Select * from RCM_ReplicationLinkStatus where snapshotapplied <>1

select * from sys.transmission_queue order by enqueue_time desc

If you see any transmission backlogs run the below query to cleanup backlogs

declare @conversation uniqueidentifier while exists (select 1 from sys.transmission_queue ) begin set @conversation = (select top 1 conversation_handle from sys.transmission_queue ) end conversation @conversation with cleanup end

Resolution:

Global data replication Re-initiation from child site (Primary site)

Next Step is re-initiate failed global DRS data one by one from Primary server

Create a .PUB file in rcm inbox folder on primary site for failed global data group

Ex: Upgrade Assessment.PUB

Verify rcmctrl.log for data processing in primary server

You can check the percentage initialization with below query.

Select * from RCM_DrsInitializationTracking where InitializationStatus not in (6, 7) order by createdtime desc?

        Once the existing data group replication has completed you can re-initiate other global data groups one by one.

        Note: Do not re-initiate two data groups at time, we’ll need to do it one at a time and wait for first one to be completed

       Site data replication Re-initiation from CAS:

       Post all Global data replication is success start re-initiate site data replication 

       Create a .PUB file in CAS server rcm inbox folder for the failed site data group 

Ex: <Site Replication Group Name>-<Child Site code (Primary)>.PUB

        Verify rcmctrl.log for data processing in primary server   

        You can check the percentage initialization with below query.

        Select * from RCM_DrsInitializationTracking where InitializationStatus not in (6, 7) order by createdtime desc?

At 41 percentage you can see some folders created on rcm box

Once the existing Site data group replication has completed you can re-initiate other failed site data groups one by one.

        Note: Do not re-initiate two data replication groups at a time, do one replication group at a time and wait for first one to be completed.Replication process will completely depend on size of your DB tables.

        Happy Learning :)

Tejeswara Reddy

Email: [email protected], [email protected]

Facebook https://www.facebook.com/Hiraniconfigmgr-120189361980772/

Follow us: https://www.linkedin.com/in/hiraniconfigmgr 

Twitter: https://twitter.com/hiraniconfigmgr