Getting the Veeam B&R Version and Build with PowerShell

There are a few ways to get the version of a Veeam Backup & Replication install, most of the online content points you towards querying the ProductVersion property of the VeeamDeploymentDll.dll file. And this works quite well if you just want to the version, but it doesn’t give you the full build which changes with cumulative patches.

Here’s a quick example, let’s use a recently released Veeam 11a Cumulative Patch which includes several critical security fixes.

Veeam KB article

This has been deployed to our test server, so we’re expecting the returned version to be P20220302 as per the screenshot and confirmed by the About page within the Veeam console.

Veeam build about page

Let’s check that ProductVersion property.

PS C:\> (Get-Item 'C:\Program Files\Veeam\Backup and Replication\Backup\Packages\VeeamDeploymentDll.dll').VersionInfo

ProductVersion   FileVersion      FileName
--------------   -----------      --------      C:\Program Files\Veeam\Backup and Replication\Backup\Packages\VeeamDeploymentDll.dll

Unfortunately we don’t get the full build - we’re missing the P20220302 suffix, which means we can’t reliably use this method to determine whether our Veeam install is current.

Getting the full Veeam version with PowerShell

Here is a slightly different method which gives us the full build.

$InstallPath = Get-ItemProperty -Path "HKLM:\Software\Veeam\Veeam Backup and Replication\" | Select -ExpandProperty CorePath

Add-Type -LiteralPath "$InstallPath\Veeam.Backup.Configuration.dll" 
$ProductData = [Veeam.Backup.Configuration.BackupProduct]::Create()

$Version = $ProductData.ProductVersion.ToString()
if ($ProductData.MarketName -ne "") {$Version += " $($ProductData.MarketName)"}

And here is what the $Version variable gives us.

PS C:\> $Version P20220302

At the time of writing I’ve only had the opportunity to test this on various v11 installs but I’ll update the post if I have the chance to confirm with earlier versions.

If you enjoyed this post consider sharing it on , , , or , and .