System Center 2012 R2 – High Availability: Operations Manager

System Center 2012 R2 – High Availability: Operations Manager

To continue series about how to implement each product of System Center 2012 R2 suite as highly available and how to backup & recover them. In this article, we will focus on System Center Operations Manager (also known as OpsMgr and SCOM).

Unlike OpsMgr 2007, you can natively maintain availability and redundancy for your management servers in any management group. System Center Operations Manager 2012 R2 is composed of these majors roles and services:

  • Management Group: The management group is the basic unit of functionality. At a minimum, a management group consists of a management server, the operational database, and the data warehouse database.
  • Management Server: The management server is the focal point for administering the management group and communicating with the database. Depending on the size of your computing environment, a management group can contain a single management server or multiple management servers gathered in a resource pool.
  • Resource Pool: A resource pool is a collection of management servers used to distribute work amongst themselves and take over work from a failed member.
  • Operational Database: The operational database is a SQL Server database that contains all configuration data for the management group and stores all monitoring data that is collected and processed for the management group. The operational database retains short-term data, by default 7 days.
  • Data Warehouse Database: The data warehouse database is a SQL Server database that stores monitoring and alerting data for historical purposes. Data that is written to the Operations Manager database is also written to the data warehouse database, so reports always contain current data. The data warehouse database retains long-term data.
  • Operations Console: The operations console lets you monitor, author, report and administrates your SCOM infrastructure.

In order to make your Operations Manager infrastructure highly available you will have to:

  • Install multiple management servers and gather them into dedicated resource pools.
  • Make Data Access Service highly available using network load balancing.
  • Install the operations web console on multiple web servers in a load-balanced configuration.
  • Deploy both operational database and data warehouse database on a dedicated SQL Server Failover Cluster.

Backing up Operations Manager involves backing up the following elements (DPM supports backup needs):

  • Operational database
  • Data warehouse database
  • Audit Collection Services (ACS) database (if deployed)
  • Custom Management Packs (manual actions or script required)
  • Custom report definition files
  • Computer certificates

Microsoft recommends the backup schedule listed in the table below for an Operations Manager deployment (You can learn more about backup and disaster recovery in Operations Manager here).

In order to recover a Management Server on your Operations Manager infrastructure:

  • Build a new server, ensuring that it meets the minimum supported configurations, and use the same name that was given to the failed management server.
  • Restore the operational database and data warehouse database, if required.
  • On the new server, open a Command Prompt window by using the Run as Administrator option, and run the following command (this process only recovers the management server):

If you have to recover a management server when all management servers in the management group have failed, then you must also reconfigure the Run as Accounts.

2 thoughts on “System Center 2012 R2 – High Availability: Operations Manager

Leave a Reply

Your email address will not be published. Required fields are marked *