Veeam ONE 13.1 Release Notes

This document provides last-minute information about Veeam ONE version 13.1, including system requirements, installation and upgrade procedure, as well as relevant information on technical support, documentation, online resources, and so on.

The release version of Veeam ONE 13.1 is available for download at: https://my.veeam.com/my-products starting from July 29, 2026.

Resolved Issues

The following issues have been resolved in Veeam ONE v13.1.

Alarms

• The Backup Copy RPO alarm continues to trigger for a backup job even after that job has been removed from the backup copy job.
• The Backup Job State and Agent Backup Job State alarms behave incorrectly for job retries — triggering on a retry attempt, or failing to raise a warning when a session finishes with a warning.
• Alarms can stop triggering after the database retention (cleanup) task completes.
• Alarms can stop triggering after an alarm export/import, including the Backup Job State alarm for Veeam Backup & Replication high-availability (HA) clusters.
• The SQL Server Express database size alarm uses an incorrect size limit on SQL Server 2025 and later, producing inaccurate notifications.

Dashboards and Threat Center

• In Threat Center, the RPO Anomalies widget shows duplicate workloads across all Veeam Backup & Replication servers when multiple servers share the same host.
• The RPO Anomalies widget continues to display virtual machines from plug-in–managed platforms (KVM, Proxmox, Oracle Linux VM, XCP-ng, and Scale Computing) after the virtual machine, its backup, and its job have all been deleted.

Data Collection and Infrastructure Monitoring

• Restore points stored on cloud provider (Cloud Connect) repositories display an incorrect immutability date.
• The scale-out backup repository (SOBR) data transfer session state is not reported correctly when a session does not transfer any restore point.
• Tape server data, including file-to-tape job statistics, is not displayed in the Veeam ONE Client.
• Collecting data from a Microsoft System Center Virtual Machine Manager (SCVMM) server can fail with “Object synchronization method was called from an unsynchronized block of code.”
• A Hyper-V failover cluster cannot be added when the cluster name contains one of its node names as a substring (“Specified server is not a Failover Cluster”).
• The collector stops receiving data from a Veeam Backup & Replication server after the server’s monitoring agent ID changes, due to a stale peer cache.
• The Veeam ONE Monitoring Service can crash (0xC0000005) after a specific Veeam Backup & Replication server is added.
• Adding a Veeam Backup Enterprise Manager server, or testing host credentials, can take an excessively long time (over 80 seconds) or time out with “the server is not available.”
• Veeam ONE could stop collecting data from a specific Veeam Backup & Replication server, and re-adding the server or restarting its collector task did not restore collection.
• Data collection from a Veeam Backup & Replication server could fail with a “maximum allowed timeout” error when a system proxy was configured on the Veeam ONE server.
• Data collection from a Veeam Backup & Replication server could get stuck and never finish when the server stopped responding to a data request, so that server’s data was no longer updated.
• Signing in to Veeam ONE Web with “Log on as current user” did not work.
• VMware Cloud Director tenant users could not log in to the Veeam ONE Web Client when their Cloud Director was older than version 10.3

Reporting

• The Restore Operator Activity report shows incorrect values in the Restored Object column, so the name or IP address of the restored machine may be missing.
• The Latest Job Status report for Veeam Backup for Microsoft 365 does not display detailed information when the volume of text is very large.
• The Job Configuration Change Tracking report fails to generate with the error “Failed to get data set ‘User’ from report.”
• Report generation could fail because the timeout counted time spent waiting in the queue. A new ReportTimeoutMinutes setting now controls the report generation timeout independently of queue time.
• Scheduled reports now support page format and orientation options, and the table of contents is no longer missing.
• Testing the connection to the Reporter Web Service in Veeam ONE Settings fails with “Failed to connect to the specified server. Version mismatch.”
• After the Web API certificate is replaced with a third-party SSL certificate, Report Booster stops working and returns a 500 error.
• A missing service dependency between the Reporter and Caching services can prevent report caching from starting (“Failed to connect to the Reporter service”).
• A clear, actionable error is now shown when the required PostgreSQL ltree extension is not installed, instead of a generic 500 error on remote Linux PostgreSQL.
• The Caching Service can stop connecting to PostgreSQL using Windows authentication after the service account is switched to Local System on servers with a German locale.
• The Backup Objects Change Tracking report becomes empty after some time when an Enterprise Manager scope is used.
• Boosted reports can fail with “Data caching in progress” when the Business View tree collection task encounters unexpected data; the task no longer fails in this case.
• The SkipVbrRequiredCollectionCheck setting does not work in Enterprise Manager topologies, preventing the Caching Service from starting caching for boosted reports.
• The Workload Protection History report does not display data for enterprise application plug-ins (such as SAP HANA) older than three months.
• The Workload Protection History report rounds values on the Success and Failure Rates History chart, causing a discrepancy between the summary and the chart.
• The Workload Protection History report does not plot the failure rate on the Success and Failure Rates History chart when the value is below 1%.
• The Workload Protection History report stops listing a job under the Jobs report parameter after that job is deleted in Veeam Backup & Replication.
• The Protected Computers report returns non-deterministic results for agents managed by multiple jobs, so some protected computers with existing restore points may not appear.
• The Job History report can contain incorrect data when a job’s main and retry sessions are returned in different Report Booster queries.
• The Job History report shows no data for public cloud (Veeam Backup for public clouds) policies.
• The Backups on Repository report does not include unmanaged plug-ins and enterprise applications.
• Kasten policy jobs appear in the Latest Job Status report with no option to exclude them.
• The Job History report data collection task can fail and cause excessive tempdb growth.
• The Backup Billing report now accounts for metadata backups.
• The Backup Billing report could show usage figures that did not match Veeam Backup & Replication, for example after restore points were moved between extents of a scale-out backup repository.
• The Backup Billing report did not correctly account for data stored in the object storage capacity tier.
• The Backup Billing report was missing data for some jobs whose restore points were stored on repositories that had since been removed.
• On large infrastructures, several reports fail to generate with “Failed to cache data for reporting” or “Unable to load dataset from the database,” in some cases caused by an arithmetic (BigInt) overflow. This is resolved for the Backup Infrastructure Assessment, Capacity Planning for Backup Repositories, Cluster Configuration, Veeam Backup Files Growth, Unmapped Datastore LUNs, Orphaned VM Snapshots, How Many More VMs Can Be Provisioned, and Host Failure Modelling reports.

Scalability and Performance

• The VeeamDCS service does not release memory from the staging (composite) cache after the initial data collection, leading to high memory consumption.
• VMware Cloud Director tenant login to the Web Client is slow; login performance has been significantly improved.
• Under sustained memory pressure, the Veeam ONE Monitor Service can stop accepting incoming client connections. A new memory-pressure safeguard now protects service availability.
• Veeam ONE Client performance is poor in large environments when the IgnoreDeletedEntities setting is enabled.
• The VeeamDCS service crashes intermittently — at least once a day — without generating a dump or error.
• The Analytics Service accumulates partial query results when DIS/WMI enumeration fails, causing 10–20+ GB of memory growth on the Veeam Backup & Replication agent.
• The SQL Server tempdb database grows uncontrollably after a VeeamDCS restart.
• Generating a large number of reports in parallel causes the Reporter service to hang.
• Environments with a large number of vSphere virtual machines that have no saved creator experience high database load.
• After upgrading to v13, the Veeam ONE service could keep crashing due to high memory usage.

Licensing

• The Veeam Backup for Microsoft 365 license capacity alarm could report a “License exceeded” condition when consumption was actually within the licensed limit.
• Rental licenses that include newly added packages are not updated.
• License consumption by virtual machines is calculated incorrectly in some cases when virtual machines are matched with agents.

Log Collection and Diagnostics

• The LogAnalyzerTempFolder registry key no longer takes effect.
• Log analysis (Veeam Intelligent Diagnostics) sessions are very slow on high-load servers.
• CDP task session logs (CDPTaskSessionLog) are not collected.
• The size of Veeam Backup & Replication logs collected on the agent has been reduced to lower storage and transfer overhead.
• The VeeamDCS.log file grows indefinitely (up to 1.5 GB and beyond).
• The AnalyticsService.Host.log is filled with unnecessary “Unable to open contract…” messages for deleted agents after a repair.
• The Analytics Service log no longer records misleading “untrusted root” certificate errors.
• Collecting and analyzing Veeam Backup & Replication logs could fail on large or slow servers, returning a timeout error.

