Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Centreon Plugin Veeam Mode Vsb-Jobs not working with Veeam 12.1.2.172 cmdlet not supported anymore #5116

Open
Pieso974 opened this issue Jul 19, 2024 · 5 comments

Comments

@Pieso974
Copy link

Hi,

Veeam just get updated to 12.1.2.172.
We downloaded the last centreon_plugins.exe (July 2024) but got the same message for Sure Backup checks :

Command:
scripts\centreon\centreon_plugins.exe --plugin=apps::backup::veeam::local::plugin --mode=vsb-jobs --critical-jobs-failed="$ARG1$" $ARG2$

Result:
UNKNOWN: Command error: System.Exception: This cmdlet is no longer supported. Use Get-VBRSureBackupSession instead. - at Veeam.Backup.PowerShell.Cmdlets.GetVSBSession.Execute() - at Veeam.Backup.PowerShell.Cmdlets.PSCmdletBase.ProcessRecord() - at System.Management.Automation.CommandProcessor.ProcessRecord()

Thanks for your help

@lucie-dubrunfaut
Copy link
Contributor

Hello :)

You indicated the "same message" which implies a problem already identified, could you tell me the issue in question or other information relating to a bug already reported? Could you also provide us the output of the plugin with the --debug option to help us troubleshooting this issue?

@Pieso974
Copy link
Author

Pieso974 commented Aug 2, 2024

Hi,

I said "same message" because I tried the centreon-plugins released in March too (and older ones).
But since the Veeam update to 12.1.2.172, the vsb-jobs mode return that the cmdlet is not longer supported.

I'll be back with --debug soon

Thanks

@Pieso974
Copy link
Author

Pieso974 commented Aug 6, 2024

Hi,
here the output with --debug:

PS C:\Program Files\Centreon NSClient++\scripts\centreon> .\centreon_plugins.exe --plugin=apps::backup::veeam::local::plugin --debug --mode=vsb-jobs --critical-jobs-failed=1

UNKNOWN: Command error: #< CLIXML - System.Exception: This cmdlet is no longer supported. Use Get-VBRSureBackupSession instead. - at Veeam.Backup.PowerShell.Cmdlets.GetVSBSession.Execute() - at Veeam.Backup.PowerShell.Cmdlets.PSCmdletBase.ProcessRecord() - at System.Management.Automation.CommandProcessor.ProcessRecord() - System.Management.Automation.InformationRecordSystem.ObjectSystem.Exception: This cmdlet is no longer supported. Use Get-VBRSureBackupSession instead.x000D__x000A at Veeam.Backup.PowerShell.Cmdlets.GetVSBSession.Execute()x000D__x000A at Veeam.Backup.PowerShell.Cmdlets.PSCmdletBase.ProcessRecord()x000D__x000A at System.Management.Automation.CommandProcessor.ProcessRecord()System.Management.Automation.HostInformationMessageSystem.ObjectSystem.Exception: This cmdlet is no longer supported. Use Get-VBRSureBackupSession instead.x000D__x000A at Veeam.Backup.PowerShell.Cmdlets.GetVSBSession.Execute()x000D__x000A at Veeam.Backup.PowerShell.Cmdlets.PSCmdletBase.ProcessRecord()x000D__x000A at System.Management.Automation.CommandProcessor.ProcessRecord()System.Exception: This cmdlet is no longer supported. Use Get-VBRSureBackupSession instead.x000D__x000A at Veeam.Backup.PowerShell.Cmdlets.GetVSBSession.Execute()x000D__x000A at Veeam.Backup.PowerShell.Cmdlets.PSCmdletBase.ProcessRecord()x000D__x000A at System.Management.Automation.CommandProcessor.ProcessRecord()falseDarkYellowDarkMagentaWrite-Host

2024-08-06T16:15:18.8724907+04:00
System.Collections.Generic.List`1[[System.String, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=XXXXXXXX]]System.ObjectPSHOSTXXXXXXXXXX295522060417

Does the --mode=vsb-jobs uses the VBRSureBackupSession?
Maybe it still use the obsolete Get-VSBSession cmdlet? (still ok in v10 and v11 but not in v12)
https://helpcenter.veeam.com/docs/backup/powershell/get-vsbsession.html?ver=120

Thanks for your help

@Pieso974
Copy link
Author

Hello,
any news?

Thanks

@lucie-dubrunfaut
Copy link
Contributor

Hello :)

We have opened an internal analysis ticket which will be discussed and estimated in refinement with the dev team in the next session.
Best regards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants