Prepare your environment to Operations Manager 2012 – Part II Updating the SQL Server
As promise, the second part of this series will show you to how to update your Operations Manager 2007 R2 infrastructure from SQL Server 2005 to SQL Server 2008 R2 SP1.
I invite you first to read my previous post : Prepare your environment to Operations Manager 2012 – Part I Actions Plan
Marnix Wolf, an Operations Manager MVP, already posted a series about the same subject, and I really advise you to read it :
Preparing for migrating to OM12: Moving from SQL 2005 to SQL 2008 – Part I: Along came a theory
Preparing for migrating to OM12: Moving from SQL 2005 to SQL 2008 – Part II: Phase I – The Preparations
Preparing for migrating to OM12: Moving from SQL 2005 to SQL 2008 – Part III: Phase II – The Migration
Below, the pre-requisites from a infrastructure point of view :
- Your current SCOM 2007 R2 Infrastructure must be at least Cumulative Update 4 (CU4) Level, but my personal advice it’s to update it first to the last Cumulative Update, the CU5.
- A brand new server running Windows Server 2008 R2 SP1.
- .Net Framework 3.5.1 role installed.
- Microsoft SQL Server R2 2008 source + SP1 Package.
- Add you SQL Service Account to the local administrator group of the new server.
- Backup all your SCOM 2007 R2 Infrastructure.
SQL Server 2008 R2 installation
Report Server Uninstallation
You must back up any custom reports that were authored outside of Operations Manager 2007. For more information about this, see Moving the Report Server Databases to Another Computer in the SQL Server 2008 Books Online (http://go.microsoft.com/fwlink/?LinkId=151513).
SQL Server 2005 : Backup the DBs
Go on your SQL Server 2005, start the SQL Management Studio, select OperationsManagerDB, Tasks, Backup.
SQL Server 2008 R2 SP1 : Restoring the DBs
It’s now time to go on your brand new SQL Server 2008 R2 SP1 server to restore the two databases.
In the User Mapping part, we have to copy exactly the same rights that we have on the SQL Server 2005.
We have to Enable the CLR on the Operations Manager DB on the SQL Server 2008 R2 SP1 server. Just copy past the query below.
sp_configure ‘show advanced options’, 1;
sp_configure ‘clr enabled’, 1;
Enable the SQL Broker, for that, take a look to Alexander’s post : http://scug.be/blogs/scom/archive/2008/11/22/the-sql-server-service-broker-for-the-current-opsmgr-database-is-not-enabled.aspx
RMS & MS : Changing the link to the DB server
Launch the RegEdit and look for the key HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft Operations Manager3.0Setup
Last but not least, the reporting server.
Microsoft released a KB for running Operations Manager 2007 R2 on SQL Server 2008 R2 KB245714. http://support.microsoft.com/kb/2425714
Open Computer Management, in the Computer Management MMC snap-in, expand System Tools, expand Local Users and Groups, and then click Groups.
We could now remove the SQL Server 2005 and enjoy our new SQL Server 2008 R2 SP1.
I hope this post will help you to prepare your environment to be ready for SCOM2012. The next post of this series will show you how to migrate your RMS role from Windows Server 2003 SP2 to Windows Server 2008 R2 SP1.
Christopher Keyaert – Ops Mgr MVP