SCCM High Availability Redundancy DR Options ConfigMgr. In this post, I just wanted to provide some reference posts.
I have also added my latest and quick notes on SCCM High Availability, Redundancy, and Disaster Recovery. There are loads of improvements in SCCM CB in terms of HA (High Availability), Redundancy, and Disaster Recovery.
SCCM High Availability Redundancy DR Options ConfigMgr
SCCM 1806 onwards, SCCM primary server passive server options are available. Arnab explained this primary server passive option feature with a detailed blog post.
SCCM CB High-Availability (Quick Note)
- Install 2 MPs instead of 1 MP
- Install 2 Dps instead of 1 DP
- Install 2 SUPs instead of 1 SUP
- Use SQL DB cluster
- All site server components can be offloaded to separate server for high availability
- Primary server high availability options are still not there in SCCM production version. But Primary server DR/HA options are available for SCCM CB technical preview versions.
Excellent post on HA from Peter Daalmans:: High availability options in ConfigMgr 2012
High Availability-related post by MadOne45 talks about multiple improvements in CM2012 like having multiple SMS Providers, Management Points, SQL clustering, etc. More details are in the following link.
What are the high availability options for ConfigMgr 2012?
You can see useful thoughts on Redundancy by Brian Mason in the following link. Does he talk about the real-world experience of reducing the impact by spitting the site server roles? Etc. Note: See the comments part for more details.
Planning for some redundancy in CM07 or CM12?
Some interesting Questions related to Disaster Recovery, through the TechNet Forum thread and very useful answers, are from Jim Dempsey [MSFT].
1. Can you now restore the DB to a server with a different name in a DR situation?
ANS – No, you cannot restore your site database to a different server, but you can move the database to a different server after the recovery is finished. The ability to restore to a different SQL Server/instance is on our list to investigate for a future release, but no committed plans at this point.
2. What significant changes are there in DR from 2007 to 2012
There are many changes, so I encourage you to read through the documentation. Some notable changes are as follows:
- There is no longer a separate repair wizard that you have to run after running Setup to reinstall the site. Instead, recovery is an option integrated into Setup.
- You now have the ability to recover data from another site in your hierarchy if you don’t have a good backup (doesn’t apply to a stand-alone primary environment).
- Backup still backs up some registry keys and files (e.g. logs, inboxes), but recovery doesn’t use anything other than the database.
- Status messages for backup failure have been improved, including in-console alerts when your backup fails.
3. What is the best high availability solution?
That’s a loaded question. What’s best depends on your specific environment, budget, and business requirements. Again, I encourage you to read the documentation on this. A couple of things that have changed from ConfigMgr 2007 are as follows:
- We no longer support NLB for management points. Instead, we allow you to simply deploy multiple MP’s and we will automatically load-balance for you.
- We now allow you to install multiple SMS Provider roles per site (must be installed on separate servers).
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…