[apps::backup::veeam::local::plugin] - mode(vsb-jobs): Not working with Veeam 12.1.2.172 cmdlet not supported anymore

[Pieso974]

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]

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]

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]

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() - <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04"><Obj S="information" RefId="0"><TN RefId="0"><T>System.Management.Automation.InformationRecord</T><T>System.Object</T></TN><ToString>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()</ToString><Props><Obj N="MessageData" RefId="1"><TN RefId="1"><T>System.Management.Automation.HostInformationMessage</T><T>System.Object</T></TN><ToString>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()</ToString><Props><S N="Message">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()</S><B N="NoNewLine">false</B><S N="ForegroundColor">DarkYellow</S><S N="BackgroundColor">DarkMagenta</S></Props></Obj><S N="Source">Write-Host</S><DT N="TimeGenerated">2024-08-06T16:15:18.8724907+04:00</DT><Obj N="Tags" RefId="2"><TN RefId="2"><T>System.Collections.Generic.List`1[[System.String, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=XXXXXXXX]]</T><T>System.Object</T></TN><LST><S>PSHOST</S></LST></Obj><S N="User">XXXXX</S><S N="Computer">XXXXX</S><U32 N="ProcessId">29552</U32><U32 N="NativeThreadId">20604</U32><U32 N="ManagedThreadId">17</U32></Props></Obj></Objs>

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]

Hello,
any news?

Thanks

[lucie-dubrunfaut]

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.

[monsieurpouet]

Hi !

Any news about this issue ?

Thanks !

[lucie-dubrunfaut]

Hello :)

This ticket was estimated and will be processed soon. When the dev branch becomes available, we will post a link here so that you can test the proposed solution.