Heartbeat is missing for VM

[mintyevertonian]

Hi Guys,

I am continually getting this error for a Windows 7 64 bit VM
The VM is fine and is operatinal. I reinstalled VMware tools to ensure all is ok. Just keep getting this error numerous times a day but not with any other VMs on the same host so it makes little sense to me

any ideas?
I created this from a clone if that makes any difference

[veremin]

Have you tried to resolve these alarms manually? Will they be triggered again? What about restarting corresponding services (monitor, etc.) ? Thanks.

[Vitaliy S.]

Also can you please check VM heartbeat counter in the vSphere Client? What are the values there?

[mintyevertonian]

Afraid still an issue after resolving alarms manually and restarting services.

[mintyevertonian]

Not really sure where I can see these counters?

[Vitaliy S.]

Navigate to VM Performance tab -> Advanced -> Chart Options -> System - Real Time to see heartbeat counter.

BTW, is this the only VM that is affected by this? You said that you've cloned it...is the original VM still present in the VI?

[mintyevertonian]

for the last day the counters are maximum 99562;average 4078;minimum 0

I recall the original VM having the same issues and I simply took this out of the monitoring

Its causing no problems but veeamone is alerting ...no alerts from vcentre

[Vitaliy S.]

There are no alerts from vCenter Server, cause this alarm is not predefined. You can create it by yourself and confirm that it has the same behavior. On top of that, what related events do you see for this VM when the heartbeat alarms is fired?

[mintyevertonian]

there are no other events for this VM...as far as i ama ware there is no problem with the VM

[veremin]

What about manually creation similar vCenter alarm? Does the said problem repeats there? Thanks.

[mintyevertonian]

I set the alarm in vcentre and i have received no alarms from this only from veeam One

[Vitaliy S.]

Then please contact our technical team for further investigation, and please post your case number for future reference.

[jlehtinen]

Was googling a related issue and saw this post.

Have you confirmed the sleep/hibernation settings in Windows 7 for the VM?

Veeam will report 'heartbeat missing' on a Windows 7 VM if it goes to sleep.

[Vitaliy S.]

Hi John, I think that this is expected for any OS that goes to sleep, since VMware Tools are no longer responding in this case.

[jlehtinen]

Hi John, I think that this is expected for any OS that goes to sleep, since VMware Tools are no longer responding in this case.

Agreed. I was just asking if the OP had confirmed this was not the cause of the problem.

I had the same issue: a few Windows 7 VMs that seemed to be giving this error at "random" times. It turned out they were just being used intermittently and had sleep/hibernation enabled. They would go to sleep a few times a day, causing the error to display in Veeam.

[Vitaliy S.]

Yes, it was a great catch, that slipped my mind for some reason.

[genetorres]

Hi guys, I found this via a search, and I'm looking at the "heartbeat" counter for a VM. Since you've been discussing it, and I never use this counter for anything, could someone tell me exactly what this counter means? I'm seeing numbers like this:

Max: 737686 Min: 1200 Average: 27610 and there are two huge spikes over a 1 hour period every 24 hours (when backups are running) and outside of that, this line in the graph is a flat line. I'm not looking to solve a problem, but simply understand what these numbers mean.

Thanks!

[veremin]

Hearbeat alarm shows up, if VM is either unavailable or overloaded for a certain period of time. Thanks.

[Vitaliy S.]

This counter represents how many heart beats your VM had in a certain time period, these spikes are usually caused be VM reboots and other activities. In the best case the line should be flat indeed.

[edvschriesheim]

Hi Guys,

i have an nearly identical problem as this guy: http://forums.veeam.com/veeam-one-f28/h ... 21181.html

We have a couple of Citrix Linked Clone VMs. Some of the Clones produced the "Hearbeat is missing" Error.
Everything in the VMs runs fine and in the vSphere Chart the Heartbeat seems ok.
I reinstalled vSphere Tools in the Citrix Master and recreated the clones, but the error comes up again. I thin about 2-3 Times a day.

Veeam One reports the following
Error Heartbeat Missing 06:10:55
Resolved Heartbeat Missing 06:14:18

During this Time vSphere show's me a constant heartbeat of 30


Any suggestion how we can resolve this issue?

Greetings
Tobias

[Shestakov]

Hello Tobias,
That looks like a bug.
Do you observe other performance metrics during that time period(06:10:55-06:14:18)?
Btw, what product version you are at?
Thanks!

[Vitaliy S.]

Also what is the difference between VM clones that have this error and the ones that don't? Are they hosted on the same server, datastore etc?

[edvschriesheim]

We're now on Veeam One 9, but the error occured on Veeam One 8, too.
The other metrics during that time period are fine. The VM itself also runs without any problems.

There's no differne betweeen the clones. There on the same Servers and the same datastore.

[Shestakov]

Considering that, I would suggest to contact Veeam support for the further investigation.
Once you have a support case # please post it here.
Thanks!

[edvschriesheim]

Support Case is #01689940

[edvschriesheim]

Case is closed. I got a Registry File with some changes in the Registry of the Veeam One Monitor Server. That solved the issue.

The Reg File increased the time interval during which Heartbeat is not monitored after system starts.

[Shestakov]

Interesting! Thanks for updating the topic.

[edvschriesheim]

Is it allowed to post the registry file, so others can use the same solution?

[Shestakov]

It`s not necessary for you to do that. We will discuss the issue with support and devs and create a KB article if needed.
Thanks for your participation!

[UPD]
The bug is going to be fixed in the update 1, which is planned for the end of February.
Those who have the same problem, can get the registry via technical support.

[Shestakov]

Glad to inform that v9 update 1 has been released and discussed issue is fixed there.