As we rapidly approach release day for Veeam Backup and Replication v10 (February 18!) Many of you are going to want to do upgrades on that day or shortly after. Personally for production level servers I advocate for waiting for patch 1 to come out, usually 2 weeks to 1 month after GA if history bears out. This is especially true if you utilize any Cloud Service Providers for offsite copies as this is what Veeam refers to as a “breaking” release. That means that if the cloud side VBR you are connecting to is not also on version 10 then you will see errors both during installation and then once you open the console and your backups WILL fail.
That said if you have a testing environment or a lab GA is a great day to get at it. This post, now with video, will outline the steps necessary to do an in-place upgrade. One important thing to note before going down this road is upgrade to the RTM/GA is limited to 9.5 update 3 or later. If you happen to be running an older version you will need to upgrade to this first.
- Go to my.veeam.com and download the ISO on or after 2/18.2020 and obtain a new v10 license file
- Ensure that any and all jobs are not running. Usually this means Backup Copy Jobs need to be disabled as they are continuous (mostly)
- Mount the ISO file by right click>mount
- Run setup.exe and click upgrade
- VBR v10 is now based on the .NET Framework v4.7.2 and you will be prompted to install that if you haven’t already. A reboot will be required before you can proceed.
- Once the reboot has been completed (pretty quick on Windows Server 2019) we’ll need to remount our ISO and run setup.exe again
- Accept EULAs, Next
- Verify versions you are upgrading from, Next
- If you’ve already downloaded your new v10 compatible license file go ahead and install it now. If not, no worries because Veeam will be granting you a 60 day grace period to get this done. Once you are installed you can import the new license via the Menu>License window in the VBR console. Hit Next
- Next we want to verify the database configuration. It should automatically have all the information for where your VeeamBackup database is. Before you get to this point it is a best practice to take a SQL level backup of the database prior to upgrading. Hit Next and then confirm that you do want to upgrade the existing database.
- Finally we are at ready to install. Go ahead and check the “Update remote components automatically” as this will have Veeam launch the updater wizard upon first launch of the console to update any scaled out proxies, repositories or WAN accelerators you may have. Hit Install.
- Once complete hit Finish and choose yes to reboot.
- Launch and log in to the VBR console
- Upgrade any external components that need done
- Go to Backup Infrastructure>vSphere and rescan all your vSphere components. This may be overkill but I’ve always found a rescan after upgrade heads off many upgrade related issues.