Simplifying the SCOM 2007 OperationsManager Database move

When upgrading or rescaling your OpsMgr environment you want to move the Operationsmanager database to a brand new server you will find a step-by-step guide in the Operations manager 2007 backup and recovery guide. But why move it the hard way????!?!?!?

There is a much easier, more clickable, approach on moving a database in general so lets use it!

You still have to take some steps to before starting the actual move:

1. Always have a good backup to make sure you can go back to the original working state.
2. Make sure you have a logon account with sufficient permissions to access and move the database.
3. Stop the OpsMgr Config Service, OpsMgr SDK Service, and OpsMgr Health Service for Root Management Servers and OpsMgr Health Service for Management Servers
4. Backup the secure encryption key on the Root Management Server using the SecureStorageBackup.exe utility

Now logon to the SQL server where you want to move you OperationsManager database and open the SQL Server Management studio.

1. Connect to both current OperationsManager SQL server and the target SQL server.
2. Expand the tree until you find the OperationsManager Database en right click the database.
3. Select Tasks and select Copy database.

Walk through the wizard to copy or move the database to the new SQL server.

You still have to edit the registry on the Root Management server and management server to point them to the new OperationsManager Database server by using regedit en changing the following value:

HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Setup DatabaseServerName “NewSQL server name”

Finally start the OpsMgr Config Service, OpsMgr SDK Service, and OpsMgr Health Service for Root Management Servers and OpsMgr Health Service for the Management Servers.

Big advantage compared to the procedure in the backup an recovery guide is you don’t have to set permissions on the database you can copy the endpoints, don’t have to set the enable_broker don’t have to bring down your SQL server and when it fails it will rollback and start the database at it’s original location.

Have fun moving you SCOM environment around!