Move SCOM 2012 Database to another server

Use the following procedure to move you OperationsManager Database to a new SQL server.

I’m assuming that you have the new SQL server prepared with the exact same installation as the currently used server.

This process includes a downtime for the SCOM server so be prepared.

Please perform backup to the configurations before doing anything. We’re going to modify several keys in the registry and a configuration file located on the SCOM 2012 server. Please backup them before doing any changes!

  1. Stop SCOM services – System Center Management, System Center Data Access and System Center Management Configuration

Stop-Service omsdk
Stop-Service HealthService
Stop-Service cshost

  1. On the original SQL server backup the Database (OperationsManager) using the SQL Management Studio.
  2. Once the backup is completed copy the BAK file to the new SQL server to a local drive.
  3. Restore the OperationsManager Database using SQL Management Studio.

That is the procedure to move the SCOM 2012 Database to a new server.

Now we need to reconfigure the SCOM 2012 server to connect to the new SQL server.

  1. Change the SCOM 2012 ConfigService.config configuration file located in the following folder:

%ProgramFiles%\System Center 2012\Operations Manager\Server\

Locate the <Category> tag named “Cmdb” , and change the ServerName value to point to the new server.

Locate the <Category> tag named “ConfigStore”, and change the ServerName value to point to the new server.

  1. Open the registry on the SCOM 2012 and change the following key appropriately:

HKLM\SOFTWARE\Microsoft\System Center\2010\Common\Database

Double click DatabaseServerName and paste in the new value pointing to the new server

** Please note, if you have installed the new SQL with the default instance name then you need to enter only the servername. If you have installed the SQL with a named instance, you will have to enter the servername\instancename.

Now the SCOM 2012 server knows about the new SQL server that holds its DB.

The next step is to modify some properties on the new SQL server:

  1. Open SQL Server Management Studio
  2. Expand Databases, OperationsManager, and Tables .
  3. Right-click dbo. MT_Microsoft$SystemCenter$ManagementGroup, and then click Edit Top 200 Rows
  4. Change the value in the SQLServerName_<GUID> column to reflect the name of the new SQL Server-based computer.
  5. Click on update to reflect the changes
Change OperationsManager ManagementGroup server name

Change OperationsManager ManagementGroup server name

  1. Right-click dbo. MT_Microsoft$SystemCenter$OpsMgrDB$AppMonitoring , and then click Edit Top 200 Rows .
  2. Change the value in the MainDatabaseServerName_<GUID>, column to reflect the name of the new SQL Server-based computer.
  3. Click on update to reflect the changes
Change OperationsManager AppMonitoring server name

Change OperationsManager AppMonitoring server name

** Please note, if you have installed the new SQL with the default instance name then you need to enter only the servername. If you have installed the SQL with a named instance, you will have to enter the servername\instancename.

The next step is to make sure that all the SQL Logins are configured correctly.

The Logins should have been maintained during the restoration of the Database on the new SQL server, but I suggest that you review the permissions on the old SQL server and match them to the new SQL server.

Next step is to reconfigure some settings on the new SCOM 2012 Database.

  1. Execute the following commands on the new SQL server

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

  1. Make sure the SQL Server Broker Service is enabled by running the following command:

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

The output should be ‘1’. If not, run the following commands to enable it:


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

 

That’s it!

You can now start the SCOM 2012 services but my suggestion is to reboot the SCOM 2012 server. The services should start automatically and all should be now working!

 

Incoming search terms:

  • 2012 move
  • moving report server instance scom 2012
  • scom database configuration
  • SCOM 2012 R2 reporting serer moved
  • scom 2012 r2 move database
  • scom 2012 r2 change to new database server step by step
  • scom 2012 powershell list db server for scom
  • scom 2012 operation manager dw sql permissions
  • scom 2012 move
  • scom 2012 r2 sql named instance