Mastering Development System & Network

Monitoring Windows Failover Cluster with Enterprise Manager

I’m trying to monitor SQL Server instances on a 2 node active/passive windows failover cluster with Enterprise Manager.

Oracle gives the following steps:

-Install local agents on both nodes.

-Install agent on shared storage for the virtual hostname of the cluster on ONE node.

This seems to be somewhat incomplete, especially the last part.

Agent installation creates a windows service. Creating a failover resource would require said service to run on a shared storage and to be defined on both cluster nodes.

So I’d expect the service for the virtual cluster is either supposed to replace the two local agent services or it needs to be copied to the second host? Which is the better option or am I completely wrong? (My replacement theory is based on my puzzlement that a local agent neede to be installed on each node in the first place, why would that otherwise be necessary?)

I expect to run into additional problems when I create a cluster role from the agent service, since I can only do that by giving the role its own IP. However, the agent is registered with the OMS host on installation. Will I need to also fix the data in the repository for the new IP adress in an additional step, or will the combination of (virtual cluster adress):(agent port) automatically point to the role’s new IP?

Leave a Reply

Your email address will not be published. Required fields are marked *