In this article we shall discuss how to upgrade Veeam One from v12 to v13. It will interest you to know that Veeam ONE can be upgraded to version 13 starting from Veeam ONE version 12 (build #12.0.0.2498). This means, Veeam ONE 13 supports automatic in-place upgrade from version 12.0.0.2498 and newer versions to v13. This upgrade preserves all data, product settings, and configuration. Please, see [World Backup Day] V13 Upgrade Failure: Veeam Configuration Backup Saved the Day.
There is a strong business and technical need to upgrade to Veeam ONE v13 in order to leverage Veeam Intelligence, enhanced analytics, and next-generation dashboard capabilities that improve visibility, reporting, and operational decision-making as shown below.
Please see “Upgrade Path and In-Place Upgrade for VBR v13 and Known Fixes“, How to setup Veeam Software Appliance v13, and Unable to Remove Orphaned VHR Repository v2 from VBR v13.
Why Veeam ONE?
As discussed above, Veeam ONE give IT teams complete visibility into their backup and virtual infrastructure. The platform delivers real-time monitoring, intelligent alerting, reporting, and analytics for Veeam Backup & Replication, Veeam Backup for Microsoft 365, VMware vSphere, VMware Cloud Director, and Microsoft Hyper-V environments.
In addition to the above, Veeam ONE helps administrators monitor backup jobs, track infrastructure health, troubleshoot performance issues, plan capacity growth, and optimize resource usage from a single interface.
The solution combines business-focused dashboards, detailed reports, and proactive alarms to help organizations maintain availability and strengthen data protection operations. The platform includes two main components:
- Veeam ONE Web Client: Delivers dashboards and reports for capacity planning, change tracking, resource optimization, and infrastructure analysis.
- Veeam ONE Client: Provides real-time monitoring, performance analysis, troubleshooting, and administration for backup and virtual environments.
With Veeam ONE, organizations can proactively identify risks, monitor SLAs, improve operational visibility, and ensure critical workloads remain protected across modern virtual and cloud infrastructures.
Please see how to migrate Veeam One Database from SQL Server 2017 to 2025, Enhanced Proactive Monitoring with Veeam ONE, and how to install Veeam ONE and Add VBR: Fix failed to connect to VBR.
Download Veeam One Installation ISO
As mentioned above, to upgrade to version 13 is supported starting from Veeam ONE version 12 (build #12.0.0.2498). Please proceed to the following page to download the latest version of Veeam ONE.
After downloading the ISO, open the file properties and ensure the “Unblock” option is selected before mounting or extracting the file. Since the ISO was downloaded from the internet, Windows marks it with a security identifier (Mark of the Web), which can prevent certain files or scripts from executing correctly
Note: Unblocking the file removes this restriction and helps avoid installation or execution issues during the upgrade process.
Ensure Veeam ONE Services are stopped. This will ensure data consistency, prevent file locking issues, and avoid database corruption during schema changes.
Note: In short: stopping services guarantees a controlled upgrade window where nothing is actively changing underneath the installer, which is critical for a monitoring and analytics platform
Now mount or insert the disk with Veeam ONE installation image.
Thereafter, an autorun will open a splash screen with installation options. If Autorun is not available or disabled, run the Setup.exe file from the installation image as shown below.
Please see how to update Veeam Backup & Replication to Build 13.0.1.2067, how to Integrate Trellix ePolicy Orchestrator with a Syslog Server, and Veeam Backup and Replication: PowerShell must be Remote Signed.
Upgrade Veeam ONE
On the splash window click Upgrade.
Click on “Upgrade Veeam ONE” as shown below.
At the License Agreements step of the wizard. Read and accept Veeam license agreement, licensing policy, 3rd party components and required software license agreements. You will not be able to continue upgrade until you accept license agreements.
Note: To read the terms of the license agreements, click the individual links.
Shortly, the Veeam ONE Setup wizard will automatically detect components of the previous version installed on the server. Kindly review the components to upgrade and click on Next.
At the License window, click one of the two options to provide a license:
- Sign-in with Veeam: Sign in with your Veeam account credentials if you already have a registered license on your account.
- Browse licence file locally: Here, ypou can specify the local path to the license file downloaded.
To install new licenses automatically when you renew or expand your contract, select the Update license automatically check box. If you enable the automatic license update, and therefore enable usage reporting. You will double the number of workloads by which you can exceed your installed license.
Note that for Evaluation and NFR licenses automatic license update must be enabled as shown below.
As you can see below, our license details have been displayed. Click on Next.
Please see How to upgrade Veeam ONE to v12.1, how to fix Client Certificate Mapping Authentication error, and Demystifying Zero Trust with Veeam: Design your Architecture.
Specify Service Account
At the Service Account step of the wizard. Now, specify the password of the account under which Veeam ONE Service runs.
At the System Configuration Check stage, the installer verifies that all required prerequisite software is present on the system before continuing with the upgrade.
If any required components are missing. The setup wizard automatically installs and enables the necessary software features to ensure the system meets all requirements for the upgrade process.
Please see Integrate Hyper-V [SCVMM] with Veeam Recovery Orchestrator, how to replace Veeam Recovery Orchestrator License, and Why you should attend VeeamOn 2023.
Reporting Database
At the Reporting Database step, I will leave everything as deafults. Starting with Veeam ONE v13, the platform requires a PostgreSQL instance in addition to the primary Microsoft SQL Server database, either newly installed or an existing instance that meets system requirements.
Now, do not forget to uninstall the Microsoft SQL Server database from this server.
On the port configuration window, click on Next to proceed.
Please see How to apply and install Veeam NFR License, how to Fix Repository time shift detected: Immutability flag cannot be set, and how to Fix failed to connect to the backup server: Make sure it is online.
Veeam Analytics Service Status: Invalaid Class
Note: Veeam ONE replaces the Veeam ONE Agent with the Veeam Analytics Service This enables direct communication with the Veeam Backup & Replication server. The communication model has changed: Veeam Backup & Replication now sends data to Veeam ONE via port 2805 for analytics and data collection. While Veeam ONE v13 reduces outbound communication to Veeam Backup & Replication by using only port 443 for secure HTTPS communication.
As you can see below, the Veeam Analytics Service could not be started and prompted and “invalid class” error. We will proceed and complete the upgrade and fix this later later on.
Error acknolwledge and will be fixed at a latter time. Click on Ok to proceed as the Veeam Analytics Serice could not be started at this time.
On the ready to upgrade window, click on Upgrade as shown below.
Please see Prevent Automatic Driver Updates in Windows and Xen-Orchestra, how to Switch from IP Addresses to DNS for Backup Infrastructure in VBR, and how to remove a Repository from Veeam Backup and Replication.
Upgrade Status
As you can see, the upgrade of Veeam ONE is oin proggress. At this time, the Veeam ONE Client is being upgraded.
The Veeam ONE Server upgrade has kicked off.
In this step, the Veeam ONE Web Serices are now being started.
Now, the latest updates are being applied
Installations are being finalized and services are starting at this stage of the upgrade process.
As you can see below, the upgrade has finished successfully. Click on Finish to complete the upgrade process.
You will be required to perform a reboot for the configuration changes to take effect. To do this, click on “Yes”.
As you can see below, we are now running Veeam ONE Version 13.0.1.6168 as downloaded.
You can verify the license information as shown below.
Please see SQL Server 2025 Upgrade Requirements and Compatibility, how to create a backup job for Proxmox VMs using VBR, and Resolving VSS Errors: Veeam AD Backups failing with SentinelOne.
Access Veeam ONE Web and Client
To access the Veeam ONE Web Client, please double click on the web client icon on your desktop. Ensure the log in as current user ius slected and click on connect.
Please see how to download and install the Windows ADK Patches, DMA Compatibility Mode: Prepare and Migrate Safely, and Preliminary Guide for Active Directory and Initial Assessment.
Veeam Threat Center
The “Threat Center” dashboard provides a centralized security and risk overview of a backup environment. As shown in the image below, the main highlight on the left is a large risk indicator showing 36.4% with a “High Risk” label, meaning the platform’s overall security posture is below safe thresholds (under 50%).
On the right side of this score, several detailed metrics break down the situation: Platform Score is 45.7%, indicating moderate issues in infrastructure health, Data Recovery is 100%, meaning recovery capability is currently fully functional, while both Data Protection (0%) and Backup Immutability (0%) show critical gaps, suggesting backups may not be adequately protected or resistant to tampering (a major ransomware concern). You may want to read about the various argument on “If Immutable backups are the only effective defense against ransomware.”
On the right panel labeled Malware Detections, all counters (infected restore points, suspicious restore points, marked clean) are currently zero, indicating no detected threats in backups during the selected period, although a warning notes that some repositories are not assigned to a location, which could impact visibility.
A world map visualization below confirms no restore point threats found recently. Overall, the below dashboard communicates that despite strong recovery capability and no current malware detections, the environment is considered high risk due to poor protection and immutability settings, which could leave backups vulnerable to future attacks.
Please see Deploy Veeam Recovery Orchestrator and Agents to VBR and VEM, Preliminary Guide for WSUS Analysis and Initial Assessment, and how to upgrade Veeam Backup and Replication v12.3.x to 12.3.2.
Veeam ONE Client
On the other hand, below is the Veeam ONE Client interface ad we will focus on the below image since it displays the Veeam Backup & Replication monitoring and alarm management section. In the upper section (Summary tab), the dashboard provides an operational overview of backup jobs: a pie chart labeled “VM Jobs Status” displays the distribution of job results, with segments indicating Success (green), Warning (yellow), Failed (red), and Running (blue).
In this case, there is a noticeable portion of warnings and failures, suggesting issues in the backup environment. To the right, the “Agent Jobs and Policies Status” panel shows no available data, meaning no agent-based jobs are currently reporting.
Below, a bar chart titled “Top Repository Servers by Used Space” shows storage consumption, where repositories like Default Backup Repository and Backup VHR are consuming significant capacity, indicating where backup data is concentrated. Another chart, “Top Backup Proxies by Weekly Transferred Data,” is present but appears empty, suggesting no recent or insufficient transfer activity data.
The Alarms tab highlights an active error alarm related to a Veeam Backup & Replication object. The alarm list includes details such as status (Error), timestamp, source, and type, indicating a specific issue that needs attention.
On the right-hand Actions panel, options such as Resolve, Acknowledge, Assign, and Export are available, and I will resolve this alarm by adding a resolution note (“installed new nfr”) and confirming with OK.
Overall, this view demonstrates how Veeam ONE not only monitors backup infrastructure health and performance but also provides incident tracking and manual resolution workflows, allowing administrators to analyze job outcomes, identify failures, track storage usage, and formally resolve alerts for audit and operational purposes.
Fix Veeam Analytics Service Status: Invalaid Class Error
Note: Remember an error was prompted above and we have to ensure that the Veeam Analytics services is installed before starting data collection.
In Veeam v13, a major architectural change was introduced: NTLM, RPC, and WMI-based communication are being removed and replaced in favor of modern protocols (Kerberos + gRPC). This change affects how Veeam ONE deploys and communicates with the Veeam Analytics Service on the backup server.
In older setups, Veeam ONE relied heavily on WMI + NTLM authentication + Admin$ share access to push and register components. If your environment has NTLM disabled/restricted, is running in a workgroup, and lacks proper DNS/AD/Kerberos configuration, or still depends on legacy WMI-based communication, the installation or interaction with the Analytics Service can fail.
Sometimes producing misleading errors like “Invalid Class” (which normally points to WMI issues but can actually be triggered by failed service deployment or authentication error). This error shows a real case where the Analytics Service push fails and authentication is rejected. Even with correct credentials, because the underlying communication method has changed and legacy mechanisms no longer work properly.
As you can see below, we have successfully installed the “Veeam Analytics Service” and the status is healthy again.
Now, start your data collection. When VBR becomes unhealty again, ensure that the analytics services is running as a local system if it does not work correctly with your local Administrator’s account.
Note: As stated above, now that you have completed the upgrade and validated that Veeam ONE is functioning correctly. You can proceed to uninstall the Microsoft SQL Server database components from the server if they are no longer required.
This cleanup step helps free system resources and ensures the environment only retains the PostgreSQL database used for Veeam ONE v13 operations.
I hope you found this article on how to upgrade Veeam One from v12 to v13 very useful. Please feel free to leave a comment below.
