Archive

Posts Tagged ‘SQL’

Upgrading Operations Manager Reporting Server to Windows 2008 R2 and SQL 2008

23/05/2010 Leave a comment

Customer requested to upgrade his Operations Manager reporting services to Windows server 2008 R2 & SQL 2008 SP1 to do so i followed :

http://technet.microsoft.com/en-us/library/cc540368.aspx
http://technet.microsoft.com/en-us/library/cc540369.aspx

The site DBA said that we don’t need to do an SQL upgrade and we can move the DB from SQL 2005 to SQL 2008.

the monitoring environment include:
RMS + SQL for OpsMgr DB (windows server 2008 SP2 with SQL 2005)
MS
GW
SRS + SQL for OpsMgrDW DB (Windows server 2003 SP2 with SQL 2005)

in order to get a fast rollback we got a new server and we will use the same server name (customer home-made scripts and reports uses server name and not a relative name).

The Upgrade Procedure:
1. Install new OS on the new server with temp name.
2. Backup of the OpsMgrDW DB + Jobs + Logins form the old server.
3. Stop all Opsmgr services (RMS,MS,GW) and shutdown the old reporting server.
4. Change the temp server name to the old server name.
5. Install SQL 2008 with SP1 + Configure the reporting services.
6. Verify that http://localhost/reports is showing info.
7. Start all services from step 3 and Install SCOM R2 Reporting Services. use the same Data Warehouse action account, OpsMgr Data reader and Writer.
8. repeat step 3 and Delete the new OpsMgrDW and restore the old DB.
9. Check Security settings (Logins) for OpsMgrDW DB for the users in step 7 and for the SDK service account.
10. Verify that the reporting services data source (connection string) is OK.
11. Start all services from step 3.
12. Verify that RMS and MS can store data in OpsMgrDW DB , check the OperationsManager event log for events 31570,31558,31554,31563,31551,31569,31552,10103 that indicates a connection problem.
13. run a report and check that everything is OK.

Rollback:
In case of rollback we need to shutdown the new server, restart the old server (join to domain) and that’s all.

We followed all steps and it seems that everything is fine, BUT i found that the setup procedure include an agent installation and the service “System Center Management” did not start. did i missed something ?

OK, i followed the move procedure again and i found that i need to “Uninstall the current Data Warehouse component” before i move to the new installation. maybe this part delete the agent from the OpsMgr DB? 

To fix this i deleted the old reporting server agent from the console, uninstalled the agent from the new server restart the server and then pushed a new client. now the agent started and we can monitor the new reporting server.

Advertisements
Categories: OpsMgr Tags: , , ,

Disable SQL Express monitoring

14/02/2010 Leave a comment

When you deploy the SQL MP (2005 & 2008), the discovery rule that targets the windows computer class start to collect information about SQL DB Engine. the results are that SQL Express edition (SQL 2005) and the Windows Internal DB (SQL 2008) are being monitored immediately.

In my experience, most DBAs do not like to get alerts about instances of SQL Express edition and Windows Internal DB. but several system administrators like to know if there is a problem with applications that uses those DB (Antivirus software, SCVMM, backup etc’). so basically if we will disable the discovery process we will not be able to get the state of the SQL service.

in that case, I advice my customers that do need to monitor SQL Express to build a dynamic group for those instances. to build this group do the following:

1. Open the admin console –> authoring –> groups.

2. Create a new group (SQL Express DB Engine)

image

3. Right click on the group you created and select View Group Members…

image

verify the the group contain the SQL Express and Windows Internal DB.

image

now its time to disable the monitors that we don’t need.

scope the authoring view to SQL 2005 DB Engine and SQL 2008 DB Engine and override the monitors that you do need. use the group we created earlier for the override.

image

 image

Do not Forget that the best way to disable a monitor is to use overrides and the disable option, if you disable a monitors you can not choose the management pack for overrides and you use the default MP!!!

Note:

1. The overrides are for monitors only, take in mind that we did not overrides any rules that target SQL DB Engine.

2. If you with to disable discovery for SQL Express and Windows Internal DB you can use the following: http://blogs.technet.com/kevinholman/archive/2010/02/13/stop-monitoring-sql-express-and-windows-internal-database.aspx

Categories: OpsMgr Tags: ,