June 30, 2023 at 11:25 am
Correct me if I'm wrong here but on a SQL Server 2019 cluster (active/passive deployment) ----- where NODE1 of the Cluster is ACTIVE and NODE2 of the Cluster is PASSIVE (dormant) ----- the SQL Server services (except for SSIS) will show as STOPPED on the PASSIVE (dormant) NODE2.
We have a vendor asking about this as their monitor ALARMS are ringing because the PASSIVE NODE2 SQL Services are showing as DOWN.
June 30, 2023 at 2:52 pm
If you are referring to a Failover Cluster Instance (FCI) in the cluster - where that instance has been installed in the cluster using shared storage, then yes - the services that are managed by the cluster need to be set to manual on each node in the cluster that can be a possible owner and the cluster will manage those services.
The services will be running on the node that is currently hosting the FCI and stopped on all of the other possible owners in the cluster.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
June 30, 2023 at 3:09 pm
This is correct. The services will start when the cluster fails over.
If the monitoring is an application that is installed on each server, then this can be created as a clustered resource.
They also should be monitoring 4 different "servers" Node1 and Node2 should be monitored as Windows Servers.
The SQL Server name should be monitored as a SQL Server. Optionally, this can also be Windows and SQL
The cluster should be monitored as a Windows Server
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
June 30, 2023 at 4:30 pm
Jeff & Michael - thank you for your replies. You've confirmed our thoughts on this subject.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply