Forum Discussion

tk_baha's avatar
tk_baha
Icon for Neophyte rankNeophyte
2 months ago
Solved

Monitoring of Veeam is not reliable

Has anyone successfully monitored Veeam with LM? From what I am seeing out of the box, every single module is unreliable. The scripts run probably 50-60% of the time. Otherwise they just fail with th...
veeam
  • tk_baha's avatar
    tk_baha
    2 months ago

    We believe this one has been sorted out. The collector service cannot run as system. Even if the correct veeam credentials are provided as properties, this behavior will continue. Once the service is set to use actual account credentials, the issue goes away. Strange that service works half the time but this appears to be the issue. The below comment on veeam modules lead me to believe that you could specify veeam.user or wmi.user and pass, but the issue did not fully resolve until we switched the service as well. 

    • Collector user must have access permission or credential properties must be provided as either of the following: -- Veeam (veeam.user and veeam.pass) -- WMI (wmi.user and wmi.pass)
tk_baha's avatar
tk_baha
Icon for Neophyte rankNeophyte
2 months ago

We believe this one has been sorted out. The collector service cannot run as system. Even if the correct veeam credentials are provided as properties, this behavior will continue. Once the service is set to use actual account credentials, the issue goes away. Strange that service works half the time but this appears to be the issue. The below comment on veeam modules lead me to believe that you could specify veeam.user or wmi.user and pass, but the issue did not fully resolve until we switched the service as well. 

  • Collector user must have access permission or credential properties must be provided as either of the following: -- Veeam (veeam.user and veeam.pass) -- WMI (wmi.user and wmi.pass)