Yesterday, Veeam released Veeam B&R 8 Update 2, which contains some significant improvements such as Endpoint Backup integration, vSphere 6 support and more. You can find more information about the release here.
This article provides a step by step guide for an update from Veeam 8 (version 22.214.171.1247, 126.96.36.1997, 188.8.131.521, 184.108.40.2067 or 220.127.116.118) to Veeam 8 Update 2 (version 18.104.22.1681).
For more security:
The first step is to realize a configuration backup of Veeam server (“Configuration Backup” menu on the screenshot below) and if the Veeam Backup Server is deployed on a Virtual Machine, execute a backup of this VM with Veeam B&R.
When the backup is done, you can close Veeam software and restart the Windows server to clear any locks on the Veeam services (reboot). Basically I recommend you to stop properly the 6 or 7 Veeam services before upgrading (services.msc).
Running the Installer:
You have to run the installation file “VeeamBackup&Replication_22.214.171.1241_Update2.exe”.
Veeam now preparing the wizard.
Once wizard is launched, click on “Next” button.
Then Veeam will prompt to install the update 2, click “Install”.
The update took about few seconds to complete.
Once the upgrade completed, a prompt appeared to finalize the installation. Click on “Finish” button.
When the upgradre is done, I recommend you to restart properly the Windows server (reboot) and start the Veeam services.
Upon opening Veeam, a prompt will appear to update the components (especially the server and the proxy). Click on “Next” button.
Finally, when all components have been upgraded, you can click on “Finish” button.
You can check the version in “About” tab (“Help” menu) : 126.96.36.1991.
Veeam B&R 8 does not require new job creation or any architecture changes for your existing backups and replication to work. If there are dedicated Veeam proxy servers in the environment, now is a good time to upgrade those servers, otherwise, Veeam is now ready to use. After upgrading to vCenter Server 6.0, due to vSphere 6 using new unique tag IDs, you must edit all existing jobs that leverage vSphere tags and re-add all required tags.