Veeam Backup and Replication
Summary: In the discussion, Dave Thurlby raised an issue with the latest Veeam update, which disrupted the PowerShell script used for data gathering, affecting its functionality with LogicMonitor. In response, Michael Rodrigues mentioned that LogicMonitor is working on a new Groovy-based module utilizing Veeam 13's HTTP API, requesting test environments from users like Chris Red and Bhavesh Parmar, who offer their Veeam 13 environments for testing. Joshua Kurzawa shared solutions for compatibility issues between scripts and Veeam, having adjusted them to work with newer Veeam versions and methodologies. The updated scripts and insights were of interest to others, such as Rickey Hebert, looking to set up Veeam v13.
Looks like the most recent version of Veeam has broken the PS script used to gather datasets. The PS seems to error out when it tries running. Deleted and re-added all modules related, also deleted and re-added the resource. No dice.
Discover won't even detect it now, so seems to be officially borked. How can we get LogicMonitor to work on updating the script?
Joshua Kurzawa
·3 months agoI've managed to amend and successfully fix all the Veeam Backup and Replication DS scripts and now have successful monitoring across VBR v12 and v13!
Hope the below helps! I haven't uploaded the updated scripts to the Exchange yet but can do if anyone wants to check them out.
We've been running these for nearly two weeks now and are feeling much more confident about our client estate and reporting again.
Summary
There were several issues that initially made it difficult to identify what was causing failures. Hopefully this summary helps with what needed to be addressed.
Initial version compatibility
All the LM datasource scripts were calling Add-PSSnapin VeeamPSSnapIn, which was deprecated from v12 onwards. If a Veeam server has gone through several upgrades over the years, you might have been lucky and still had this lingering — but it's not reliable.
No warnings/alerting on no data collection
By default the scripts would not alert if no data was received. Adding "No Data" alerts helped flag devices experiencing issues quickly.
New DS script to check connectivity to Veeam
Built a new script that tests whether it can connect to VBR and reports back the type of issue it's experiencing, so you know what to fix.
v13 and PS7
v13 requires PS7 to be installed, but the original scripts didn't account for this and would fail without any clear indication. The scripts now detect whether PS7 is available and load the module under it. If PS7 is not found, it falls back to PS5.1 — though on a properly configured v13 host, PS7 should always be present as it's a Veeam prerequisite.
Veeam MFA configuration
The biggest contention was MFA being enforced on VBR, combined with the PowerShell modules only working with the Backup Administrator role. This means you either need a dedicated veeam.user/veeam.pass credential in VBR with the Backup Administrator role and MFA disabled for that account — or, the cleaner option, have a LogicMonitor collector installed directly on the VBR server running as LocalSystem, which allows it to authenticate to VBR without needing to disable MFA at all. Both options are supported and are tested by the connectivity status script.
Rickey Hebert
·3 months agoHi Joshua, I am definitely interested in the updated scripts. I am about to attempt to setup for a fresh install of v13 for the first time.
Joshua Kurzawa
·3 months agoI believe I've found part of the issue is down to the LM scripts use Add-PSSnapin VeeamPSSnapIn which is depreciated in Veeam v13 and requires
Import-Module Veeam.Backup.PowerShell
Connect-VBRServer
Currently going through the LM scripts to try and get them to check if it can connect to either Add-PSSnapin VeeamPSSnapIn or Import-Module Veeam.Backup.PowerShell
Matt Taylor
·4 months ago+1 for Veeam 13 support please if it helps push things along.
I imagine, you are already sorted for an env to work on however we can also provide one if required.
Bhavesh Parmar
·5 months agoHi @Michael Rodrigues
We are also facing the same issue after upgrading to Veeam 13 version, we are happy to work with you for the fixes.
Michael Rodrigues
·5 months ago · EditedHi @Bhavesh Parmar , thank you, it'd be a huge help if you can provide a Veeam 13 environment for our developers to develop/test against. I'll followup with you via email!
Bhavesh Parmar
·5 months agoHi @Michael Rodrigues we are happy to provide you V13 environment for the testing.
Do we have any work around till the new logic modules will be developed and tested?
Bhavesh Parmar
·5 months agoI am facing the same issue after upgrading VBR 13, we are not unable to get data for Veeam Backup job session and copy sessions.
Dave Thurlby
OP6 months agoWe would love to help out. What is the best way to get in contact?
Michael Rodrigues
·6 months agoHi Dave, sorry, just seeing this now. You can email me (michael.rodrigues@logicmonitor.com) or you can reach out through your CSM. Thanks for reaching out!
Michael Rodrigues
·6 months agoHi Dave, we're actually working on updated support for Veeam 13 now. The new modules are likely to be Groovy-based and will likely leverage the Veeam 13 HTTP API for collection, vs the PowerShell CMDlets.
Please let me know if you are able/willing to provide a Veeam 13 environment we can test against. Also curious if you have any opinion on the modules being PowerShell vs Groovy.
Chris Red
·6 months agoHi @Michael Rodrigues, an API/Groovy based module would be much preferred. Ideally it would work with older Veeam versions as well.
I was considering making one myself as opening up WinRM to backup appliances can get some push back from a security point for view, HTTPS for a read-only API is a much easier ask.
We have a Veeam 13 environment that needs monitoring now, I can help test as long as it doesn't affect the environment.
Chris
Michael Rodrigues
·6 months agoHi Chris, it looks like we are going the API/Groovy route. The testing we do is very safe read only stuff. Please email me at michael.rodrigues@logicmonitor.com or reach out through your CSM and we can see about setting up access. Thanks!