Monday, 18 April 2016

Step by Step Guide to recovery or Move Operations Manager Database from Old Server to New Server

Step by Step Guide to Move Operations Manager Database from Old Server to New Server




  • Step1:Stop Operation Manager services
On all the management servers in the management group, stop the Operations Manager services:
* System Center Data Access
* System Center Management
* System Center Management Configuration

  • Step2: Create Backup of Old OperationManager Database and move it to new Server

* On the original operational database server, use Microsoft SQL Server Management Studio to create a full backup of the operational database. The DB name is OperationsManager.
* Copy the backup file to a local drive of the new database server.

  • Step3: Restore the operational database on the new server

* Use Microsoft SQL Server Management Studio to restore the operational database.In this step, you can change the name of the database and choose the file location.
* Make the database online.verify that the database is online.

  • Step4:Update the registries and configuration files on the management servers

* Do these steps on each management server in the management group:
* Update the registry to refer to the new SQL Server-based computer.
*Log on to the management server with Administrator permissions.
* Click Start, select Run, type regedit in the Open box, and then click OK to start Registry Editor.
* Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup.
* For each of the following keys, double-click the name, change the value to the hostname of the SQL Server-based computer now hosting the operational database, and then click OK to save   your changes.
  1. DatabaseName
  2. DatabaseServerName
* Close the Registry Editor.
On each management server, edit the following file:

* %ProgramFiles%\System Center 2012\Operations Manager\Server\ConfigService.config 

* In the <Category> tags named “Cmdb” and “ConfigStore”, change the value for ServerName to the name of the new SQL server.

Step5: Update Operations Database to point to new server

* Open SQL Server Management Studio.
* Expand Databases, OperationsManager, and Tables.
* Right-click dbo.MT_Microsoft$SystemCenter$ManagementGroup, and then click Edit Top 200 Rows.
* Note If the SCOM was installed by upgrading from SCOM 2007 instead of by using the SCOM 2012 install media, you need to modify the dbo.MT_ManagementGroup table instead of the   dbo.MT_Microsoft$SystemCenter$ManagementGroup table.
* Change the value in the SQLServerName_6B1D1BE8_EBB4_B425_08DC_2385C5930B04 column to reflect the name of the new SQL Server-based computer.
  Save the change.

Step6: On the new server, update the operational database with the new database server name to specify the location of the Application Performance Monitoring tables

* Open SQL Server Management Studio.
* Expand Databases, OperationsManager, and Tables.
* Right-click dbo.MT_Microsoft$SystemCenter$OpsMgrDB$AppMonitoring, and then click Edit Top 200 Rows.
* Change the value in the MainDatabaseServerName_5C00C79B_6B71_6EEE_4ADE_80C11F84527A column to reflect the name of the new SQL Server-based computer.
* Save the change.

Step7: Update security credentials on the new server hosting the operational database

Expand Security, expand Logins, and then do the following:

* Add the data writer account. For more information, see How to Create a SQL Server Login.
* Add the action account.
* Add the Data Access Service (DAS) computer account, using the form “domain\computername$”.

For the DAS computer account, add the following user mappings:
* ConfigService
* db_accessadmin
* db_datareader
* db_datawriter
* db_ddladmin
*db_securityadmin

Step8: Execute these SQL commands on new Operations database instance:

 sp_configure ‘show advanced options’,1
 reconfigure
 sp_configure ‘clr enabled’,1
reconfigure
sdk_users
sql_dependency_subscriber


Run the following SQL query:

SELECT is_broker_enabled FROM sys.databases WHERE name='OperationsManager'

If the result of this query was an is_broker_enabled value of 1, skip this step. Otherwise, run the following SQL queries:

ALTER DATABASE OperationsManager SET SINGLE_USER WITH ROLLBACK IMMEDIATE
ALTER DATABASE OperationsManager SET ENABLE_BROKER
ALTER DATABASE OperationsManager SET MULTI_USER

  • Step9: Start Operation Manager services

On all the management servers in the management group, start the Operations Manager services:
* System Center Data Access
* System Center Management
* System Center Management Configuration

No comments:

Post a Comment