High-Level Restore Guidelines in Operations Manager 2007

  • Article

Applies To: Operations Manager 2007 R2, Operations Manager 2007 SP1

Use the following table for information about possible failure scenarios and the general steps required to restore operations and data in that scenario.

General Restore Steps

Failed Component General Restoration Steps Required Backups

Management server

With additional management servers:

  1. Repair the server.

  2. Reinstall the Operations Manager management server on the repaired server.

  3. After the failed management server is restored, Operations Manager agents will eventually resume reporting to that management server.

Without additional management servers:

  1. Configure the root management server (RMS) as the primary management server in the management group.

  2. Install a new management server in the management group. Use the computer running Microsoft SQL Server that is hosting the OperationsManager database, and use the same action account that was previously defined.

  3. Configure the newly installed management server as the primary management server.

none

Root management server

Clustered:

  • Repair the failed server, and re-connect to the cluster.

Not clustered:

  1. Promote an existing management server to root management server.

  2. Repair the failed server.

  3. Reinstall the Operations Manager management server on the repaired server.

  4. Demote the temporary root management server to management server.

  5. Promote the repaired server to root management server.

Root management server encryption key

Data warehouse server/Operations Manager reporting server (assumes the OperationsManager database is intact

Clustered:

  1. Repair the failed server, or reinstall SQL Server and reconnect to the cluster.

  2. If needed, configure all management servers to point to the repaired server.

Not clustered:

  1. Repair the server as needed.

  2. Restore the OperationsManager database.
  • OperationsManager database

  • Root management server encryption key

OperationsManager database
  1. Reinstall the Operations Manager reporting server component if needed.

  2. Restore the OperationsManager database.

If log shipping has been implemented:

  • Rebuild and restore the database.
  • OperationsManager database

  • root management server encryption key

Operations Manager reporting server

Clustered:

  1. Reinstall the Operations Manager reporting server if needed.

  2. Restore the OperationsManagerDW database, and the ReportServer and ReportServerTempDB databases if needed.
  • OperationsManagerDW database

Gateway server
  1. Repair the server if needed.

  2. Reinstall the Operations Manager gateway server if needed.

None

Computer hosting Operations console
  1. Repair the computer.

  2. Reinstall the Operations Manager console.

None

OperationsManagerAC (Audit Collection) database
  1. Repair the Operations Manager Audit Collection Services (ACS) database server if needed.

  2. Reinstall SQL Server if needed.

  3. Reinstall the Operations Manager ACS database component if needed.

  4. Restore the Audit Collection database.

Audit Collection database

ACS Collector Server

Do either of the following:

  1. Repair the ACS Collector server if needed.

  2. Install the ACS Collector on another management server in the management group if needed.

  3. Install another management server in the management group and install the ACS Collector if needed.

None