Monitoring and reporting for Veeam Backup & Replication, VMware vSphere and Microsoft Hyper-V in a single System Center Operations Manager Console
Post Reply
mwinchester
Novice
Posts: 3
Liked: never
Joined: Apr 29, 2010 10:41 am
Full Name: Mark Winchester
Contact:

Multiple collector heartbeat alerts

Post by mwinchester »

Hi all

Does anybody else experience these and know what the cause is ? I am seeing up to 20 per day they usually auto resolve pretty quickly but i'd like to identify the cause and get it resolved. I'm not seeing similair alerts from any other machines or any actual problem on the collector itself.

Alert: Health Service Heartbeat Failure
Source: vcamsccs001.EUROPE.PPDI.LOCAL
Path: Microsoft.SystemCenter.AgentWatchersGroup
Last modified by: System
Last modified time: 31/03/2011 01:17:24
Alert description: The Health Service on computer vcamsccs001.EUROPE.PPDI.LOCAL failed to heartbeat.

Alert view link: "http://CAMRMS01:51908/default.aspx?Disp ... f69b61f%7d"
Notification subscription ID generating this message: {E0043DE2-681D-B3BE-D2B8-F9C747ACED6E}

Regards

Mark

vBPav
Expert
Posts: 181
Liked: 13 times
Joined: Jan 13, 2010 6:08 pm
Full Name: Brian Pavnick
Contact:

Re: Multiple collector heartbeat alerts

Post by vBPav »

Mark,

Please keep an eye on the nworks Collector Agent's "Send Queue % Used" (SCOM Console\Operations Manager\Agent Performance). If this is hitting 100% then the nworks Collector is handling way too much load. If this is the case I would suggest contacting Veeam Support to work through this (support@veeam.com).

Cheers!

Brian Pavnick - Solutions Architect
Brian Pavnick | Cireson| Solutions Architect

- Follow me on Twitter @ vbpav
- Reach me on e-mail @ brian.pavnick@cireson.com

steve_mc
Influencer
Posts: 12
Liked: 3 times
Joined: Mar 01, 2011 3:11 pm

Re: Multiple collector heartbeat alerts

Post by steve_mc »

Hi,

Can anyone in the Veeam team shed any light on how this issue was resolved in the end? - I am having similar issues, I have opened a support case and still working through this but it would be interesting to hear the community perspective on this issue if anyone else had had this problem.

Alec King
VP, Product Management
Posts: 1068
Liked: 238 times
Joined: Jan 01, 2006 1:01 am
Contact:

Re: Multiple collector heartbeat alerts

Post by Alec King »

Hi Steve,

Assuming this problem happens only with nworks Collector servers - then I would investigate the Monitoring Load on each Collector. If they are monitoring too many Hosts + VMs, then the Ops Mgr Agent Health service can use high cpu and memory, which could delay heartbeats. the Agent might even auto-restart, if the correct configuration is not applied.

There are 2 key points to configure the agent for stable performance -
1. You must run the Configure Ops Mgr Agent Task against every nworks Collector (this task is built-in to our MP)
2. You must override a couple of Ops Mgr default monitors for PrivateBytes usage - this prevents the auto-restart.

Please see our Install Guide, page 13 for instructions on configuring the agent as above.
Hope that helps!


Both of the above

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests