VBO & WMI

[spiritie]

Hi Forums

I've searched a bit through the documentation and through this subforum for WMI, but haven't found anything related.

Does anyone know if VBO and WMI has any relationship on Windows servers? Does Veeam implement any NameSpaces ect?

We are monitoring hundredths of servers with WMI and only on our VBO servers we are experiencing WMI just dying out of the blue, often even with VBO is not doing anything.
Plenty of resources on the servers, and the solution is too restart the OS or WMI service in order to get WMI working again.

VBO is version 6, the WMI error we get is simply just a: "The RPC server is unavailable."

[Polina]

Hi Gert,

I'm verifying it with the dev team; will get back to you with some more details soon.

[Polina]

Hi Gert,

WMI usage in VB365 is limited to the following cases:
- validating volumes and SMB shares when creating a new backup repository
- getting the list of volumes when VSS is involved
- during automatic updates of the VB365 components (upgrades to the next patches)

Technically, none of the above should cause any issues. To investigate your problem it'd be better to open a case with Veeam Support. Please post your case ID here for the follow-up.

Thanks!

[Zew]

Since the issue itself is around WMI, the fact its on a VBO server might just be a coincidence, or it maybe the cause.

To better understand which of the two it maybe, may I suggest you enable verbose logging for WMI. https://techcommunity.microsoft.com/t5/ ... a-p/372901

This should be enough for you to narrow down the cause, if you find log information showing error that stem from VBO services, then possibly provide them here for further analysis or upload them to your support case.

[Mike Resseler]

Thanks @Zew A great idea!