Security and Certificates

• After the Veeam ONE Web API self-signed certificate expires, an uninformative error is displayed when opening Reporter Web; the error message is now clear and actionable.
• Web Client gRPC communication can fail (“Error starting gRPC call”) due to incompatible TLS cipher suites. Veeam ONE now applies the operating system’s cipher suite settings to gRPC and exposes local SSL settings in the registry.

Integrations and Notifications

• Alarms are not delivered to Syslog after periods of inactivity.
• Not all Veeam ONE alarms are forwarded to Syslog.
• ServiceNow incident creation fails when the incident short description exceeds 100 characters; longer descriptions are now handled correctly.
• Microsoft Graph delegated OAuth authentication fails because the refresh token expires when Conditional Access sign-in frequency is enforced.
• Requests to the REST API could return a “502 Bad Gateway” error when using filters or limits on protected data and applications.

Installation and Upgrade

• Upgrade fails when the SQL Server login has no permissions on the msdb database.
• Upgrade can fail while installing extension modules with “Object reference not set to an instance of an object.”
• Upgrading to v13 or later fails when a vCenter Server or ESXi host at version 7.0.0 is present in the infrastructure.
• Upgrading a very large ObjectProperty table (INT-to-BIGINT column conversion) causes excessive transaction-log growth; identifiers are now processed in batches.
• The Upgrade Wizard does not explain that PostgreSQL is a new auxiliary database, causing confusion during upgrade.
• Installing web components in a distributed deployment fails with “The client and server cannot communicate, because they do not possess a common algorithm.”
• The Veeam Analytics Service reports “Failed to install” after a Repair from the web UI, even though the repair completed successfully on the host.
• Deployment of the Veeam Analytics Service can fail because connections to the Windows Service Control Manager (SCM) are not retried.

System Requirements

For the latest system requirements and compatibility information, see the Veeam Help Center articles listed below.

These articles are maintained continuously and reflect the latest supported workloads, backup infrastructure requirements, and platform compatibility.

All-in-One Deployment

• Veeam ONE Server requirements: Veeam ONE Server.
• Microsoft SQL Server for Veeam ONE requirements: Microsoft SQL Server.
• Veeam ONE Reporting Database requirements: Reporting Database.
• Veeam ONE Web Services requirements: Veeam ONE Web Services.
• Veeam ONE Client requirements: Veeam ONE Client.
• Veeam ONE Web Client requirements: Veeam ONE Web Client.

System Requirements for Large-Scale Deployments

For large-scale Veeam ONE deployments starting from 1,000 workloads, use dedicated infrastructure components to achieve the performance required in enterprise environments.

• Veeam ONE Server requirements: Veeam ONE Server on a dedicated machine.
• Microsoft SQL Server for Veeam ONE requirements: Microsoft SQL Server on a dedicated machine.

Review these articles before installing or upgrading Veeam ONE.

Known Issues

General

• Changing the Veeam ONE services to run under the Local System account causes the Veeam ONE Reporting Service and Veeam ONE Caching Service to fail to start if the Veeam ONE database uses Windows Authentication. Switch the database connection to SQL Server Authentication before changing the account.
• Veeam ONE v13 and v13.1 installation or upgrade will fail if an active PostgreSQL instance is selected and the connection limit is reached.
• Licenses with new packages introduced in for Veeam v13 or later builds, are not displayed in the login to license option while installing or upgrading.
• Some Veeam ONE functionality might not operate as expected when using Windows 11 with Smart App Control enabled. This includes Veeam ONE installation, Veeam ONE Reporting Service functionalities and more. It is recommended to disable Smart App Control when using Windows 11 with Veeam ONE.
• Email notifications sent from an alias using the new OAuth method will display the user ID as the sender instead of the alias.

Veeam Threat Center

