It is set to the results of the SQL query that compares the date/time of the last backup to the current date/time.  In other words, if the backup is 4 hours old, then NumHours=4.

There is a line above the section of the script that I posted that creates the property that then gets sent back to SCOM in the property bag.

Call objBag.AddValue("NumHours", CInt(oResults(1)))

 

The value that I see in the alert (or if I run the SQL query manually in on the server) is correct.  The problem is the reaction of SCOM to the value.  It's not seeing 3 as being less than 25 for some reason, even though I appear to have the Healthy and Unhealthy expressions correct (as in the picture).

Hi ComputerBob,



Can I add another file at the end of my blogpost with your improvements?



Regards,

Stefan Stranger



http://blogs.technet.com/stefan_stranger/archive/2009/02/02/opsmgr-sql-full-or-differential-backup-check.aspx?CommentPosted=true#commentmessage

Hi Bob, 

I also followed Stefan's solution and i also ran into the issue your referring to above. When i posted the same issue the MSDN forum http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/f3ee2886-dcdc-4257-ba67-7f8e047683f5 , Daniele Grandini suggested that i change the data type in the xml configuration from string to integer. Since making this change, the alerts and state changes seems to occur when at the correct time. Here is the bit of xml i changed to integer.

 

 

          <ErrorExpression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery Type="Integer">Property[@Name='NumHours'] </XPathQuery>

              </ValueExpression>

              <Operator>Greater</Operator>

              <ValueExpression>

                <Value Type="Integer">20</Value>

              </ValueExpression>

            </SimpleExpression>

          </ErrorExpression>

          <SuccessExpression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery Type="Integer">Property[@Name='NumHours'] </XPathQuery>

              </ValueExpression>

              <Operator>LessEqual</Operator>

              <ValueExpression>

                <Value Type="Integer">20</Value>

              </ValueExpression>

            </SimpleExpression>

          </SuccessExpression>

Cheers,

PK

 

PK emailed me about another issue he was having with this process. He had some DBs with a space in the name (ie: "GBIX DB") which caused a problem because the script would see those as 2 separate variables and basically fail. I sent him a solution which worked for him and should work for most people. I have seen this before in another script, and had a fix for it that might work here. When you pass the parameter to the script, put quotations around it. See below to see what I’m talking about.



This is what is documented as the parameters sent to that script:

$Target/Host/Property[Type="SQLServer2!Microsoft.SQLServer.DBEngine"]/ConnectionString$ $Target/Property[Type="SQLServer2!Microsoft.SQLServer.Database"]/DatabaseName$ 47



Change it to look like this (notice the quotations around the 2nd parameter):

$Target/Host/Property[Type="SQLServer2!Microsoft.SQLServer.DBEngine"]/ConnectionString$ “$Target/Property[Type="SQLServer2!Microsoft.SQLServer.Database"]/DatabaseName$” 47



I did this for a script having to do with IIS sites and it fixed my ‘extra parameters’ problem when the people that made the site had put a space in the name.



PK tested this in his environment and it works to resolve his issue.

An enhanced version of that script has already been incorporated into a management pack, which can be downloaded at the link below:
SQL Admin Extensions Sample Management Pack for OpsMgr 2007 and Essentials 2010