As your organization grows and changes, you perform many of the following activities in Secure Configuration Manager:
Customize settings in Core Services
Add agents and endpoints to the asset map in the console
Run reports against your IT assets
Update security knowledge through AutoSync and custom security checks
Create, modify, and delete user profiles
Each of these activities affects the information stored in the Secure Configuration Manager database, Core Services, and the consoles. If your organization experiences a hardware or software problem, you could lose these incremental revisions. Sometimes, you can reinstall software on a server. On the other hand, a catastrophic failure might require you to restore backed up databases and Secure Configuration Manager components at a different site, and then reapply customized settings.
In general, organizations create a business continuity plan to ensure functionality during and after a disaster. Organizations demonstrate different levels of resilience when responding to and recovering from catastrophic events. Most business continuity plans account for four facets of organizational resilience: preparedness, protection, response, and recovery. This chapter helps you prepare for an infrastructure failure and determine whether restoring that infrastructure can be completed within company goals for an acceptable recovery time.