• Data Recovery mini-widget, part of the Data Platform Scorecard widget, does not include replication, tape, or Veeam CDP restore points.

Jobs Calendar

• Backup jobs scheduled to run continuously may not be displayed in Veeam ONE Jobs Calendar.

Security

• A user with Multi-Factor Authentication (MFA) enabled cannot complete the distributed setup if MFA is enabled but not yet configured, or when using silent setup. To resolve the issue, temporarily disable MFA for the account used for installation, run the setup, and then re-enable MFA afterwards.
• In a distributed deployment, the Certificate Management tab in Veeam ONE Web Client not display the Veeam ONE Website certificate and the Veeam ONE Web client communication certificate, because the Web Services certificate data is retrieved remotely from the machine hosting the services and not all fields can be populated.
• A user with Multi-Factor Authentication (MFA) enabled cannot complete the distributed setup if MFA is enabled but not yet configured, or when using silent setup. To resolve the issue, temporarily disable MFA for the account used for installation, run the setup, and then re-enable MFA afterwards.
• In a distributed deployment, the Certificate Management tab in Veeam ONE Web Client not display the Veeam ONE Website certificate and the Veeam ONE Web client communication certificate, because the Web Services certificate data is retrieved remotely from the machine hosting the services and not all fields can be populated.
• If Veeam ONE Server runs on Microsoft Windows Server 2022 or Microsoft Windows 11, Veeam ONE Audit Log is placed in the wrong node of Event Viewer if there is no access to the Windows event log.

Veeam Backup for Microsoft 365

• Retrieving data from a Veeam Backup for Microsoft 365 organization added using basic authentication may take significant time.

Veeam Backup & Replication

• Next Job Run data is not available for Scale Computing HyperCore, HPE Morpheus VM Essentials, Sangfor aSV, and Xen on the Protected Data tab in Veeam ONE Client
• Repositories located on the same disk display identical used space values, as used space is calculated as capacity minus free space. This data is not yet provided per repository by Veeam Backup & Replication.
• Certain antivirus software, such as ESET, may block communication between Veeam ONE and Veeam Backup & Replication servers via PowerShell and gRPC if SSL/TLS traffic inspection is enabled. As a result, data collection and Veeam Intelligent Diagnostics operations may fail. To resolve the issue, disable SSL/TLS protocol filtering or add exclusions as described in Veeam KB1999.
• The new Veeam Analytics Service is compatible only with Veeam Backup & Replication v12 or later.
• For the Backup Repositories using ReFS, in order to collect ReFS events from these, credentials must be set manually on Veeam ONE Client.
• After upgrading to Veeam ONE v13 or later builds, if using Veeam Backup & Replication Analytics, click Reconnect to clear cached links.
• When using Veeam Backup & Replication Analytics, the Replica Billing report option “Configure individual datastore price multipliers” shows all datastores instead of only those within the Veeam Backup & Replication scope.
• “Suspicious increment size” alarm does not support agent backup policies targeted to local, NFS, and SMB (CIFS) backup repositories.
• Performance data for backup proxy servers of Veeam Cloud Connect providers is not collected.
• Data of Veeam Agent for Mac backup policies targeted to cloud repositories is not shown on the “Computers” tab of Cloud Connect repositories, Business View category and group summary views, and corresponding reports on tenant Veeam ONE servers.
• Collecting OS performance metrics from JeOS-based Veeam Backup & Replication proxy and repository appliances over HTTPS requires the appliance certificate to be imported into the Trusted Root Certification Authorities store on the Veeam ONE server. Because the appliance certificate does not include the IP address in its SAN, these appliances must be added to Veeam Backup & Replication by hostname (FQDN).

Veeam Backup & Replication High Availability

• When a high-availability cluster is added using the DNS name of the primary node, reports and widgets may inconsistently display the cluster by IP address in some places and by DNS name in others. Adding the cluster by IP address avoids this issue.
• Veeam Backup & Replication high-availability clusters may appear duplicated in the web interface if the Veeam Backup & Replication server was added to Veeam ONE before clustering and the cluster was added afterward. The issue affects report scopes, the Data Collection view, and other web UI areas.
• Veeam Backup & Replication servers added to Veeam ONE before being configured as secondary nodes in a Veeam Backup & Replication high-availability cluster may display incorrect data after clustering. The secondary node database is overwritten with data from the primary node and collected into the Veeam ONE database. To resolve the issue, remove the affected Veeam Backup & Replication server from Veeam ONE and add the high-availability cluster instead.

