ConfigMgr 2007 and 2012 RTM versions don’t support the recovery of the secondary site. However, Configuration Manager 2012 SP1 RTM officially supports the restore. In ConfigMgr 2007, this is not a supported option.
Hence, the communities always suggest the fresh installation of secondary sites and redistribution of packages.
NOTE! – ConfigMgr Current Branch Secondary Site Recovery Guide – Recover Secondary Site Fix SCCM Secondary Server Recovery Failed Issue | ConfigMgr
But in a real-world scenario with tight SLA and PCK files availability at remote site/s, this option may give SCCM admins loads of problems even if we go with the package preload option using ‘PreloadPkgOnSite.exe.’
In ConfigMgr 2012 SP1, If the content library is available then the recovery process itself validates and uses the content during the recovery process. This means there is no need to perform some ‘additional’ activity to get back the full functionality of the site server.
One another interesting point is that back in SMS 2003, the recovery of the secondary site is supported.
Points to be noted before the start of recovery activity:-
Recover a site server using the “Recover Secondary Site” action from the Sites node in the Configuration Manager Admin console.
CM 2012 SP1 secondary site doesn’t use ConfigMgr backup file to restore. This site will reinitialize the data from Parent Primary Server.
If the content library is available at the time of recovery then the secondary site will validate the contents and use them. Otherwise, need to redistribute the packages.
The Restoration and Validation process may take time depending upon the size of the DB and the content library size.
The secondary server should have the ‘same’ name, FQDN, installation path, security rights and this should be installed with all the prerequisites for a successful restoration.
Unlike the original installation, the ConfigMgr Secondary site won’t install the SQL Express version as part of recovery. If it’s not installed, already, then need to install it manually before starting the recovery process. Should have the same version and instance name of SQL to complete the recovery process.
More Details about the recovery of the SCCM 2012 SP1 Secondary site are here !!
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…