Rickey Whitworth's Blog

Planning to move SCOM database to new server, here are the notes.

Updated: May 22, 2009

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

After the initial deployment of Microsoft System Center Operations Manager 2007, you might need to move the Operations Manager database from one Microsoft SQL Server-based computer to another.

SQL Server 2005 and SQL Server 2008 support the ability to change the location of the data files and of the log files between SQL Server-based computers, between instances on the same SQL Server-based computer, and different volumes on the same SQL Server-based computer. For more information about using this function in SQL Server, see the SQL Server documentation (http://go.microsoft.com/fwlink/?LinkId=93787).

The high-level steps of moving the OperationsManager database are as follows:

1. Back up the OperationsManager database.
2. Uninstall the OperationsManager database.
3. Delete the Operations Manager database.
4. Restore the OperationsManager database.
5. Update management servers with the new database server name.
6. Update the Operations Manager database with the new database server name.
7. Update the Operations Manager database logins on the new database server. Ensure that for the root management server, the SDK Account and the Action Account are included in the logins and that they have appropriate permissions. If reporting is installed, ensure that the Data Warehouse Action Account has appropriate permissions.
8. Set ENABLE_BROKER if needed.
9. Verify that the move is successful by ensuring that the console is displaying valid data.

How to Move the OperationsManager Database in Operations Manager 2007

Random Posts