SQL Server DB Mirroring Management Pack68237

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

 

14 thoughts on “SQL Server DB Mirroring Management Pack68237

  1. kapildham

    Raphael, looks like this MP doesn’t work with SQL MPs from MS v. 6.1.400.0 It worked fine with previous version, since I upgraded the base SQL MPs, the Disk mirror specific info dissapeared, any ideas?

  2. kapildham

    This is what I saw just now, as a Warning in SCOM Console:

    Alert Rule: Alert on Failure to Create PowerShell Run space for Power Shell Script

    Failed to run the PowerShell script due to exception below, this workflow will be unloaded.

    System.NullReferenceException: Object reference not set to an instance of an object.
    at System.Environment.GetEnvironmentVariable(String variable, EnvironmentVariableTarget target)
    at System.Management.Automation.ModuleIntrinsics.GetExpandedEnvironmentVariable(String name, EnvironmentVariableTarget target)
    at System.Management.Automation.ModuleIntrinsics.SetModulePath()
    at System.Management.Automation.ExecutionContext.InitializeCommon(AutomationEngine engine, PSHost hostInterface)
    at System.Management.Automation.AutomationEngine..ctor(PSHost hostInterface, RunspaceConfiguration runspaceConfiguration, InitialSessionState iss)
    at System.Management.Automation.Runspaces.LocalRunspace.DoOpenHelper()
    at System.Management.Automation.Runspaces.RunspaceBase.CoreOpen(Boolean syncCall)
    at Microsoft.EnterpriseManagement.Modules.PowerShell.RunspaceController.RunScript(String scriptName, String scriptBody, Dictionary`2 parameters, PowerShellOutputType outputType, Int32 serializationDepth, IModuleDebug iModuleDebug)
    at Microsoft.EnterpriseManagement.Modules.PowerShell.PowerShellProbeActionModule.RunScript(RunspaceController runspaceController)

    Script Name: RABurri.SQLServer.2008.ComponentGroup.Discovery.ps1

    One or more workflows were affected by this.

    Workflow name: RABurri.SQLServer.2008.Mirroring.ComponentGroup.Discovery

    Instance name:

  3. kapildham

    Hello Raphael, I also noticed this event in the RMS Event log:

    Failed to run the PowerShell script due to exception below, this workflow will be unloaded.

    System.NullReferenceException: Object reference not set to an instance of an object.
    at System.Environment.GetEnvironmentVariable(String variable, EnvironmentVariableTarget target)
    at System.Management.Automation.ModuleIntrinsics.GetExpandedEnvironmentVariable(String name, EnvironmentVariableTarget target)
    at System.Management.Automation.ModuleIntrinsics.SetModulePath()
    at System.Management.Automation.ExecutionContext.InitializeCommon(AutomationEngine engine, PSHost hostInterface)
    at System.Management.Automation.AutomationEngine..ctor(PSHost hostInterface, RunspaceConfiguration runspaceConfiguration, InitialSessionState iss)
    at System.Management.Automation.Runspaces.LocalRunspace.DoOpenHelper()
    at System.Management.Automation.Runspaces.RunspaceBase.CoreOpen(Boolean syncCall)
    at Microsoft.EnterpriseManagement.Modules.PowerShell.RunspaceController.RunScript(String scriptName, String scriptBody, Dictionary`2 parameters, PowerShellOutputType outputType, Int32 serializationDepth, IModuleDebug iModuleDebug)
    at Microsoft.EnterpriseManagement.Modules.PowerShell.PowerShellProbeActionModule.RunScript(RunspaceController runspaceController)

    Script Name: RABurri.SQLServer.2005.ComponentGroup.Discovery.ps1

    One or more workflows were affected by this.

    Workflow name: RABurri.SQLServer.2005.Mirroring.ComponentGroup.Discovery
    Instance name:
    Instance ID: {8EA2CF7A-9CEC-E638-D14D-74D0A5E320EB}
    Management group:

  4. GG

    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

  5. mrgangster

    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

  6. Joe Mead

    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.

  7. mrgangster

    Microsoft SQL Server Management Pack (6.3.173.0) can’t monitor when mirror change state from Master to Mirror state, may you will upgrade your MP? We need this monitor.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.