How to Recover Restore SCCM CAS Server using SQL Backup ConfigMgr. The key question is, Do you really need to take the entire site server backup (Backup through maintenance task/s), or is a SQL Database backup just enough?
Maybe we can reduce the backup cost by using SQL backup and show it as a new saving for the CM 2012 implementation.
Even though we use a site database manually recovered as a site database recovery option, the CAS server retrieves the global and global proxy data from the primary site server database.
- How to Recover SCCM CAS Server Database
- How to Expand SCCM CB Standalone Primary Server with CAS Server Configuration Manager ConfigMgr
- Download and Install SCCM 2012 R2 CU2 Cumulative Update 2 on CAS Primary Servers
Table of Contents
Recover Restore SCCM CAS Server using SQL Backup
Before starting this exercise, I took the SQL backup of the site Database CM_CAS and restored it using SQL Management Studio. (This is the manual method that I’ve used to recover SQL).
Read more details about Backup and Recovery Options through TechNet.
There are no major changes in the recovery process that were published last month – Recover a CAS Server without using backup, other than step 3. Rest everything remains same.
3. Site Server and Database Recovery: options are available in the following wizard.
Select “Use a Site Database that has been manually recovered.”
The option mentioned above is used when you’ve already recovered the ConfigMgr site database but must complete the recovery process. Configuration Manager can recover the site database from the Configuration Manager backup maintenance task or from a site database backup that you start by using another process.
After restoring the site database using a method outside Configuration Manager, you must run Setup and select this option to complete the site database recovery. When you have a hierarchy, the changes that were made to the site database after the last site database backup are retrieved from the central administration site for a primary site or from a reference primary site for a central administration site.
When you recover the site database for a stand-alone primary site after the last backup, you lose site changes.
If you want to know more about primary server recovery methods, read my posts Part 1 and Part 2.
I successfully recovered my Central Administration Site (CAS) using SQL backup. Note that all these are done in the LAB environment. For production environments, we need to perform more testing before taking any actions/changes.
We are on WhatsApp. To get the latest step-by-step guides and news updates, Join our Channel. Click here –HTMD WhatsApp.
Author
Anoop C Nair has been Microsoft MVP from 2015 onwards for 10 consecutive years! He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is also a Blogger, Speaker, and leader of the Local User Group Community. His main focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career, etc.