PowerShell v5 not supported on v13?

[robnicholsonmalt]

This didn't pass in front of my eyes, but can somebody confirm that Veeam cmdlets now only support PowerShell v7? Get-VBRComputerBackupJob is not found under PowerShell v5.1 but does run under PowerShell v7.6.0. I run a maintenance script on my client's Veeam servers which checks the jobs are running.

[david.domask]

Hi Rob,

Correct, PowerShell 7 is required for v13, support for lower versions was dropped.

[robnicholsonmalt]

Thanks for the confirmation. For the record, if anyone has scheduled tasks running using powershell.exe then this needs to be changed to pwsh.exe. BTW - if installing PS7 on a server, it needs to be rebooted for pwsh.exe to appear in the system command path. Also PS7 does introduce some compatibility issues with PS5 scripts, more than one might expect or at least hope

[david.domask]

Also PS7 does introduce some compatibility issues with PS5 scripts, more than one might expect or at least hope

Can you share a few examples here @robnicholsonmalt? Is it with native PowerShell cmdlets or Veeam cmdlets?

For the latter, all previous scripts are intended to work out of box (excepting for cmdlets that changed / deprecated), so would be curious to know what did not work.

[robnicholsonmalt]

This isn't specifically with Veeam - the Veeam cmdlets in my maintenance script appear to be working fine. The PS7 incompatibilities/breaking changes are mainly with the native PowerShell cmdlets. I'm a massive PowerShell fan so I've got many scripts (my software developer roots at play there) - probably say it was 1 in 20 scripts that needed tweaks. Latest example was using System.Diagnostics.ProcessStartInfo to launch other tasks from a PS script. Had to add UseShellExecute as they changed the way this system launches executables. Grok/AI is your friend here - ask if if there a breaking change with XYZ.

[david.domask]

Got it, thanks for clarifying, just wanted to make sure as our intended design was no change for Veeam cmdlets, but yes some items that worked in PowerShell 5 are handled differently in PowerShell 7.