Englisch:
In the Veeam console we activated status information under “Storage”> “Notifications”.
The status information is output as an attribute in the vSphere.
Can you monitor this if the field is not filled or if the backup is older than 24 hours?
Deutsch:
In der Veeam Konsole haben wir unter “Storage” > “Notifications” Statusinformationen aktiviert.
Die Statusinformationen werden im vSphere als Attribut ausgegeben.
Kann man dies Monitoren, wenn das Feld nicht gefüllt ist oder wenn das Backup älter als 24 Stunden alt ist?
This will add one service per backup job to Veeam server and to any VM in that job. This script might easily be extended to support Replication and Copy jobs.
The checkmk agent for Windows has a plugin available to get the backup status directly from veeam.
(veeam_backup_status.ps1)
If you enable this plugin in your agent config or copy the plugin to a directory where all plugins are executed, your checkmk server will get all the informations directly from veeam.
(the retry-bug that was the reason for the veeamagent-script at exchange.checkmk.com is fixed in the official plugin since November 2015 [werk #2726], so you can now use the official shipped plugin)
piggyback data that can give you details for each VM, added through piggyback data to all corresponding server VMs (same name, or defined through piggyback hostname translation) https://checkmk.com/cms_check_veeam_client.html
On your veeam server, the plugin is in the default plugin folder of the agent:
C:\Program Files (x86)\checkmk\service\plugins
In the default config, no plugin in this directory is executed.
You can copy the plugin to the local plugin directory
C:\ProgramData\checkmk\agent\plugins
or you can enable the veeam plugin in your check_mk.user.yml with the following config (benefit: if the shipped plugin is updated, it will automatically use the updated plugin, you do not need to copy it again)
depending on the size and performance of your Veeam infrastructure, getting all data through the powershell plugin can take some time.
If you have a normal default check interval of 1 minute, you should maybe add an “Normal check interval for service checks”-Rule for the “Check_MK$” service on your backup host in the monitoring config, to only query the veeam host every 2 or 5 minutes
(but the official agent bakery does a copy of the plugins to the local folder instead of just adding it to the config, so maybe there are reasons for this)
The reason is to stay compatible with the rules and deployment scripts from 1.5
We (as the users) need to find some time that this can be discussed with Sergej if a change is possible and doable.
I would prefer that inside the “Programdata” plugins folder are only different plugins then the default plugins.
that means if the latest Windows Agent is installed. Then the Veeam plugin is automatically installed? And you just have to adjust the parameters of the Veeam rules. Is that correct?
This is only if you configure the plugin the way that @stalmon said.
No mkp files do nothing on your target system. It installs only new or modified versions on your monitoring system. A modified plugin in only deployed to your monitored systems with a newer version if you use the enterprise edition with the agent bakery.
You have two options.
1: copy the “veeam_backup_status.ps1” from “C:\Program Files (x86)\checkmk\service\plugins” to “C:\ProgramData\checkmk\agent\plugins” - that’s all
2: change only the file “C:\ProgramData\checkmk\agent\check_mk.user.yml” inside the section “plugins” to execute the “veeam_backup_status.ps1” directly from the “program files” directory