ONE - Host average memory pressure - wrong server reported

[Robvil]

Hi,

ONE version 9.5.0.3254

I am using a Hyper-V 2012r2 cluster. I have a specific Windows 2016 guest OS which has too little memory assigned (which is per design) - therefor I get warnings saying by email:
Host average memory pressure 81% (Guest OS machine name)

For this specific object/machine, I have made a exclusion not to alert me. But 5-6-7 times a day i get a false alarm "Host average memory pressure 81%" but on one of my physical Hyper-V hosts (the one which has the VM running).
The physical host is no way near memory max usage.

Seems there is a bug where ONE monitor will email alert on a wrong host, if a make a exclusion for this.

/Robert

[Shestakov]

Hi Robert,
I`ve checked the behavior in my lab, but could not confirm it. We will double-check it with QA team and let you know here.
Thanks!

[Shestakov]

Robert,
QA team also haven`t confirmed the bug.
Could you contact Veeam support team?
Thanks!

[Robvil]

i´ll do.

[Shestakov]

Thanks!
Once you have a support case number, please post it here for us to follow the investigation.

[RMB]

Hi

I have something similar. I'm using the free version. I have a HyperV VM and a Linux VM on a clustered server. I am getting a low drive space warning on both servers. It is true for the HyperV VM but not the Linux VM. The Linux VM is also getting it's own alarms which are not reflected on the HyperV VM, so the duplication appears to be one way.

There are 15 VM on the cluster, and they are a mix of HyperV and Linux VMs, but only two are being confused, so it's not a global issue.

Rich.

[Shestakov]

Hi Richard and welcome to the community!
Could you clarify what you mean by Hyper-V VM in comparison with Linux VM? Do you mean VM with Windows OS running on Hyper-V host?
Thanks!

[elvensailor]

I have similar issue:

2 Hyper-V servers (2016, non-clustered)
hv1: 16+ VMs, 80% of RAM eaten up, all running smoothly.
hv2: 2 VMs, 20% of RAM consumed - got "High memory pressure 101%" every day.

What's going on?

[Shestakov]

Hello Dmitry,
As the behavior was not confirmed in our lab and OP didn't provide the case number I would ask you to contact Veeam support team for the issue investigation.
Once you do please provide the case number.
Thanks!

[elvensailor]

The issue disappeared by itself, after ~a week.

[Shestakov]

Thanks for the update, Dmitry.