VMware vSphere

• VMware vSphere tags are not collected from VMware Cloud on AWS infrastructures.

Microsoft Hyper-V

• “Infrastructure Overview (Visio)” report does not work correctly for Hyper-V infrastructures that have a logical dynamic disk with allocation on several physical datastores.

Veeam ONE Client

• Users with restricted permissions do not see unlicensed infrastructure objects in Veeam ONE Client, as if they do not have the required permissions assigned on the virtual infrastructure.

Veeam ONE Web Client

• Users with restricted permissions must re-log in to Veeam ONE Web Client after a new object is added to a container in the virtual infrastructure. Otherwise, users will not be able to perform reporting actions with the object.
• Users with restricted permissions cannot log in to Veeam ONE Web Client using the “Log in as current user” option.

Alarms

• The “Potential malware in backups” alarm is not triggered for restore points that were marked as infected manually.
• Connection state alarms may be falsely triggered for all types of Veeam Backup & Replication nodes during master-agent data collection. This behavior is not observed when using the new agent-based data collection. For reliable results, use the new Veeam Analytics Service for data collection.
• The new remediation action for the suspicious malware activity doesn’t work for VMs where the Operating System is in hibernate or sleep state.

Reports

• Verified VMs report displays “No data” when an ESXi host under a vCenter Server is selected as the scope.
• The Workload Protection History report does not display data for the “Target Type”, “Snapshot Name”, and “# of Storage Snapshots” columns, as this information is not yet available to Veeam ONE.
• When upgrading to v13 or later builds, custom filters applied to Backup Infrastructure Custom Data report are not retained. Open the saved report and reapply the filters manually.
• All the Backup Proxies columns from Backup Infrastructure Custom Data have been moved to a dedicated section for proxies.
• XML, Word, and Excel formats have been deprecated. Customers using these formats will now receive PDF instead of Word, and CSV instead of XML or Excel.
• Reports built using Report Builder that combine Microsoft SSRS and New Reporting Engine reports in a single scheduled report will result in an error.
• Backup Infrastructure Custom Data report generation and scheduling fail after upgrade if the report was saved with more than 15 columns.
• Backup Infrastructure Custom Data report ignores column selection in parameters. Selected columns in parameters are used only for data loading, while displayed columns follow the default report configuration.
• New Reporting Database Reports fail to run on schedule during the initial historical data collection after upgrade. Scheduling works as expected after the first data collection completes.
• In large environments, the initial new reporting engine historical data collection for the report may take multiple hours.
• Veeam Malware Detection does not include replication or Veeam CDP restore points.
• Generating multiple reports at the same time using Business View as a scope fails with an error “Invalid object name ‘reporter.LatestObjectProperty’”.
• Previewing reports may result in an error if Veeam ONE Services, SSRS, and the Web UI SSL certificate have been issued by different CAs (for example if each component belongs to a different domain or workgroup).

Reporting Database

• PostgreSQL 17 installation fails on Microsoft Windows operating systems with the tr-TR locale due to unsupported non-ASCII characters in the locale name.

ServiceNow Integration

• ServiceNow ticket creation might get delayed up to 40 minutes for new alarms, when Veeam ONE has a large number of unresolved alarms.

Upgrade

