/How to upgrade to the new Veeam v10

How to upgrade to the new Veeam v10

After the official launch of Veeam v10 on the 18th of February is time to write about how to upgrade to the new Veeam v10.

The process of upgrading to v10 is very straightforward. However, in some cases, we can encounter some issues, depending on your system and infrastructure. In this blog post, we will go through how to upgrade to the new Veeam v10 but also look at some of the errors that can occur during the upgrade and how to fix it.

If you have Veeam Enterprise Manager installed in your server or a different server, there is an order what to upgrade first in your Veeam Backup Server.

Pre-checks before start your v10 upgrade:

Note that this upgrade is only supported from Veeam Backup & Replication 9.5 Update 3 or later?. If you plan to upgrade from previous versions, contact Veeam Customer Support.

Check HERE the system requirements for Veeam Backup & Replication v10.

  • Make sure the latest run for all existing jobs has completed successfully. Rerun the failed jobs before you start your upgrade.
  • Make sure there are no running jobs, restore sessions, Instant VM Recovery sessions, and SureBackup jobs. Veeam also recommends that you do not stop running jobs and let them complete successfully.
  • Disable any periodic and backup copy jobs temporarily to prevent them from starting during the upgrade.

But here are the main system requirements and changes from the lastest Veeam 9.5 Update 4.


In-place upgrade is supported from 9.5 U3 or later, except from v10 pre-release builds.

System Requirements

Changes from 9.5 Update 4:
• Dropped VMware ESXi 5.0 and 5.1 support (5.5 is still supported).
• Dropped VMware vCloud Director 8.x support (8.20 is still supported).
• Dropped Windows Server 2008 support (2008 R2 SP1 is still supported).
• Dropped Windows 10 1507 and 1511 support (Windows 10 1607 or later are still supported)
• Dropped Windows 8.0 support (Windows 8.1 and Windows 7 SP1 are still supported).
• Dropped Windows Server 2003 and Windows XP support for all guest processing (only crash-consistent backup is now possible).

Follow this order to upgrade to v10:

  1. Veeam Enterprise Manager.
  2. Veeam Backup & Replication.
  3. Veeam Backup Console (this will automatically be upgraded after Veeam Backup & Replication).
  4. Enterprise Applications Plug-ins.

Mount the ISO Veeam downloaded from your Veeam support account.

Note: Before you start this process, bear in mind that a reboot of your Enterprise Manager and Veeam & Backup server is needed.

1 – Upgrade Veeam Enterprise Manager.

Launch Veeam Setup from the mounted ISO.

How to upgrade to the new Veeam v10

Select the option to upgrade Enterprise Manager and start the upgrade process.

The first image that you could see is the next one (it depends on your Framework and other software version needed to run Veeam Enterprise Manager v10). For System Requirements, check HERE.

Click OK to install the new version.

After Framework is installed, you need to reboot your Veeam Server (or the server where you have your Veeam Enterprise Manager installed).

After the previous reboot (if it is the case).

Mount your Veeam ISO again and select again the option 1.

As you can see in the next image, the upgrade will show you the products installed in the server and the running version.

How to upgrade to the new Veeam v10

Select your license for the v10 version.

How to upgrade to the new Veeam v10

If you provide a license that is from your previous version, you will get this error:


After the upgrade process will ask if you want to download the v10 license from your Veeam account portal automatically.


If you select Yes, then the license is automatically downloaded and applied in the installation, if you choose No, then you need to connect again to your Veeam account Portal and in the Licenses tab, select the license and choose to download the v10 version.

How to upgrade to the new Veeam v10

And then add the downloaded v10 license.

How to upgrade to the new Veeam v10

Next, you need to use the service account. You need to use the account that you used initially when you install Veeam Backup & Replication.

By default is the Local System account, but if you have a particular service account and was used previously, then you need again to use the same account.

Select your SQL DB and instance. By default, Veeam install will discover the appropriated DB and instance.

Next, Veeam upgrade process will start to upgrade Veeam Enterprise Manager DB.

How to upgrade to the new Veeam v10

Next click Install and the upgrade of the Veeam Enterprise Manager will start.


