By Raphael Burri on 6/8/2011 5:00:19 AM • Rank (9007) • Views 10146
3

3

Update May 31, 2011 - Version 1.0.2.10 now available for download.

Over 250 downloads of previously published versions.

The SQL Server DB Mirroring Management Pack discovers database mirroring components and provides probe based monitors to verify that database mirrors are operational. Optionally it verifies the roles and operating modes of mirrored databases against a Desired Configuration setting.

Use the SQL Server DB Mirroring Management Pack for:

  • Monitoring the availability state of mirrored databases and witnesses.
  • Monitoring if the mirrors are operating in line with a Desired Configuration definition.
  • View mirrored DBs as a service components and use them for Distributed Application designs.
  • Report on SQL database mirroring configuration.
  • Use the objects and groups discovered to add SQL database mirroring specific rules, monitors or overrides.

The Management Pack download contains a comprehensive guide that carefully lists all prerequisites. As a supplement it also contains an override MP that works in conjunction with the Extended Microsoft SQL Server MP hosted on OpsManJam. It shows how to use the discovered objects of the SQL Server DB Mirroring MP to parameterise existing or new MPs to support DB mirrors.

Download the SQL Server DB Mirroring Management Pack by clicking on the Download button in the upper right corner (bust be logged in - registration is free).

 

Change History

 

 

Version 1.0.2.10 - May, 31 2011 (no functional changes)

 

Fixes bug introduced in 1.0.2.5 making the discovery of SQL 2005 mirrors impossible. Update recommended if monitoring SQL 2005 database mirrors.

 Version 1.0.2.5 - April, 28 2011 (no functional changes)

Corrected spelling in language pack.

 

 Replaced all SCOM shell cmdlets with .NET calls to overcome a potential issue when several connectors and other MPs share a single SDK connection.

 

 Improved discovery script timing behaviour when using desired configuration for a large number of mirrors.

 

Version 1.0.1.72 - September, 10 2010

 

Support for SQL Server 2005 has been added and compatibility with SQL Server 2008 R2 has been verified. Starting with version 1.0.1.72, Microsoft SQL Server 2005, 2008 and 2008 R2 are supported.

 

Default Display Names of discovered DB Mirror Groups have been shortened and may optionally be changed to a customized string. See the guide for details.

Version 1.0.1.35 - June, 04 2010

Original release - SQL Server 2008 support only

Download

"Only registered users may download. Registration is free."

Version:
Importance:
Guide:
Latest Media - View All Media (1)
   
Comments (9) - Comment RSS
Stefan Koell wrote: on Jun 04, 2010 10:06 AM
looks very promising, Raphael!
Raphael Burri wrote: on Sep 10, 2010 08:15 AM
I have just published the update to version 1.0.1.72 which adds support for SQL Server 2005.
GG wrote: on Oct 20, 2011 07:26 PM
I am having a problem with the "Desired Configuration" in regards to the monitor Database Mirror Role Compliance. In the Health Explorer, I keep seeing the Role in a warning state. Furthemore, the alert shows the following:

Database mirror <DatabaseName> not currently running according to its desired configuration.
Database Name: <DatabaseName>
Desired Principal: <SQLServer1> / Current Principal: <SQLServer2>
Desired Mirror: <SQLServer2> / Current Mirror: <SQLServer1>

I have verified my servers and they are correct. The desired server in the XML does indeed match what is actually in place.

The alert description has the following in it (note the "desired" and "actual" both pull a variable named "Desired..."):

Desired Principal: $Target/Property[Type="MirroringLibrary!RABurri.SQLServer.Mirroring.ComponentGroup"]/DesiredMasterComputerPrincipalName$ / Current Principal: $Target/Property[Type="MirroringLibrary!RABurri.SQLServer.Mirroring.ComponentGroup"]/DesiredMirrorComputerPrincipalName$

Desired Mirror: $Target/Property[Type="MirroringLibrary!RABurri.SQLServer.Mirroring.ComponentGroup"]/DesiredMirrorComputerPrincipalName$ / Current Mirror: $Target/Property[Type="MirroringLibrary!RABurri.SQLServer.Mirroring.ComponentGroup"]/DesiredMasterComputerPrincipalName$

Since it seems these always pull out of the XML and pulling opposite servers it appears it is attempting to resolve

Principal = Mirror

which will always resolve to false.


Anyone else seen this behavior?

Thank you,
Gary
DBA
mrgangster wrote: on Nov 28, 2011 07:53 AM
how can i enable SQL Server Desired DB Mirroring Configuration Discovery? I need monitor when mirror change state from Master to Mirror state. I have read instruction and made DesiredDBMirrors.xml and put in on RMS Server C: location, but when mirror change state I have no alert. Please help
Al Howarth wrote: on Jan 05, 2012 02:02 PM
Does anyone have this working?

Has anyone been able to receive support from the developer?
Joe Mead wrote: on Jan 12, 2012 10:03 AM
Not us. The console views are not populating.
Joe Mead wrote: on Jan 13, 2012 12:42 PM
Found our issue. The account used for SQL needed to be distributed to the RMS. It does not go there by default if there is no SQL Server on the RMS.
mark blakey wrote: on Feb 07, 2012 04:24 AM
Thanks, have been looking for something like this
Add your Comment


Who Viewed
Who Reviewed
Categories
Tags
Database Mirroring, Management Pack, Operations Manager 2007 R2, SQL Server
Related Pages
Shortened URL
http://tinyurl.com/44mplff

Top Contributors
Featured Members
Pete Zerger
Points: 66505
Level: System Center Expert
Tommy Gunn
Points: 43683
Level: System Center Expert
Simon Skinner
Points: 40804
Level: System Center Expert
Stefan Koell
Points: 29364
Level: System Center Expert
Andreas Zuckerhut
Points: 28364
Level: System Center Expert