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 the error: Veeam Powershell snap-in was loaded from an incorrect location. This results in numerous "No data " responses. Which leads to issues with alerts not clearing when they should, or not opening when they should. Which cascades into our ticketing system to cause further confusion. Powershell works fine locally on any of the servers in question, scripts that utilize Veeam's powershell module that I push from our management tool also work fine. It just seems to be LogicMonitor that has issues with reliability. In these instances, the collector is installed directly on the Veeam host. Veeam forums indicate this may be due to the snap-in installation being corrupted, however I have manually verified it is all correct on a handful of servers and the issue persists. Plus it works locally and on my pushed scripts from a different tool. We are monitoring 44 Veeam servers (all the latest version) and all of them seem to have this reliability issue. Making it hard to believe that the installation could be goofed on every single one of them. All LM supplied default scripts utilize: Add-PSSnapin -Name VeeamPSSnapIn -WarningAction SilentlyContinue -ErrorAction SilentlyContinue I tested by manually running the script from a debug window, but changing from Add-PSSnapin to using Import-Module and referencing the Veeam dll file, yet the intermittent "incorrect location" error persists. Another test, I removed all references to Add-PSSnapin and suprisingly, it still works about 50% of the time. By all findings, I only get this error when running collection scripts from LogicMonitor. Have yet to see it locally. Anybody ese noticing the same thing?Solved134Views0likes1CommentVeeam SOBR Offload and Checkpoint removal monitoring
With recent updates to Veeam 12.2, checkpoint removal has been decoupled from the backup job and it now produces alerts within the veeam console when it fails. This is not detected in any current version of LogicMontiors Veeam modules. It also seems that the offload of backups when you have a SOBR configuration are not monitored by LogicMonitor's Veeam modules. We are finding this means we are blind to most of our customers offsite storage as we are not notified of offload failures or checkpoint removal. This means if an S3 bucket fills up in your capacity tier, but the performance tier is still working you will never get an alert in logicmonitor, as the backup job itself is successful, but the offloads and checkpoint removals will fail due to the bucket being at maximum capacity. The offsite copy will fall severely out of date as well since no new backups can offload or copy to capacity tier. We have had to fall back to email alerts to compensate for this. SOBR is the most common setup we see across our customer base these days, and I have a feeling it will only become more prevalent in the future.48Views1like0CommentsSupport for Veeam Backup & Replication v12
On Friday Oct 13th, LogicMonitor released module updates that introduce official support for Veeam Backup & Recovery v12. For more information, please see the product documentation or search for Veeam in LM Exchange; https://www.logicmonitor.com/support/monitoring/backup-and-replication-systems/veeam-backup-replication-monitoring Below are screenshots, but please follow your organization;s change control processes.332Views23likes5Comments