After the last step, the upgrade is done, and we can now continue to the next upgrade that is set in the above order.

After finish, the upgrade of Veeam Enterprise Manager is time to upgrade Veeam Backup & Replication.

2 – Veeam Backup & Replication.

Go back to your Veeam Upgrade Setup and select the second option to upgrade the Veeam Backup & Replication.

Again installation will show you the existed version of the Veeam that you are planning to upgrade.

Note: Don’t forget to check the system requirements before you upgrade your Veeam Backup & Replication.

Here again, is to add the v10 license. The process is the same that was already shown in the above upgrade for Veeam Enterprise Manager.

Select your Local System Account (or an account that you have for services).

Next, upgrade process will upgrade the Veeam Backup & Replication DB.

In this case, the upgrade process found some Linux Agents installed, so check if your Linux Guest OS is supported with the new Agent version 4.0. If not and you do not upgrade your Guest OS, those Linux cannot be back up.

If you have any Virtual Labs created on your Veeam Infrastructure, you need to upgrade after you finish this upgrade.

You can choose to upgrade all your remote components (likes proxies, etc.) and click to start the upgrade itself for Veeam Backup & Replication.

After the last step, your Veeam Backup & Replication is upgraded t0 v10.

3 -Veeam Backup Console.

As we can check, the Veeam Backup Console is automatically upgraded after the Veeam Backup & Replication upgrade.

After we have all Veeam Server components upgraded, Veeam Backup & Replication is fully upgraded to v10.

4 – Enterprise Applications Plug-ins.

Veeam Application Plug-ins need to be installed/upgraded manually by running the Setup on each Application folder.

Since I do not use any of these Plug-Ins, I will postpone this section.
I will came back to Plug-Ins in a future blog post.


After you enter for the first time in your new Veeam Backup Replication v10, the upgrade service will try to update your Proxies.

But sometimes the upgrade is not possible, and we need to do it manually.

When you encounter the above of error, maybe you have a not reachable proxy, and you need to do it manually. I have already written an article about how to update proxies manually.

Next will enumerate some of the errors that we can encounter while upgrading Veeam Server to v10 (some of the errors can happen upgrading to v10 or another version. Can even occur in a Veeam Backup & Replication install).

Errors found in upgrading:

1 – Error: Existing ESXi and vCenter not supported in v10.

This error is easy to identify the issue, and it shows when the upgrade process tries to upgrade Veeam DB. I have some old ESXi 5.0/5.1 configured in my Veeam Server.

To fix this issue, just identify any old ESXi or vCenter that no longer supported in v10 (again, check system requirements) and remove them from any job and remove them from the Backup Infrastructure.

In this case, was some old test lab that I had with vCenter and ESXi hosts 5.0/5.1. Removed the vCenter and ESXi hosts and click ok, and the upgrade continue to upgrade Veeam DB.

Note: vSphere 5.5 is still supported in Veeam v10.

2 – Failed to start service ‘VeeamCatalogSvc’.

This error happens when trying to upgrade the Veeam Enterprise Manager and needed to start/stop services.

Even I have known this error before, I also wrote a blog post some time ago, about this issue when upgrading HERE, I check the Catalog log to double-check if the error was the same.

Log location: C:\ProgramData\Veeam\Backup\Svc.VeeamCatalog.log

“Error Unable to sure whether all catalog folders are created. (Veeam.Backup.Common.CRegeneratedTraceException)
Error at Veeam.Backup.Common.CExceptionUtil.RegenTraceExc(Exception originalExc, String formatString, Object[] args)
Error at Veeam.Backup.CatalogFsLib.CCatStorePaths.MakeSureAllFoldersCreated()
Error at Veeam.Backup.CatalogFsLib.CCatalogStore..ctor(ICatStoreCfg cfg, CCatStoreOptions options, Boolean bMountCrawlStore, ICatFeaturesAccessibility featuresAccessibility, CTerminationMediator terminator, CCacheContext cacheContext)
Error at Veeam.Backup.CatalogDataService.CLcMngr..ctor(CTerminationMediator terminator, CAppEnvironment appEnvironment)
Error at Veeam.Backup.CatalogDataService.CVeeamCatalogSvc.OnStart(String[] args)
Error Failed to create folder ‘F:\VBRCatalog\’. (Veeam.Backup.Common.CRegeneratedTraceException)
Error at Veeam.Backup.Common.CExceptionUtil.RegenTraceExc(Exception originalExc, String formatString, Object[] args)
Error at Veeam.Backup.Common.FileSystemEx.CreateFolder(String path)
Error at Veeam.Backup.CatalogFsLib.CCatStorePaths.MakeSureAllFoldersCreated()
Error Could not find a part of the path ‘F:\VBRCatalog\’. (System.IO.DirectoryNotFoundException)
Error at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)”

