VeeamONE 9.5.0.3254
2 Hyper-V hosts monitored. Both are Server 2016, w/Veeam 9.5.
In the lefthand pane of Infrastructure View or Business View, next to one of the Hyper-V servers, there is a small red circle w/exclamation mark, but this server has no unresolved alarms, either at host level, VM level, or storage level.
Hovering over exclamation mark shows "Errors: 0, Warnings:0".
This condition has been like this for a couple of months, and neither VeeamONE server reboots, or Veeam B&R upgrade to 9.5U3 has changed this condition.
So it seems to be some kind of phantom alarm condition.
How can I clear it?
-
- Enthusiast
- Posts: 37
- Liked: 8 times
- Joined: Sep 27, 2016 6:59 pm
- Contact:
-
- Product Manager
- Posts: 14726
- Liked: 1706 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Phantom error on Hyper-V host
Hello TGacs.
Is it possible for your to share a screenshot? Thanks in advance!
Is it possible for your to share a screenshot? Thanks in advance!
-
- Enthusiast
- Posts: 37
- Liked: 8 times
- Joined: Sep 27, 2016 6:59 pm
- Contact:
Re: Phantom error on Hyper-V host
Here is a screenshot showing the exclamation mark on the first Hyper-V server:
-
- Enthusiast
- Posts: 37
- Liked: 8 times
- Joined: Sep 27, 2016 6:59 pm
- Contact:
Re: Phantom error on Hyper-V host
Well, that figures - I had upgraded VBR to 9.5U3 and nothing changed, but I just upgraded VeamOne to 9.5U3 and the phantom red exclamation mark has gone away...at least for now.
So, for now, anyway, this appears resolved as a side-effect of upgrading.
So, for now, anyway, this appears resolved as a side-effect of upgrading.
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Phantom error on Hyper-V host
Hello,
That's a known bug. It appears when object with errors/warnings is deleted or excluded from monitoring.
The bug will be fixed in the upcoming update.
Workaround is to use "Resolve all" command. Otherwise if it bothers you, contact support team. They will help delete the error state from DB.
Thanks!
That's a known bug. It appears when object with errors/warnings is deleted or excluded from monitoring.
The bug will be fixed in the upcoming update.
Workaround is to use "Resolve all" command. Otherwise if it bothers you, contact support team. They will help delete the error state from DB.
Thanks!
Who is online
Users browsing this forum: No registered users and 4 guests