Prepare your environment to Operations Manager 2012 – Part II Updating the SQL Server
2:29 pm in Uncategorized by Christopher Keyaert
Hi All,
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.
Pre-requisites
Resources
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
Infrastructure
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
We’re starting a new SQL installation
Select SQL Server Feature Installation
Check at least the check boxes below
Use the default instance, or create a new one, depending of your environment.
Review the information and click on next.
Configure your Run As Account for the SQL Server.
In the Collation Tab, select SQL_Latin1_General_CP1_CI_AS and click next.
Specify the SQL Admins for your new SQL Server.
Select Install the Native Mode Default Configuration and click Next.
Just review the information and click on Next.
Just review the information and click on Next.
Just review the information and click on Install.
Installation Completed Successfully.
It’s now time to install the SP1, run the SQLServer2008R2SP1-KB2528583-x64-ENU.exe that you have previously downloaded on Microsoft Website.
Accept the license terms and click next.
Review the information and click on next.
Review the information and click on next.
Review the information and click on update.
SP1 has been successfully installed.
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).
Go to your current SCOM reporting Server, Add and Remove Programs menu and uninstall the System Center Operations Manager 2007 R2 Reporting Server.
SQL Server 2005 : Backup the DBs
Go on your SQL Server 2005, start the SQL Management Studio, select OperationsManagerDB, Tasks, Backup.
Select the backup location for your Operations DB.
In the options, check Verify backup when finished and click on OK.
The backup of the Operations Manager DB completed successfully.
Do exactly the same operations than above for the Data Warehouse DB.
We’ve got now, two DB Backup files.
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.
Start the Sql Management Studio and choose Restore Database.
Select restore from Device and add the backup file of your OperationsManager DB and click OK
Check the Restore box next your DB name.
In the Destination for restore, you are now able to specify the OperationsManager DB.
Review all the information, and click on OK.
Do exactly the same for the Data Warehouse DB.
Now, we have to authorize the SCOM service accounts to connect to these newly restored DBs. For that simply go Sql Management Studio, Security Logins and do a right click, chose new login.
In the User Mapping part, we have to copy exactly the same rights that we have on the SQL Server 2005.
Replicate the exact same configuration, for each Maps to the SQL Server 2008 R2 SP1.
If you are using several account to connect to the different Database, apply the same than what we did above for all your accounts. For my lab environment, I just have a second account.
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; GO RECONFIGURE; GO sp_configure ‘clr enabled’, 1; GO RECONFIGURE; GO |
Click on Execute and check the result.
Now, in the OperationsDB, search for the table dba.MT_ManagementGroup.
Change the SQLServerName_6B1D1BE8_EBB4_B425_08DC_2385C5930B04 value from your SQL Server 2005 server name to the SQL Server 2008 server name.
Go on your OperationsManagerDW Db, select the table dbo.MemberDatabase.
Change the ServerName value from your SQL Server 2005 name to the SQL Server 2008 name.
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
We now have to change the SQL server reference on the RMS server and every MS to point to the new SQL Server. For that, stop the three System Center Services.
Launch the RegEdit and look for the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup
We have to change the DatabaseServerName value to point to our new SQL Server.
Start the 3 Operations Manager Services on the RMS and the System Center Management service on the MS.
In the Event Logs, you must see these events.
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.
Locate the following group:
SQLServerReportServerUser$<hostname>$MSRS10_50.<SQLInstanceName>
Rename the group to the following by removing "_50" from the group name:
SQLServerReportServerUser$<hostname>$MSRS10.<SQLInstanceName>
Install System Center Operations Manager 2007 R2 Reporting.
Select only the Reporting Server Part.
Specify the name of you RMS server.
Specify the name of your new SQL Server.
Review the information and click on Next.
The Reporting is Back in SCOM Console.
After you install System Center Operations Manager 2007 R2 Reporting, rename SQLServerReportServerUser$<hostname>$MSSRS10.<SQLInstanceName>
back to original name SQLServerReportServerUser$<hostname>$MSSRS10_50.<SQLInstanceName>
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