Configuration Manager 2012 R2 disaster recovery is a complex process. It requires sufficient knowledge of the Configuration Manager Product & dependent components. This document describes the steps to recover a full Configuration Manager 2012 R2 hierarchy in case of disaster. This document also describes the steps to recovery either CAS or Primary sites as well as additional steps that Configuration Manager Administrators should follow in order to restore a Configuration Manager Hierarchy or Sites without data loss. This document also provides some helpful troubleshooting tips.
At a higher level, there are the following few steps described below to recover an entire hierarchy in the event of disaster. Please note that the steps are different for recovering an entire hierarchy and individual site servers such as CAS or Primary sites. Please refer to appropriate sections within this document to recover appropriate site servers. The approximate time noted below in each of the tasks may vary significantly as there are many factors involved when recovering an entire hierarchy so use this timing as an example ONLY.
- Collect CAS & Primary Site Information (~1 hour) In this step, collect & document all the necessary information required from the existing hierarchy. This task should be followed regularly whenever there are updates/changes at the site level so that it will save time at the time of disaster recovery.
- Backup Sites – CAS & Primary (~3 hrs.) This section describes backup options.
- Recover CAS Site (~3 to 48 hrs.) This section provides the steps to recover the CAS Site server. Global data can be recovered within 3-4 hours but for site data it can take up to 48 hours.
- Recover Primary Site(s) (~3 to 48 hrs.) This section provides the steps to recover Primary Site servers. Global data can be recovered within 3-4 hours but for site data it can take up to 48 hours. Recover from supplemental backups (~2 hrs.)
- This section describes the steps to recover the additional components of Configuration Manager.