Compartir a través de

SCOM 2012 DataBase Movement

  • Artículo

Hello,

 

I wanted share the steps for successful movement of SCOM 2012 OPsMgr and DW databases movement to the new SQL server.

 

 

You can follow the below the below articles for OpsMgrDB and OpsMgrDW database movements.

 

https://technet.microsoft.com/en-us/library/hh278848.aspx

https://technet.microsoft.com/en-us/library/hh268492.aspx

 

  • Apart from this, you will also have to edit the following registry settings on each management servers. I have seen customers are missing to edit this registry key and getting issues.

 

======================================================================================================

  • On each Management you need to update the following registry keys.

 

              a. Log on to the management server with Administrator permissions.

              b. Click Start, select Run, type regedit in the Open box, and then click OK to start Registry Editor.

     c. Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCenter\2010\Common\Database, double-click the name DatabaseServerName, and then change the value to the name of the SQL Cluster that will be hosting the OperationsManager Database, and then click OK to save your change.

 

  (If you are using a named instance of SQL Server, be sure to use the ServerName\Instance name format.)

 ======================================================================================================

 

Reference :

Using SQL Server 2012 Always On Availability Groups with System Center 2012 SP1 - Operations Manager

https://technet.microsoft.com/en-us/library/jj899851.aspx

 

 

 

======================================================================================================

On each Management you need to update the registry keys.

 

a. Click Start, select Run, type regedit in the Open box, and then click OK to start Registry Editor.

 

b. Under HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Setup, double-click the value DatabaseServerName, and then change the value to the hostname of the SQL Server-based computer now hosting the OperationsManager database. If you are using a named instance of SQL Server, be sure to use the ServerName\Instance name format.

 

 c. Click OK.

 

d. Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup\DataWarehouseDBServerName - (change this to the new SQL server hosting the DW).

 

  • If your SQL server is not using the default port, then you need to upadte the registry as below. DatabaseServerName – HostName\InstanceName,<PortNumber>

 

======================================================================================================

 

 

Thanks

Santosh Killekar - Support Engineer (System Center)

 

Disclaimer: This posting is provided "AS IS" with no warranties and confers no rights.