Skip to Content

Setting up the monitoring of a clustered environment

You can set up and configure a Microsoft SQL Server cluster for monitoring by PATROL using the following methods:

  • With a virtual PATROL Agent, the following statements are true:
  • Does not require you to configure the SQL Server instances on each cluster node. Instead, you configure PATROL for Microsoft SQL Server on the active nodes (that is, the virtual SQL Server).
  • Parameter history and configuration settings are stored on a shared drive and are, therefore, available after failover.
  • The Failover parameter is available in this environment.
  • Only SQL Server instances belonging to the same cluster resource group as the virtual PATROL Agent are discovered.
  • You must use the PATROL Cluster Configuration Wizard to add the virtual PATROL Agent.
  • You must run a virtual PATROL Agent on each cluster resource group that has a SQL Server to monitor.
  • With PATROL Agent node-level monitoring, the following statements are true:
  • Because PATROL configuration data and parameter history data are not shared between the PATROL Agents on the cluster nodes, you must configure each SQL Server to which the instance can fail over.
  • You must configure each SQL Server to which the instance can fail over.
  • You cannot view parameter history that was collected on another cluster node.

Before you begin installing the product in a clustered environment, decide which of the configurations you should use to monitor your clustered environment. To help you decide which configuration is best for your needs, see Actions-PATROL-takes-when-a-SQL-Server-comes-online.

Related topics

Monitoring-a-cluster-by-using-a-virtual-PATROL-Agent

Monitoring-a-cluster-by-using-a-PATROL-Agent-on-each-node

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC PATROL for Microsoft SQL Server 9.5