Considerations for High Availability and Disaster Recovery


Updated: May 13, 2016

Applies To: System Center 2012 R2 Operations Manager, System Center 2012 - Operations Manager, System Center 2012 SP1 - Operations Manager

This section describes key concepts to consider when designing for disaster recovery. Using multiple management servers and the concept of resource pools, it is possible to easily set up for successful failover scenarios.

Multiple Management Servers and Distributed Deployment

You should always have two management servers in ANY environment. A second management server allows for failover and easy restore, and a second management server can take on the load if one fails. All management servers are members of the All Management Servers Resource pool, which balances the monitoring load of your management group as new management servers are added, and provides automatic failover for monitoring. The impact of failure of a management server in a distributed environment is minimized, but it increases the workload on additional management servers in the management group until the failed management server is restored. See Distributed Deployment of Operations Manager in the Deployment Guide for complete details.

You should always keep a backup of your operational database and data warehouse databases. For information about scheduling regular backups of the Operations Manager databases, see How to Schedule Backups of System Center 2012 - Operations Manager Databases.

You must keep SDK services running on all management servers.