Just fix the connecting, connect the volume properly and folder is back and I was able to continue the with the upgrade.

Note: In case you cannot recover the VBRCatalog folder, follow the above blog post to create a new one and redirect it to the new path.

3 – Unable to connect to SQL Server

This error happens when he upgrade process tries to connect to Veeam DB to upgrade the DB.

The first thing is to check the SQL Service if it is running.

As we can see, the service is stopped. After the reboot to install the Framework, the service did not start properly. Re-starting the service did fix the issue, and I was able to continue the upgrade.

So that Veeam DB SQL Service starts in a reboot, I change the start model to Delay Start.

After this section about upgrade errors, we are done, and Veeam Backup & Replication v10 is now installed, and all is working fine.

I hope this information was useful, and you learn how to upgrade to the new Veeam v10 and also fix some of the errors that you may encounter.

Note: Share this article if you think it is worth sharing.

©2020 ProVirtualzone. All Rights Reserved
By | 2020-12-11T16:11:02+01:00 March 6th, 2020|Backups Posts, Partners, Veeam, VMware Posts|5 Comments

About the Author:

I have over 20 years of experience in the IT industry. I have been working with Virtualization for more than 15 years (mainly VMware). I recently obtained certifications, including VCP DCV 2022, VCAP DCV Design 2023, and VCP Cloud 2023. Additionally, I have VCP6.5-DCV, VMware vSAN Specialist, vExpert vSAN, vExpert NSX, vExpert Cloud Provider for the last two years, and vExpert for the last 7 years and a old MCP. My specialties are Virtualization, Storage, and Virtual Backup. I am a Solutions Architect in the area VMware, Cloud and Backup / Storage. I am employed by ITQ, a VMware partner as a Senior Consultant. I am also a blogger and owner of the blog ProVirtualzone.com and recently book author.


  1. Chris 29/05/2020 at 17:22

    Hi ! thx a lot for this very good article. Just one thing, becareful when you say vSphere 5.x is not supported with Veeam 10. Actually, vSphere 5.0 and 5.1 are not supported, but vSphere 5.5 is supported !

    • Luciano Patrao 29/05/2020 at 19:56

      Hi Chris,

      Thanks for the reply and also thanks for the correction.

      Yes you are correct the right statement is 5.0 and 5.1, not 5.5 that is supported.

      Honestly I cannot remember witch ESXi 5.x I had on that old test lab, this is why I wrote 5.x. But I will correct the article so that is more clearly.

  2. Becks 26/07/2020 at 22:52

    HI Luciano,

    If my customer wants to upgrade their ESXi to version 7, what should i do first assuming that veeam9.x is running.

    Upgrade VEEAM to v10 first and then upgrade to ESXi ver 7 or vice versa. Please advise.


    • Luciano Patrao 28/07/2020 at 20:07

      Hi Becks,

      If you plan to do all in the same day (no backups backups between the upgrades) there is no impact on or the other. But if the plan is do that upgrade in days, or while there is backups running, then you upgrade first your Veeam to v10 Cumulative Patch 2 (build P2) since it works with ESXi 6.7 and 7. If you upgrade first the ESXi to 7.0, then you cannot backup the VMs while you do not upgrade your Veeam since 9.5 4b only is supported to 6.7 Update 3.

  3. […] is very straightforward, no need to repeat here the process again. In my previous blog post about How to upgrade Veeam Server, I have explained the process. This update process is the […]

Leave A Comment