• Scripts configured for execution in schedules created in previous versions of Veeam ONE will not run after upgrade. Edit the affected schedules and re-add the required scripts.
• When performing a silent upgrade without a local PostgreSQL instance and using the parameter , the upgrade may fail with the error “Failed to connect to 127.0.0.1:5432.” This is expected behavior, as the PostgreSQL service is not installed on the target system.
• Veeam Backup & Replication server appears with an “Unhealthy” status if the environment contains Microsoft Entra ID backup jobs created before Veeam Backup & Replication v12.3.1. To resolve the issue, recreate or update the affected Microsoft Entra ID jobs.
• In large environments, upgrading Veeam ONE may take several hours. To reduce upgrade time, a script included in the ISO can be run beforehand to create the necessary indexes without service disruption. Contact Veeam Technical Support for assistance.
• During the upgrade, a wrong administrator idle session timeout value can be found if there was a custom value in UiSessionTimeoutMinutes. You can manually set the correct value in Configuration > Security > Login Sessions.
• Microsoft Report Viewer 2015 Runtime component installed with previous versions of Veeam ONE or manually is not uninstalled automatically during the upgrade and can be safely removed manually if required.

Installing Veeam ONE

Refer to Veeam ONE User Guide for more information: veeam.com/one-docs.

Uninstalling Veeam ONE

1. From the Start menu, select Add or remove programs.
2. In the programs list, select Veeam ONE and click the Remove button.

   Refer to Veeam ONE User Guide for more information: veeam.com/one-docs.

Upgrading Veeam ONE

Veeam ONE 13 supports automated in-place upgrade from version 12 and later versions which preserves all data, products settings, and configuration. To upgrade from earlier versions, please contact Veeam Customer Support.

Upgrade checklist:

• Perform a backup of the SQL database for Veeam ONE, so that you can easily revert to the previous version in case of issues with the upgrade.
• If you have Veeam Backup & Replication servers connected to Veeam ONE, upgrade Veeam ONE first; Veeam Backup & Replication must be upgraded after Veeam ONE.
• Make sure you are using as a minimum Veeam ONE version 12 (build number 12.0.0.2498) or above.
• Make sure Veeam ONE Client is installed on a supported operating system.
• Refer to Veeam ONE User Guide for more information: veeam.com/one-docs.

Licensing

Veeam ONE can be licensed per protected workload with Veeam Universal License (VUL). For more information, see Veeam Licensing Policy at veeam.com/licensing-policy.html

The trial license key is sent to you automatically after downloading the product. The trial license is valid for 30 days from that moment and includes Basic technical support.

To obtain a full license key, please refer to veeam.com/buy-veeam-products-pricing.html

Subscription VUL and Perpetual VUL licenses include a maintenance plan with Premium support. To renew or upgrade your maintenance plan, contact Veeam Renewals at veeam.com/renewal.html

Veeam ONE license does not put any restrictions on the number of managed Veeam Backup & Replication servers.

There are two versions of Veeam ONE: Community and full version with complete functionality. The community version does not require a license file during installation.

The product defaults to the Community version if you do not provide a license during installation.

Refer to Veeam ONE User Guide for more information about licensing: veeam.com/one-docs.

Technical Documentation References

If you have any questions about Veeam ONE, you may use the following resources:

• Product web page: veeam.com/virtualization-management-one-solution.html
• User guides: veeam.com/one-docs
• R&D forums: veeam.com/forums

To view the product help, press the F1 key or select Configuration > About from the main menu of Veeam ONE Web Client.

Technical Support

We offer email and phone technical support for customers on maintenance and during the official evaluation period. For a better experience, please provide the following when contacting Veeam Customer Support:

• Version information for the product and all infrastructure components.
• Error message and/or accurate description of the problem.
• Log files. To export the log files, select Help > Support Information from the main menu of Veeam ONE Client.

To submit your support ticket or obtain additional information, please visit https://www.veeam.com/support.html.

Contacting Veeam Software

At Veeam Software, we pay close attention to comments from our customers — and make it our mission to listen to your input, and to build our products with your suggestions in mind. We encourage all customers to join Veeam R&D Forums at https://forums.veeam.com and share their feedback directly with the R&D team.

Should you have a technical or licensing issue or question, please feel free to contact our Customer Support organization directly. We have qualified technical and customer support staff available 24 hours a day, 7 days a week who will help you with any inquiry that you may have.

Customer Support

For the most up-to-date information about our support practices, business hours, and contact details, please visit https://www.veeam.com/support.html. You can also use this page to submit a support ticket and download the support policy guide.

Company Contacts

For the most up-to-date information about company contacts and office locations, please visit https://www.veeam.com/contacts.html.