Hi all
Has anybody had any success monitoring Microsoft Database cluster using Xymon/Hobbit?
Cheers V
NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments.
Hello, Vernon!
I do not have a MS DB cluster, but my Exchange 07 cluster monitoring works just fine. What is it you are trying to accomplish exactly?
Ray
From: Everett, Vernon [mailto:Vernon.Everett at woodside.com.au] Sent: Tuesday, November 11, 2008 1:35 AM To: hobbit at hswn.dk Subject: [hobbit] MS Cluster
Hi all
Has anybody had any success monitoring Microsoft Database cluster using Xymon/Hobbit?
Cheers V
NOTICE: This email and any attachments are confidential.
They may contain legally privileged information or
copyright material. You must not read, copy, use or
disclose them without authorisation. If you are not an
intended recipient, please contact us at once by return
email and then delete both messages and all attachments.
Hi Raymond
I have no idea what the correct terminology is for this, being a Unix admin myself, but we are trying to keep tabs on a Microsoft Cluster running MS-SQL. The problem is, the disk devices appear to be dynamic on the component servers. Imagine a database server WINDB01, consisting of servers WINDB02, WINDB03 and WINDB04. We are seeing disk m: for an example in WINDB02, then the graph disappears, and the disk m: suddenly appears on WINDB04, and then later vanishes again only to appear back on WINDB02. It's a bit of a pain, because you have no continuity.
We are looking for a way to monitor the static drives on WINDB02,03 and 04 as normal disks, and then have the shared or pooled resources (whatever the term is I don't know) listed on Hobbit under WINDB01, no matter where they really reside. This will give us continuous graphs for local and shared/pooled resources.
Any ideas?
From: Storer, Raymond [mailto:storerr at nibco.com] Sent: Tuesday, 11 November 2008 10:54 PM To: hobbit at hswn.dk Cc: Everett, Vernon Subject: RE: MS Cluster
Hello, Vernon!
I do not have a MS DB cluster, but my Exchange 07 cluster monitoring works just fine. What is it you are trying to accomplish exactly?
Ray
From: Everett, Vernon [mailto:Vernon.Everett at woodside.com.au] Sent: Tuesday, November 11, 2008 1:35 AM To: hobbit at hswn.dk Subject: [hobbit] MS Cluster
Hi all
Has anybody had any success monitoring Microsoft Database cluster using Xymon/Hobbit?
Cheers V
NOTICE: This email and any attachments are confidential.
They may contain legally privileged information or
copyright material. You must not read, copy, use or
disclose them without authorisation. If you are not an
intended recipient, please contact us at once by return
email and then delete both messages and all attachments.
NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments.
Vernon,
I'd put the node name on the client as the cluster name, not the node's NetBIOS name if your cluster is active/passive. Then, when the active node changes just run a script that changes the node name for the active node and recently deactivated node-perhaps adding and removing the M: drive monitoring as appropriate too. It isn't perfect; and, you will miss a beat or two between active node checks. If all your nodes are running active perhaps you could do something with WMI scripting against the cluster name to get the M: drive stats and tell bbwin to ignore the M: drive on all the nodes.
Ray
From: Everett, Vernon [mailto:Vernon.Everett at woodside.com.au] Sent: Wednesday, November 12, 2008 2:08 AM To: Storer, Raymond Cc: hobbit at hswn.dk Subject: RE: MS Cluster
Hi Raymond
I have no idea what the correct terminology is for this, being a Unix admin myself, but we are trying to keep tabs on a Microsoft Cluster running MS-SQL. The problem is, the disk devices appear to be dynamic on the component servers. Imagine a database server WINDB01, consisting of servers WINDB02, WINDB03 and WINDB04. We are seeing disk m: for an example in WINDB02, then the graph disappears, and the disk m: suddenly appears on WINDB04, and then later vanishes again only to appear back on WINDB02. It's a bit of a pain, because you have no continuity.
We are looking for a way to monitor the static drives on WINDB02,03 and 04 as normal disks, and then have the shared or pooled resources (whatever the term is I don't know) listed on Hobbit under WINDB01, no matter where they really reside. This will give us continuous graphs for local and shared/pooled resources.
Any ideas?
From: Storer, Raymond [mailto:storerr at nibco.com] Sent: Tuesday, 11 November 2008 10:54 PM To: hobbit at hswn.dk Cc: Everett, Vernon Subject: RE: MS Cluster Hello, Vernon!
I do not have a MS DB cluster, but my Exchange 07 cluster monitoring works just fine. What is it you are trying to accomplish exactly?
Ray
From: Everett, Vernon [mailto:Vernon.Everett at woodside.com.au] Sent: Tuesday, November 11, 2008 1:35 AM To: hobbit at hswn.dk Subject: [hobbit] MS Cluster
Hi all
Has anybody had any success monitoring Microsoft Database cluster using Xymon/Hobbit?
Cheers V
NOTICE: This email and any attachments are confidential.
They may contain legally privileged information or
copyright material. You must not read, copy, use or
disclose them without authorisation. If you are not an
intended recipient, please contact us at once by return
email and then delete both messages and all attachments.
NOTICE: This email and any attachments are confidential.
They may contain legally privileged information or
copyright material. You must not read, copy, use or
disclose them without authorisation. If you are not an
intended recipient, please contact us at once by return
email and then delete both messages and all attachments.
CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
participants (2)
-
storerr@nibco.com
-
Vernon.Everett@woodside.com.au