Veeam Version Numbers

Veeam Version Numbers

Veeam Version Numbers

The following Veeam version number table provides a useful guide when planning Veeam upgrades. It can be used to find the latest Veeam version, plan an upgrade path and see what version you are currently using, plus find the relevant release notes.

Veeam Updates

Updates – are like patches to the software and are applied within the same release family.  So for example to apply 9.5 Update 2 you would need to be running a version 9.5.x. Getting the specific version number information from the table to move to 9.5 Update 2 you would need to be on at least version,, or

You can download the latest product updates from the Veeam Website.

Veeam Major release

Major releases – are the next major increment in the software. You can generally do an in place upgrade within 2 release versions.  You can use the table below to confirm the upgrade path.  So for example if you were updating to 9.5 you would lookup 9.5 in the table and see that the earliest version you could be on would be 8.0 Update 3. The latest major release download files generally are bundled with the updates so for example there would be no need for example to install 9.5 and then 9.5 Update 2.

Veeam Versions Table

Veeam Version Build Number Earliest Supported Update Version Release Notes
9.5 Update 3a,,,,, or 9.5 Update 3a KB
9.5 Update 3,,,, or 9.5 Update 3 KB
9.5 Update 2,, or 9.5 Update 2 KB
9.5 Update 1, or 9.5 Update 1 KB
9.5 8.0 Update 3 9.5 Release Notes
9.0 Update 2 or 9.0 Update 2 KB
9.0 Update 1 9.0 Update 1 KB
9 Version 8 any patch level, 7 patch 4 9.0 Release Notes
8.0 Update 3,,,,,, or 9.0 Update 3 KB
8 7.0 or 6.5 8.0 Release Notes
7 Patch 4,,,,, or 7.0 Patch 4 KB
7 6.5, 6.1 and 6.0 (any patch level)

Whilst the above table is useful when planning your Veeam upgrade path. Be sure to refer to the release notes to ensure you have captured all the details relevant to planning the upgrade of your environment.


Backup gets sexy – Nimble Secondary Flash Array

Getting the most from Veeam

Veeam Version Numbers

Deleting jobs in Veeam

Veeam v9 Upgrade

I have written a way more detailed post on the Veeam upgrade process which you may prefer to read!

I recently upgraded a version 8 Veeam Backup and Replication installation to version 9. These are the notes I took to summarise the process.


  • If you have Veeam ONE upgrade this first
  • Download the Veeam V9 media
  • Licence file for v9
  • Suspend all jobs in Veeam Backup and Replication


  • Run a config backup
  • Take a manual SQL backup of your Veeam Backup and Enterprise databases
  • Snapshot Veeam backup server VM

Enterprise manager

  • Accept licence
  • The wizard finds the old version of Veeam. Choose next to proceed with upgrade
  • Browse to licence file
  • System configuration check. Allows you to install missing components
  • Reboot if missing components installed require it
  • Rerun setup if it doesn’t start automatically
  • Setup should find the existing DB used by Veeam Enterprise Manager. Choose to upgrade it
  • Allow upgrade to complete
  • Reboot if prompted

2 config check

Veeam Backup & Replication

  • Check Veeam version information and upgrade path
  • Run the V9 setup file
  • Choose to upgrade Veeam Backup and Replication
  • Accept licence agreement
  • The wizard finds the old version of Veeam. Choose next to proceed with upgrade
  • Browse to licence file
  • Setup should find the existing DB used by Veeam Backup and Replication. Choose to upgrade it
  • Allow upgrade to complete
  • Reboot if prompted
  • Launch Veeam console when prompted and allow all the different components such as proxy servers etc to be upgraded
  • Optional – install the Veeam standalone console


Brocade FC Switch Supportsave

A Brocade supportsave command saves a wealth of logs and information that can be useful when troubleshooting an issue.  It is also a recommended procedure to run a supportsave before upgrading the firmware on a switch, so that you have the necessary information to hand should there be an issue. Supportsave requires an FTP server to upload the logs to, if you don’t have an FTP server you can connect to the switch using Putty and choose to save the output to a file and then run a supportshow.

The following procedure shows how to collect logs from a Brocade switch via the CLI:

1 Connect to the switch via CLI

2 Enter supportsave and follow the prompts

3 Choose y when prompted to proceed

OK to proceed? (yes, y, no, n): [no] y

4 Enter the IP address of the FTP server

Host IP or Host Name:

5 Enter a username with access to the FTP server

User Name: anonymous

6 Select the protocol the FTP server uses

Protocol (ftp | scp | sftp): ftp

7 Select the directory on the FTP server to save the logs to. In this case the logs are being saved into a folder called switches

Remote Directory: /switches

8 When the operation finishes you will see a number of zip files in the location you specified

See all the steps together below

FCSWITCH1:admin> supportsave This command collects RASLOG, TRACE, supportShow, core file, FFDC data and then transfer them to a FTP/SCP/SFTP server or a USB device. This operation can take several minutes. NOTE: supportSave will transfer existing trace dump file first, then automatically generate and transfer latest one. There will be two trace dump files transferred after this command. OK to proceed? (yes, y, no, n): [no] y Host IP or Host Name: User Name: anonymous Protocol (ftp | scp | sftp): ftp Remote Directory: /switches Saving support information for switch:FCSWITCH1

For reference this is the link to the Brocade site on supportsave

More Brocade content

Configuring a Brocade switch in access gateway mode

Moving a Brocade Port Licence

Backing up a Brocade switch