MS System Center Operations Manager 2007 SQL Log

MS System Center Operations Manager 2007
SQL Log Shipping – Part II
Purpose
The purpose of this document is to provide a guide on how to configure and use the log shipped
secondary database server for Microsoft System Center Operations Manager 2007.
This guide has only been tested in a single management group environment without ACS and only
covers the Operations Manager database, not the data warehouse.
Author: David Allen
http://www.aquilaweb.com
Preparing Secondary Database
Restore
To enable your secondary database for usage, it first needs to be restored with recovery.
1. Open the SQL Server Management Studio.
2. Connect to the secondary SQL server.
3. Click 'New Query'.
4. Type: RESTORE DATABASE <dbname> WITH RECOVERY
5. Click 'Execute'
6. Confirm the restore was successful by checking the Messages tab.
Security
Confirm that all the required accounts have logins and appropriate permissions on the secondary
database server. The accounts used can differ depending on set up but here are a few to consider
with their associated database roles:
Account
Operations Manager DB role membership
SDK Account
configsvc_users, db_datareader, db_datawriter,
db_ddladmin, sdk_users
Action Account
db_datareader, db_datawriter, db_ddladmin,
dbmodule_users
Data Warehouse Action Account (for
Reporting)
db_datareader, dwsynch_users
Author: David Allen
http://www.aquilaweb.com
SQL Broker
The SQL Broker is used by Operations Manager to perform discoveries and run tasks. The steps
below outline how to check whether SQL broker is enabled and how to enable if it is not.
1. Open the SQL Server Management Studio.
2. Connect to the secondary SQL server.
3. Click 'New Query'.
4. Type:
SELECT is_broker_enabled FROM sys.databases WHERE name='<dbname>'
5. Click 'Execute'. If the value returned is 1 then SQL Broker is already enabled, if not a 1
follow the next 5 steps.
6. In the New Query window delete previous query, enter the query below and execute:
ALTER DATABASE <dbname> SET SINGLE_USER WITH ROLLBACK
IMMEDIATE
7. Enter this query and execute:
ALTER DATABASE <dbname> SET ENABLE_BROKER
8. Kill all connections to the database and close the SQL Server Management Studio.
9. Re-open the SQL Server Management Studio.
10. Connect to the SQL server.
11. Click 'New Query'.
12. Type the following query and execute:
ALTER DATABASE <dbname> SET MULTI_USER
13. Follow steps 4 & 5 again to confirm SQL Broker is enabled.
Author: David Allen
http://www.aquilaweb.com
Updating System Center Operations Manager
Configuring the Management Server(s)
All management servers and the root management server must be updated to reference the
secondary SQL server.
Warning: This change is made by updating the registry
1. Log onto management server with an administrator account.
2. Open Registry Editor
○
Click Start and select Run
○
Type regedit and click OK
3. Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations
Manager\3.0\Setup. Right click DatabaseServerName, select Modify, type the new server
name in the Value data field and click OK.
Note: If using a named instance this also needs to be specified in the DatabaseServerName
string, for example: <servername>\<instancename>
4. Close Registry Editor and repeat on all remaining management servers and the root
management server.
After all management servers have been updated the OpsMgr Health Service requires restarting on
all management servers to read the registry change. The OpsMgr Config Service and OpsMgr SDK
service will also need restarting on the root management server.
Configuring the Operations Manager database
The last action is to configure the SQL server name within the Operations Manager database.
1. Open the SQL Server Management Studio.
2. Connect to the new SQL server.
3. Click 'New Query'
Author: David Allen
http://www.aquilaweb.com
4. Type:
USE <dbname>
UPDATE [dbo].[MT_ManagementGroup]
SET [SQLServerName_6B1D1BE8_EBB4_B425_08DC_2385C5930B04] =
'<servername\instancename>'
5. Click 'Execute'
6. Confirm the update was successful by checking the Messages tab.
Once all the above steps have been completed, open the Operations Manager console and confirm
correct operation.
Author: David Allen
http://www.aquilaweb.com