Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

It should be simple, so it is just most likely my approach being totally off and someone will hopefully prod me into the right direction.

We have a Zabbix 2.0.3 server instance set up monitoring a bunch of different servers, but now we need to set it up to monitor and notify any alerts in regards to the SQL Server 2008 R2 Failover Active-Passive cluster.

Essentially, this is a 2 servers cluster, when only one of its nodes can be "active" at a given time, serving all SQL Server related requests, while the other server just "sleeps" and from the point of anyone logged on on that server - has all of the SQL Server related services in stopped state.

We have tried setting up Zabbix agents on both servers, using SQL Server 2005 templates (we could not find any 2008 specific ones and the 2005 ones always seemed to be working just fine for monitoring 2008 R2 instances) and configuring Zabbix server for both of the servers, but we end up having constant alerts for the server being currently the passive one in the cluster. We have been able to look up various methods of actually monitoring the failover, but we have not been able to find any guidance in regards to how to instruct Zabbix, that in this particular case, only one of the servers in the group is expected to be in the online state, while the other can be just discarded and should not raise any alerts.

I hope I made myself clear. Thanks for any guidance. I am out of ideas.

share|improve this question

2 Answers 2

I do not know anything about SQL Server cluster, but there is probably a Service IP address associated with the active node that failover to the other node in case of HA event. Instead of monitoring SQL Server on both your nodes (hosts in zabbix), create a new host "SQL Server Active" with the Service IP address, and monitor SQL Server only on that host.

share|improve this answer
    
The thing is, that the Service IP is valid only on the private network, while the Zabbix server is located somewhere else. Setting up VPN between Zabbix and the private network could be a solution, but it adds another point of failure, which we would like to avoid. Also, this would not be enough, since we need to monitor on the OS level as well, e.g. the amount of free space on the data drive, and the iSCSI drive which holds data for the cluster is mounted on the active node server only. The best solution would be to have a group, where we could say: if one host is ok, disregard the others. –  Sebastian Zaklada Dec 4 '12 at 8:49
    
My suggestion is to have 3 hosts: 1st node, 2nd node, and service. You could even have a 4th host to monitor your standby service. If both nodes are reachable, I do not think it is a big pain to make the service reachable as well. A well placed NAT could do the job here. –  jfgagne Dec 4 '12 at 12:35

I have 3 hosts in zabbix to monitor Clusters. 1 and 2 is NODES ofcourse. 3rd is Cluster. I monitor them checking on cluster what is his hostname currently so it introduces the active node hostname. I also found some way to check status through WMI. Just ask google :)

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.