Yesterday I upgraded veeam 10 to 11. According to the release notes, the pssnapin is replaced by a module
Source: veeam_backup_11_0_whats_new_wn.pdf page 6:
PowerShell module — By popular demand, we switched from the PowerShell snap-in to the PowerShell
module, which can be used on any machine with the backup console installed. We also no longer require
PowerShell 2.0 installed on the backup server, which is something many customers had problems with.
But when using the Powershell module in scripts you could get messages:
Import-Module : The specified module ‘Veeam.Backup.PowerShell’ was not loaded because no valid module file was found in any module directory.
WARNING: The names of some imported commands from the module ‘Veeam.Backup.PowerShell’ include unapproved verbs thatmight make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
This is because the Veeam Powershell module is not in the default paths so you can add some lines to you scripts to fix this issue:
$VeeamModulePath = “C:\Program Files\Veeam\Backup and Replication\Console”
$env:PSModulePath = $env:PSModulePath + “$([System.IO.Path]::PathSeparator)$VeeamModulePath”
Import-Module -DisableNameChecking Veeam.Backup.PowerShell