Hi,
I'm currently working on a large Exchange 2010 Template that also monitors the DAG and so it monitors if a database is currently active or passive. I use the following performance counter to check the state of a database. I have to admit that documentation for all the counters is really rare, thanks to Microsoft.
\MSExchange Active Manager(pf-db-002)\Database Mounted
0 = passive
1 = active
I have created an item with a status mapping for this. It works as expected.
Now I would like to create a trigger (or two if required). That states in the triggername if the database has switched from passive to active or vice versa. I tried the following but this doesn't seem to work.
Trigger Name: Exchange database {HOSTNAME} switched from {ITEM.LASTVALUE} to {ITEM.VALUE}.
But this will always state either "switched from passive (0) to passive (0)" or "switched from active (0) to active (0).
I thought ITEM.LASTVALUE is the "last" value and ITEM.VALUE is the 2nd last value. Turns out they are both the same.
Maybe this can be done with two triggers that depend on each other but I'm not sure.
I'm currently working on a large Exchange 2010 Template that also monitors the DAG and so it monitors if a database is currently active or passive. I use the following performance counter to check the state of a database. I have to admit that documentation for all the counters is really rare, thanks to Microsoft.
\MSExchange Active Manager(pf-db-002)\Database Mounted
0 = passive
1 = active
I have created an item with a status mapping for this. It works as expected.
Now I would like to create a trigger (or two if required). That states in the triggername if the database has switched from passive to active or vice versa. I tried the following but this doesn't seem to work.
Trigger Name: Exchange database {HOSTNAME} switched from {ITEM.LASTVALUE} to {ITEM.VALUE}.
But this will always state either "switched from passive (0) to passive (0)" or "switched from active (0) to active (0).
I thought ITEM.LASTVALUE is the "last" value and ITEM.VALUE is the 2nd last value. Turns out they are both the same.
Maybe this can be done with two triggers that depend on each other but I'm not sure.