Veeam Support Knowledge Base

Applications Restored by Veeam Kasten Disaster Recovery Fail to Export with: invalid repository password

2026-09-04T00:00:00Z

Applications Restored by Veeam Kasten Disaster Recovery Fail to Export with: invalid repository password

KB ID:	4910
Product:	Veeam Kasten for Kubernetes
Published:	2026-09-04
Last Modified:	2026-09-04

Challenge

After a Veeam Kasten Disaster Recovery (KDR) restore is performed on an instance of Veeam Kasten for Kubernetes running a version earlier than 8.5.4, and that instance is later upgraded to version 8.5.4 or newer, export and backup actions for the restored applications fail with an error similar to the following:

invalid repository password

The restore points imported by the KDR restore are present in the catalog, but any policy or export action that references them afterward fails.

Cause

This issue occurs because Veeam Kasten for Kubernetes versions earlier than 8.5.4 import application restore points into the local catalog without correctly linking the encryption key artifact (EKA) to the corresponding repository artifact. The catalog entry appears complete, but the repository password derived from it does not match, so any later operation that requires decrypting or reconnecting to that repository fails.

The binding behavior was corrected in version 8.5.4. That correction applies to restore points imported after the upgrade, so restore points that were already imported under the earlier binding remain broken in the catalog.

Solution

Starting in Veeam Kasten for Kubernetes 9.0.5, the KastenDRRestore resource supports the forceReimportAppRestorePoints option. When this option is set to true, every application restore point being imported is reprocessed and its repository artifact is rebound to a valid encryption key, including restore points that were already imported successfully by an earlier KDR restore.

The repair is applied by running a new KDR restore with this option enabled. The option is a field on the KastenDRRestore resource, so the repair restore is performed using the CLI or API method, regardless of how the original KDR restore was performed.

Confirm that the Veeam Kasten for Kubernetes instance is running version 9.0.5 or later.
Edit or create the KastenDRRestore resource for the affected restore, and set forceReimportAppRestorePoints to true:

apiVersion: dr.kio.kasten.io/v1alpha1
kind: KastenDRRestore
metadata:
  name: sample-kdrrestore
  namespace: kasten-io
spec:
  sourceClusterInfo:
    profileName: my-profile
    sourceClusterID: 
  forceReimportAppRestorePoints: true

Alternatively, reference a restore point from an existing KastenDRReview resource:

apiVersion: dr.kio.kasten.io/v1alpha1
kind: KastenDRRestore
metadata:
  name: sample-kdrrestore
  namespace: kasten-io
spec:
  kastenDRReviewDetails:
    kastenDRReviewRef:
      name: 
      namespace: kasten-io
    id: 
  forceReimportAppRestorePoints: true

Run the KDR restore as described in Recovering Veeam Kasten from a Disaster via CLI.
Once the restore has completed, verify that the export or backup action that previously failed for the affected application now succeeds.

More Information

Note: Do not enable forceReimportAppRestorePoints for a KDR restore performed on a clean installation, or for the first KDR restore performed on a cluster. In those cases no existing bindings are present to repair, so the option is unnecessary.

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Release Information for Veeam Service Provider Console 9 and Updates

2026-09-04T00:00:00Z

Release Information for Veeam Service Provider Console 9 and Updates

KB ID:	4788
Product:	Veeam Service Provider Console \| 9 \| 9.1 \| 9.2 \| 9.3
Published:	2025-10-21
Last Modified:	2026-09-04

Veeam Service Provider Console 9 Builds

9.3.0.35706

2026-09-04

Resolved Issues

Scalability

When a large number of management agents connect to the Veeam Service Provider Console Portal at the same time, the management agent installed on the Veeam Cloud Connect server can be disconnected.

Veeam Backup & Replication Integration

Under certain conditions, manual patching of managed backup servers can take a long time.
VMware Cloud Director (VCD) backup jobs are not mapped to the corresponding company when the VCD server name ends with / or \.
The Veeam Backup & Replication Health Check Session state alarm reuses the description from the Job Session state alarm.
Malware status for a protected object cannot be resolved for orphaned backups.

REST API

Company usage endpoints take 10-20+ seconds per call after an upgrade on installations with a large history of stored metrics.

9.3.0.35057

2026-07-29

Release Information

9.2.1.33875

2026-05-27

Resolved Issues

Security

CVE-2026-32998 | Severity: Critical (9.4)
A vulnerability in Veeam Service Provider Console allows for remote code execution.
CVE-2026-64635 | Severity: Medium (5.3)
A vulnerability in Veeam Service Provider Console that allows an unauthenticated attacker to hijack the password reset link and take over a user account.
Third-party libraries and packages used in Veeam Service Provider Console and its components have been updated to their latest versions to address discovered vulnerabilities. (See: KB4856)

General

Under certain conditions, a managed company cannot be deleted from the Veeam Service Provider Console Portal, displaying the error:
```
Value cannot be null (Parameter 'first')
```
Companies that are mapped to VMware Cloud Director tenants with WAN Accelerators enabled are displayed without the WAN Accelerator option in the Veeam Service Provider Console Portal.
The Reports page in the Veeam Service Provider Console Portal fails to load when there are more than 15,000 reports available.
The discovery rule cannot discover Ubuntu 26.04 machines.

Upgrade

Under certain conditions, after the upgrade, users cannot log in to the Veeam Service Provider Console Portal.

Veeam Backup & Replication Integration

The Veeam Software Appliance (Linux-based Veeam Backup & Replication) secondary node of the HA Cluster disappears from the Veeam Service Provider Console Portal after the failover operation is performed and the Veeam Service Provider Console server services are restarted.
Under certain conditions, the Backup repository connection state alarm is triggered incorrectly in the Veeam Service Provider Console Portal.

Veeam Cloud Connect Integration

Under certain conditions, a tenant cannot be removed from Veeam Service Provider Console because of a data mismatch between Veeam Service Provider Console and Veeam Cloud Connect database records.

**Veeam Backup for Microsoft 365 Integration**

Under certain conditions, a licensed Microsoft 365 user is reported as unlicensed on the Protected Data page.
Under certain conditions, the licensed and educational user properties shown in the Protected Data table are not updated after upgrading to the most recent version of Veeam Service Provider Console.
Under certain conditions, the Veeam.AC.Agent.VB365.Satellite.exe process consumes a lot of RAM on the Veeam Backup for Microsoft 365 server.

Veeam Vault Integration

Filters applied on the company selection step of the Vault Plugin wizard are ignored when the Select All option is checked. This results in tenant creation for all managed companies.
In the New Tenant creation wizard, client subscriptions are not hidden (not filtered) on the Subscription step when the bulk tenant creation option is used. This results in Vault subscriptions being displayed to all companies upon tenant creation, even if those companies don't have access to them.

Veeam Agent Integration

Veeam Agent for Mac is not installed when deploying it with the management agent using the installation ZIP package downloaded from Veeam Service Provider Console.
Veeam Agent for Linux backup jobs targeted to an object storage repository with immutability enabled cannot be edited.

REST API

The (GET) /replicationResources/usage method returns the wrong replica count after the replication job is recreated.
The (GET) /api/v3/infrastructure/backupServers/jobs endpoint returns HTTP 500 when any backup job's session task contains a DateTime value out of valid range for DateTimeOffset conversion.
The (GET) /api/v3/protectedWorkloads/computersManagedByBackupServer/backups endpoint returns HTTP 404 when the managed server has both Veeam Backup & Replication and Veeam Backup Enterprise Manager installed, with the message:
```
Cannot find Backup Server with ID {guid}
```

9.2.0.33215 (9.2 GA)

2026-04-09

Release Information

9.1.0.30713

2025-12-05

New Features and Enhancements

General

Veeam Backup & Replication Integration

File-level restore wizards are now available directly in the Veeam Service Provider Console, enabling a seamless user experience and improving operational efficiency.

Scalability and Optimizations

The data collection and processing procedures for managed Veeam Backup & Replication servers have been optimized, improving overall scalability and stability of the backup portal.
The parallel processing of management agent requests to the backup portal has been optimized, improving the overall scalability of the solution.
The Veeam Software Appliance HA handling procedure has been optimized to avoid management agent connection issues.
The management agent database is now automatically compacted when it reaches a certain threshold of free pages, allowing for more efficient use of disk space on the machine where the management agent is installed.

Security

The reset user password functionality has been optimized to further minimize the possibility of user data hijacking.

Alarms

The minimal threshold for PRO-based alarms has been set to 15 minutes to avoid misconfigurations and false-positive occurrences.

Resolved Issues

General

Veeam Cloud Connect servers may be unregistered from the backup portal when multiple data collection errors occur.
Under certain conditions, Veeam Backup Enterprise Managers running on Linux OS cannot be registered in the backup portal.
Under certain conditions, the error "Unexpected error has occurred. Contact the technical support team for assistance." appears when refreshing any page in the VSPC UI.

Security

When logging into the web PowerShell console in the backup portal, the session always runs under the account used by the management agent service (e.g., Local System), not the actual user’s credentials who started the PowerShell session. This allows privilege escalation for any authenticated user.

Deployment

Veeam Service Provider Console cannot be installed on Microsoft Windows 10 22H2.

Upgrade

Under certain conditions, customer job mappings configured for hosted Veeam Backup & Replication servers might be reset after upgrading from VSPC v8.x.
The backup portal malfunctions after upgrade when duplicate records are detected in the stored backup data.
Under certain conditions, after upgrading to VSPC v9.1, the backup portal web UI may be unable to connect to the server.

Alarms

In some situations, RPO-based alarms may be triggered even when there is no actual issue, resulting in false positives.

Management Agent

The The Veeam.AC.Agent.JobManager.exe process consumes CPU resources inefficiently on managed Veeam Backup & Replication servers, resulting in spikes in CPU usage.

Backup Agent

Under certain conditions, backup policies with Cloud Connect repositories fail to be assigned to Veeam Agent for Linux.
After upgrading Veeam Agent for Mac running on a physical machine to v13.0.1 via the backup portal, the agent stops working.
The checkbox "Back up directly from live file system" works inversely in the backup portal for Veeam Agent for Mac backup jobs.
Backup jobs for Veeam Agent for Linux v13.0.1 cannot be edited when the object storage repository is used as the destination target and retention is set to use the number of restore points to keep instead of days.
Under certain conditions, backup policies with Cloud Connect repository can only be targeted to a default repository assigned to a tenant.

Veeam Backup & Replication Integration

Under certain conditions, redirection of backup job creation and restore wizards to managed backup servers fails.
Under certain conditions, patching Veeam Backup & Replication servers v13 fails.
Manual triggering of a full recollection cycle for managed backup servers is not possible.

Veeam Cloud Connect Integration

Under certain conditions, after upgrade, Veeam Cloud Connect tenants may be unmapped from VSPC companies.

Veeam Backup for Public Cloud Integration

Under certain conditions, the procedure for adding existing backup appliances to the backup portal fails when parsing the appliance's security certificate.

Veeam ONE Integration

After upgrading the VSPC server to v9.1, the Alarms Data Collection toggle for managed Veeam ONE servers is switched off.

Notifications

After upgrading to v9.1, incorrect locale settings are used in the date format for email notifications.

Reporting

Orphaned backups from upgraded Veeam Cloud Connect servers are not displayed on the Protected Data page.

Plugins

ConnectWise Manage and Veeam Agent File-Level Restore Portal Web UIs cannot start with:
```
Decoded string is not a valid IDN name. (Parameter 'unicode')
```

REST API

An incorrect value is returned for the parameter "blockSize" in the method: /infrastructure/backupAgents/linux/{backupAgentUid}/jobs/configuration.
REST API v3.4 was reinstated after being removed from the product specification in v9.1; however, this API version is now marked as deprecated, and customers are advised to plan to switch to a higher version of the VSPC REST API.

9.1.0.30636 (9.1 GA)

2025-11-19

Release Information

9.1.0.30345 (9.1 RTM)

2025-11-07

Release Information

9.0.0.29860

2025-10-21

This repack of build 9.0.0.29555 addresses potential upgrade issues and includes most critical fixes discovered at the early availability stage.

Resolved Issues

Upgrade

Under certain conditions, the upgrade process may fail with this error message:
```
The system cannot find the file specified.
```

Data Collection

Under certain conditions, the management agent fails to process data from managed Veeam Backup & Replication servers. This results in high memory consumption by the agent and delays in showing actual data in the Veeam Service Provider Console UI

Licensing

After upgrading to version 9, the backup portal stops pushing the license attribute to managed backup agents.

9.0.0.29555

2025-09-03

Release Information

Download Information

Deployment Guidance

New Deployments of Veeam Service Provider Console, use the ISO.
Upgrading existing VSPC v9.1 and v9.2 Deployments, use the ISO.
- For 8.1 and 9.0 deployments, please review the notes in the upgrade section of the product user guide.
Updating existing VSPC v9.3 (build 9.3.0.35057) Deployments, use the patch.

Patch Install

If at least version Veeam Service Provider Console 9.3 (build 9.3.0.35057) is already installed, download the cumulative patch below and perform the following steps to update to the latest Cumulative Patch:

Back up the Veeam Service Provider Console configuration database.
Log off from all active Veeam Service Provider Console Portal sessions.
Using an Administrative Command Prompt or Administrative PowerShell console:
- Execute VSPC.ApplicationServer.x64_9.3.0.35706.msp on the Veeam Service Provider Console server.
- Execute VSPC.WebUI.x64_9.3.0.35706.msp on the Veeam Service Provider Console Web UI server.

Download Patch

^{Filename: VSPCv9.3Patch1_9.3.0.35706_20260901.zip}

SHA256: C504E6864E58CF4A3B4516A839C4ECD84FD6B74A9E9F164F97EF4999A1AA389B

Reboot may be required

Please note that a reboot may be required after installing the update.

Please plan accordingly.

Deployment ISO

DOWNLOAD latest 9.3 ISO

See the Current Version Download Page for ISO hashes.

ISO Release History

^{Previously released files are not publicly available for download. Mouse-over or tap the filenames in the table to view a file's checksum.}

Release Date	ISO Filename	Changelog
Veeam Service Provider Console 9 Releases
2026-09-04	VeeamServiceProviderConsole_9.3.0.35706_20260901.iso^{SHA256: 931553A86DE4478A726AC0E59313D894BB21FA7B35817B1C1873EAB099F8887B}	Initial Release
2026-07-29	VeeamServiceProviderConsole_9.3.0.35057_20260726.iso^{SHA256: C2B0CE5B3B537912656A861044CAA46EAAE0A3DF50FAB585BF3A4BBAAE656F13}	Initial Release
2026-05-27	VeeamServiceProviderConsole_9.2.1.33875_20260522.iso^{MD5: BA48514257C225215826F7D0DDEE83F1 SHA1: 77A8DAB3E4F00D9D058BA3EDFB3121DAC827604B}	Initial Release
2026-04-09	VeeamServiceProviderConsole_9.2.0.33215_20260408.iso^{MD5: A816199DD6BB4244DDFBE3D7C1E1D99A SHA1: 9D3F44309101B0FA66CD66E6BFB70FB05747E98D}	Initial Release
2025-12-05	VeeamServiceProviderConsole_9.1.0.30713_20251203.iso^{MD5: B9467A75C0BA2C97EFB22721E2D16903 SHA1: A26FF0E9E67B9F7039801BE6464E9F910B9431F9}	Initial Release
2025-11-19	VeeamServiceProviderConsole_9.1.0.30636_20251117.iso^{MD5: 261685F88D51204A80DF7E8201485C60 SHA1: 89662902E2479984AD778FB9ADD88E2B7D6913E0}	Initial Release
2025-11-07	VeeamServiceProviderConsole_9.1.0.30345_20251105.iso^{MD5: 91CEEECE2621D0D4D06E1D7836876E72 SHA1: 07F7000843E652D89F3D9388047F0742858E02F6}	Initial Release
2025-10-21	VeeamServiceProviderConsole_9.0.0.29860_20251020.iso^{MD5: 0821F41C556E45902913BDB5EAF261AC SHA1: E198ACBF385674346A4053CC4D6D2BB20D3E8AD4}	Initial Release
2025-09-03	VeeamServiceProviderConsole_9.0.0.29555.iso^{MD5: 807C647C1B5D1E2245002A24D5381F0A SHA1: 862D123C0CE0EC22B1E6447BC8D98BF64422DBFA}	Initial Release

Swipe to show more of the table

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Build Numbers and Versions of Veeam Service Provider Console

2026-09-04T00:00:00Z

Build Numbers and Versions of Veeam Service Provider Console

KB ID:	4464
Product:	Veeam Service Provider Console \| 4.0 \| 5.0 \| 6.0 \| 7.0 \| 8.0 \| 8.1 \| 9 \| 9.1 \| 9.2 \| 9.3 Veeam Availability Console \| 2.0 \| 2.0_U1 \| 3.0
Published:	2023-06-16
Last Modified:	2026-09-04

This KB article lists all versions of Veeam Service Provider Console and their respective build numbers.

For more information on downloading the latest version of Veeam Service Provider Console, visit:

Version	Build Number	Release Date	Release Notes
Veeam Service Provider Console 9 Releases
Veeam Service Provider Console 9.3 Patch 1	9.3.0.35706	2026-09-04	KB4788
Veeam Service Provider Console 9.3	9.3.0.35057	2026-07-29	HTML
Veeam Service Provider Console 9.2.1	9.2.1.33875	2026-05-27	KB4788 HTML
Veeam Service Provider Console 9.2	9.2.0.33215	2026-04-09	HTML
Veeam Service Provider Console 9.1 Patch 1	9.1.0.30713	2025-12-05	KB4788
Veeam Service Provider Console 9.1 GA	9.1.0.30636	2025-11-19	HTML
Veeam Service Provider Console 9.1 RTM	9.1.0.30345	2025-11-07	KB4788
Veeam Service Provider Console 9 CP1	9.0.0.29860	2025-10-21	KB4788
Veeam Service Provider Console 9	9.0.0.29555	2025-09-03	HTML
Veeam Service Provider Console 8 Releases
Veeam Service Provider Console 8.1 CP1	8.1.0.21999	2024-12-03	KB4651
Veeam Service Provider Console 8.1	8.1.0.21377	2024-08-28	HTML KB4651
Veeam Service Provider Console 8 CP2	8.0.0.19552	2024-05-28	KB4509
~~Veeam Service Provider Console 8 CP2~~ (Note)This build was retracted and rereleased as build 8.0.0.19552. For more information review KB4509.	~~8.0.0.19236~~	2024-05-06
Veeam Service Provider Console 8 CP1	8.0.0.18054	2024-03-04
Veeam Service Provider Console 8	8.0.0.16877	2023-12-05	PDF
Veeam Service Provider Console 7 Releases
Veeam Service Provider Console 7 P20240516	7.0.0.19551	2024-05-28	KB4441
Veeam Service Provider Console 7 P20240412	7.0.0.18899	2024-05-06
Veeam Service Provider Console 7 P20230531	7.0.0.14271	2023-06-05
Veeam Service Provider Console 7 P20230321	7.0.0.13157	2023-03-21
Veeam Service Provider Console 7 GA	7.0.0.12777	2023-01-30	PDF
Veeam Service Provider Console 6 Releases
Veeam Service Provider Console 6 Patch 1	6.0.0.8787	2022-02-02	KB4277
Veeam Service Provider Console 6 GA	6.0.0.7739	2021-09-27	PDF KB4212
Veeam Service Provider Console 5 Releases
Veeam Service Provider Console 5 Patch 4	5.0.0.7151	2021-10-12	KB4223
Veeam Service Provider Console 5 Patch 3	5.0.0.6959	2021-05-22	KB4163
Veeam Service Provider Console 5 Patch 2	5.0.0.6883	2021-03-25	KB4127
Veeam Service Provider Console 5 Patch 1	5.0.0.6838	2021-03-03	KB4116
Veeam Service Provider Console 5 GA	5.0.0.6726	2021-02-24	PDF KB4111
Veeam Service Provider Console 4 Releases
Veeam Service Provider Console 4 Patch 2	4.0.0.4914	2020-07-23	KB3237
Veeam Service Provider Console 4 Patch 1	4.0.0.4911	2020-07-03	KB3211
Veeam Service Provider Console 4 GA	4.0.0.4877	2020-03-31	PDF KB3040
Veeam Availability Console 3 Releases
Veeam Availability Console 3 Patch 4	3.0.0.2795	2020-01-23	KB3036
Veeam Availability Console 3 Patch 3	3.0.0.2762	2019-09-20	KB3003
Veeam Availability Console 3 Patch 2	3.0.0.2725	2019-06-17	KB2960
Veeam Availability Console 3 Patch 1	3.0.0.2703	2019-04-11	KB2934
Veeam Availability Console 3 GA	3.0.0.2647	2019-03-28	PDF
Veeam Availability Console 2 Update 1 Releases
Veeam Availability Console 2 U1 Patch 1913	2.0.2.1913	2018-12-21	KB2835
Veeam Availability Console 2 U1 Patch 1850	2.0.2.1850	2018-11-15	KB2795
Veeam Availability Console 2 U1 Patch 1824	2.0.2.1824	2018-10-05	KB2781
Veeam Availability Console 2 U1 Patch 1817	2.0.2.1817	2018-08-30	KB2715
Veeam Availability Console 2 U1 Patch 1807	2.0.2.1807	2018-07-30	KB2694
Veeam Availability Console 2 U1 GA	2.0.2.1750	2018-06-19	PDF
Veeam Availability Console 2 Releases
Veeam Availability Console 2 Cumulative Patch 1376	2.0.1.1376	2017-12-21	KB2418
Veeam Availability Console 2 GA	2.0.1.1319	2017-11-14	PDF
Veeam Managed Backup Portal 1 Releases
Veeam Managed Backup Portal 1	1.0.0.295	2016-03-24	-

Swipe to show more of the table

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

After Veeam ONE 13.1.0.7034 Upgrade: No connection could be made because the target machine actively refused it. (localhost:2743)

2026-09-03T00:00:00Z

After Veeam ONE 13.1.0.7034 Upgrade: No connection could be made because the target machine actively refused it. (localhost:2743)

KB ID:	4912
Product:	Veeam ONE \| 13.1
Published:	2026-09-03
Last Modified:	2026-09-03

Article Applicability

The issue described in this article only occurs for deployments in which Veeam ONE was installed to a folder other than the default C:\Program Files\Veeam\Veeam ONE\ path.

Challenge

After Veeam ONE is upgraded to version 13.1 (build 13.1.0.7034), reports cannot be generated and the following error occurs:

No connection could be made because the target machine actively refused it. (localhost:2743)

The Veeam ONE Caching Service log contains entries similar to the following:

[ERR] DelayedLogSaver - Failed to save log record  of type Veeam.Reporter.CachingService.Repository.Entity.EventLog.JobSessionEventEntity, will retry save it later
System.InvalidOperationException: An exception has been raised that is likely due to a transient failure.
 ---> Npgsql.NpgsqlException (0x80004005): Failed to connect to [::1]:5432
 ---> System.Net.Sockets.SocketException (10061): No connection could be made because the target machine actively refused it.

Cause

This issue occurs because the appsettings.overrides.json file is placed in the default installation folder on the system drive rather than in the Veeam ONE Caching Server folder of the custom installation path. The upgrade updates the Veeam ONE Caching Service files in the custom installation folder correctly, but the configuration file that the service reads is written to the default folder instead.

That file supplies the Veeam ONE Caching Service with the connection settings for the Veeam ONE database. Without it, the Caching Service cannot connect to the database and does not accept connections on TCP port 2743, which is the port the Veeam ONE Web Client uses to request cached report data.

Solution

To resolve this issue, update Veeam ONE to version 13.1 Patch 0 (build 13.1.0.7233) or later. The patch places the appsettings.overrides.json file in the correct folder and restores the Veeam ONE Caching Service connection to the Veeam ONE database.

The patch is documented in KB4762: Release Information for Veeam ONE 13 and Updates.

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

How to Allow Company Users to Open Veeam Backup & Replication Web UI Wizards From Veeam Service Provider Console

2026-09-01T00:00:00Z

How to Allow Company Users to Open Veeam Backup & Replication Web UI Wizards From Veeam Service Provider Console

KB ID:	4908
Product:	Veeam Service Provider Console \| 9.3
Published:	2026-09-01
Last Modified:	2026-09-01

Purpose

This article documents how to allow company users to open Veeam Backup & Replication web UI wizards from Veeam Service Provider Console for backup servers managed by their company.

Starting with Veeam Service Provider Console 9.3, users can perform restore operations by redirecting to the Veeam Backup & Replication web UI wizards from Veeam Service Provider Console. For details, see the Restoring Veeam Backup & Replication Workloads section of the Veeam Service Provider Console Guide for Service Providers.

Access to the wizards depends on the user type:

Service provider users: The wizards are available by default.
Company users: The wizards are disabled by default and must be explicitly enabled using the configuration key described in this article.
Reseller users: The wizards are not available, regardless of the configuration key.

If a company user attempts to open a Veeam Backup & Replication web UI wizard while the key is disabled, the operation fails with the following error:

Cannot open the Veeam Backup & Replication wizard because this capability is not enabled for your organization. Contact your service provider for assistance.

Scope of the Configuration Key

The configuration key described in this article affects the Veeam Backup & Replication web UI wizards only. It does not affect redirecting to the Veeam Backup & Replication web UI itself, which remains available to service provider users only.

Solution

To allow company users to open Veeam Backup & Replication web UI wizards, add a configuration key on the machine where the Veeam Service Provider Console Server component is installed:

Open the following file in a text editor:
C:\ProgramData\Veeam\Veeam Availability Console\Configuration\Service\configuration.overrides.json

The same folder can also contain incremental configuration files named configuration.overrides.NNNNNNNN.json. Those files are generated and merged automatically, and should not be edited manually.
Add the following key inside the root JSON object (or change its value if the key is already present):
```
"ClientAgent_TreatClientAgentsAsCompanyOwned": "true"
```
Key Name: ClientAgent_TreatClientAgentsAsCompanyOwned
Value Type: Boolean
Value Data:
true — company users can open Veeam Backup & Replication web UI wizards for backup servers managed by their company.
false — the functionality is available to service provider users only.
Default: false
Save the file. The configuration file is monitored for changes, so a short delay can occur before the change is applied.
Restart the Veeam Management Portal Service (service name: VeeamManagementPortalSvc).

The service can be restarted using the following PowerShell command:

Restart-Service VeeamManagementPortalSvc

To revert to the default behavior, set the key value to false (or remove the key) and restart the service.

Additional Requirements for Company Users

Regardless of this configuration key, the Enable redirecting to Veeam Backup & Replication web UI wizards toggle must be enabled for the backup server, and the company user must have a role that permits the corresponding restore operations, such as Company Owner or Company Administrator. For details, see the Configuring Remote Access section of the Veeam Service Provider Console Guide for Service Providers.

More Information

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Build Numbers and Versions of Veeam Backup for Google Cloud

2026-09-01T00:00:00Z

Build Numbers and Versions of Veeam Backup for Google Cloud

KB ID:	4359
Product:	Veeam Backup for Google Cloud \| 1 \| 2 \| 3 \| 4 \| 5 \| 6 \| 7
Published:	2022-09-22
Last Modified:	2026-09-04

This KB article lists all versions of Veeam Backup for Google Cloud and their respective build numbers.

For more information on deploying the latest version of Veeam Backup for Google Cloud, visit:

Starting with the release of Veeam Backup & Replication 12.1, the What's New information for integrated products, like Veeam Backup for Google Cloud, is included in the Veeam Backup & Replication What's New PDF.

Version	Build Number	Release Date	Release Notes
*Veeam Backup for Google Cloud* 8 Releases**
Veeam Backup for Google Cloud 8	8.0.0.237	2026-09-01	HTML
*Veeam Backup for Google Cloud* 7 Releases**
Veeam Backup for Google Cloud 7.0.1	7.0.1.4	2026-05-27	KB4859
Veeam Backup for Google Cloud 7	7.0.0.47	2025-11-19	HTML
*Veeam Backup for Google Cloud* 6 Releases**
Veeam Backup for Google Cloud 6	6.0.0.21	2024-12-03	HTML
*Veeam Backup for Google Cloud* 5 Releases**
Veeam Backup for Google Cloud 5 Patch 2	5.0.2.41	2024-08-28	KB4560
Veeam Backup for Google Cloud 5 Patch 1	5.0.1.1343	2024-03-18	KB4560
Veeam Backup for Google Cloud 5	5.0.0.1297	2023-12-05	HTML
*Veeam Backup for Google Cloud* 4 Releases**
Veeam Backup for Google Cloud 4	4.0.0.1082	2023-09-20	KB4497
	4.0.0.1080	2023-07-06	KB4471
	4.0.0.1072	2023-02-14	PDF
*Veeam Backup for Google Cloud* 3 Releases**
Veeam Backup for Google Cloud 3	3.0.0.868	2022-12-16	KB4383
Veeam Backup for Google Cloud 3	3.0.0.859	2022-06-16	PDF
*Veeam Backup for Google Cloud Platform* 2 Releases**
Veeam Backup for Google Cloud Platform 2 P1	2.0.0.535	2021-10-13	KB4220
Veeam Backup for Google Cloud Platform 2	2.0.0.530	2021-08-18	PDF
*Veeam Backup for Google Cloud Platform* 1 Releases**
Veeam Backup for Google Cloud Platform 1	1.0.0.288	2021-02-03	PDF

Swipe to show more of the table

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Proxmox VE Worker VM Deployment Fails When Default Local Storage Is Disabled

2026-08-31T00:00:00Z

Proxmox VE Worker VM Deployment Fails When Default Local Storage Is Disabled

KB ID:	4906
Product:	Veeam Plug-In for Proxmox VE
Published:	2026-08-31
Last Modified:	2026-08-31

Challenge

When attempting to deploy or test a worker VM, the operation fails with the following errors:

Failed to deploy the worker VM: Cannot access a closed Stream.
Worker  test failed: Cannot access a closed Stream.

This may also occur after an upgrade, when the existing worker VM is recreated and the redeployment fails.

Cause

This issue occurs because the storage that Veeam Backup & Replication is configured to use for worker VM deployment does not provide the ISO image and Snippets content types.

During deployment, the worker image is written to the ISO image directory of that storage, and the worker's cloud-init configuration is written to its snippets directory. By default, Veeam Backup & Replication uses the Proxmox VE local storage, which on a default installation carries both content types. This storage is separate from the storage where the worker VM's disks are mounted, so selecting a different storage for worker VMs does not remove the requirement.

Solution

A worker VM can only be deployed to a host that provides file-level storage with the ISO image and Snippets content types enabled. The storage must also support snapshots. LVM storage that uses the Snapshots as Volume Chains (SAVC) mechanism cannot be used for worker files.

If the default local storage was disabled unintentionally, enable it on the affected Proxmox VE nodes, then test each existing worker VM before a job is run. If the default storage cannot be used in the environment, configure an alternative as described below.

Configuring an Alternative File-Level Storage

In the Proxmox VE web interface, identify a file-level storage that is available on every node where a worker VM will be deployed. Confirm that both the ISO image and Snippets content types are enabled on it, and note the storage ID.

In the example below, the storage ID is NFS-truenas.

Example

On the Proxmox VE host, review the storage definition in /etc/pve/storage.cfg to determine its path value, for example:

nfs: NFS-truenas
        export /mnt/RAIDZ2-pool/proxmox-nested
        path /mnt/pve/NFS-truenas
        server 10.9.2.5
        content iso,images,snippets
        preallocation off
        prune-backups keep-all=1

Example

Confirm that the expected directories exist at that path. In a multi-node cluster, confirm this on every node where a worker VM will be deployed.
```
# ls /mnt/pve/NFS-truenas
images  snippets  template
```

Update the plug-in configuration to use the storage identified in step 1. The steps differ by deployment type:

Instructions for Veeam Software Appliance

How to Customize the VSPC Welcome Email

2026-08-31T00:00:00Z

How to Customize the VSPC Welcome Email

KB ID:	3138
Product:	Veeam Service Provider Console \| 9 \| 9.1 \| 9.2
Published:	2020-04-02
Last Modified:	2026-08-31

Article Applicability

This article is relevant only to Veeam Service Provider Console 9.2 and older.

Starting in Veeam Service Provider Console 9.3, the email template model has been changed and can no longer be customized as described in this article.

Purpose

This article documents how to customize the Welcome emails sent out by Veeam Service Provider Console.

Solution

Requirements and Considerations for Modifying the Welcome Email Template File

To modify the Welcome email template file effectively, proficiency in XML, HTML, and XSLT is essential. While simple text edits are accessible to most, a complete redesign of the email's layout might require expertise in web design to ensure optimal presentation and functionality.

Customizing the Welcome Email:

Download the Welcome email template file from this article.
On the Veeam Service Provider Console server, create a new folder named “Template” for the custom email in this directory:
C:\Program Files\Veeam\Availability Console\ApplicationServer\
Save the Welcome email template (WelcomeEmail.xslt) file and place it in that “Template” folder.
C:\Program Files\Veeam\Availability Console\ApplicationServer\Template\
Modify the Welcome email template file as needed.

Tip: Changes to the template can be previewed using the Preview welcome email... link in the Notifications section when editing a company.

Download Information

DOWNLOAD TEMPLATE

_{Updated: 2025-02-06}^{Filename: KB3138_WelcomeEmailTemplate_20250203.zip}

MD5: 0895F3D862E451DE88B43228D59D2C37
SHA1: 1A6945680251AE8D5E23243EF1A28F792375F416

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Release Information for Veeam Backup & Replication 13 and Updates

2026-08-27T00:00:00Z

Release Information for Veeam Backup & Replication 13 and Updates

KB ID:	4738
Product:	Veeam Backup & Replication \| 13 \| 13.1
Published:	2025-09-03
Last Modified:	2026-09-02

Release Information

13.1.1.18

2026-08-12

Resolved issues

Veeam Software Appliance

After upgrading a Veeam Software Appliance (Linux-based Veeam Backup & Replication) that is configured to use an HTTP or HTTPS proxy, core services fail to start and the Web UI returns HTTP 502 errors along with the message:
```
Failed to connect to identity service
```
Clean installations are not affected.

Object Storage Repository

Backup jobs that write directly to immutable object storage fail with the error:
```
Blockset blocks immutability mismatch
```

Guest Processing

Backup jobs with application-aware processing enabled report the following warning for Windows guest machines running a PostgreSQL instance, including embedded instances installed by third-party applications:
```
Failed to explore PostgreSQL instance
```

Cloud Connect

After upgrading a tenant deployment to 13.1, Backup Copy jobs targeting a Cloud Connect repository fail when the service provider uses a publicly trusted SSL certificate and the certificate revocation cache is empty.

Veeam Agents

Veeam Agent for Microsoft Windows 13.1.1.700
Veeam Agent for Linux 13.1.1.4
Veeam Agent for Mac 13.1.1.3

13.1.0.411

2026-07-29

Security

Vulnerabilities

CVE-2026-58070 | Severity: Medium (6.8)
A vulnerability that causes guest OS credentials used for Application Aware processing to be recorded in cleartext in logs on the guest machine.

13.0.3.63

2026-08-25

Release Notes

Previous Version Availability

Veeam Backup & Replication 13.0.3.63 is available from the Previous Versions download page.

Security

Vulnerabilities

CVE-2026-58070 | Severity: Medium (6.8)
A vulnerability that causes guest OS credentials used for Application Aware processing to be recorded in cleartext in logs on the guest machine.

13.0.2.29

2026-05-27

Security

Vulnerabilities

CVE-2026-32996 | Severity: High (7.3)
A vulnerability in Veeam Agent for Microsoft Windows allows for Local Privilege Escalation.
CVE-2026-32997 | Severity: High (8.6)
A vulnerability allowing an authenticated user with the Backup Administrator role to write arbitrary files on a Linux-based Veeam Backup & Replication server (Veeam Software Appliance).

Resolved issues

General

Removal of the BUILTIN\Administrators group from Users & Roles does not correctly remove permissions from users in that group.
Veeam Backup & Replication causes excessive logging of Event ID 0.
The History tab fails to display historical information correctly.

Remote Console

The Veeam Backup & Replication Console auto-update process fails on systems with non-English locales.

Note: As the issue is within the Veeam Backup & Replication Console application, after updating the Veeam Backup Server, remote deployments of the Veeam Backup & Replication Console on systems with non-English locales must be manually updated.
The Veeam Backup & Replication Console installer downloaded via the Web UI is not at the latest version, requiring additional patching after installation to match the installed server.
When the Veeam Backup & Replication Console connects to multiple remote Veeam Backup & Replication deployments at the same version, the auto-update process runs redundantly, and connection behavior is inconsistent. (Improved patched-file detection in the Console auto-update process so it correctly identifies already-current installations.)

High Availability

Creating a high-availability cluster may reset the PostgreSQL OOMScoreAdjust setting, increasing the risk of the service being terminated by the operating system under memory pressure.

NFS Repository

Resetting the NFS share context also resets the NFS directory cache settings configured by the deployment service.

Object Storage Repository

Checkpoint removal on Azure-based object storage repositories fails with an InvalidQueryParameterValue error when the VersionId parameter is incorrectly set to null.
Operations with Azure-based Capacity Tier and Archive Tier repositories fail due to the use of a deprecated Microsoft endpoint.

Data Domain Repository

DDBoost credentials are not properly validated before checking repository availability.
Multiple repositories backed by the same Data Domain system must share a single set of DDBoost credentials, preventing per-repository credential isolation and separate Storage Unit ownership.
(Added support for using multiple DDBoost credentials with a single Data Domain system.)

Guest Processing

Backup or replication jobs for Windows virtual machines hosted on Nutanix AHV, Proxmox VE, or Scale Computing HyperCore fail with one of the following errors:

Failed to install guest processing components for [VM name]. Error: Failed to connect to the guest OS.

Failed to prepare guest for hot backup. Error: Cannot start service. Machine: [IP address]. Service: [VeeamGuestHelper]. Cannot start service. Win32 error: The service did not respond to the start or control request in a timely fashion. Code: 1053

For more information, see KB4842.

Enterprise Manager

Logon to Windows-based Enterprise Manager fails due to a SAML authentication failure.

Microsoft Hyper-V

Hyper-V replica virtual machines may become unbootable in rare scenarios.
Orphaned records related to Hyper-V infrastructure objects persist after the underlying objects are removed.
Guest processing of Windows Server 2025 virtual machines fails.

Unstructured Data Backup

After a source job in a Backup Copy job is removed, that Backup Copy job fails with the error:
```
Unable to find cache settings for server
```
Backup jobs targeting S3 repositories in Direct connection mode may incorrectly start gateway components on the backup server.

Veeam Agents

Veeam Agent for Microsoft Windows 13.0.3.1220
- File-level restore operations using Entra ID accounts may fail, potentially leading to LSASS crashes with InvokerTestConnection errors.
Veeam Agent for Linux 13.0.2.2
- Veeam Agent for Linux cannot be installed on x86_64 distributions of RHEL 9.8, RHEL 10.2, or Ubuntu 26.04 LTS. (Added platform support for x86_64 distributions of RHEL 9.8, RHEL 10.2, and Ubuntu 26.04 LTS.)
Veeam Agent for IBM AIX 13.0.2.2108
Veeam Agent for Oracle Solaris 13.0.2.2108
- ZFS enumeration may cause a segmentation error on Veeam Agent deployments running on SPARC systems.

File-Level Restore

Helper appliance settings are resolved based on the backup service account instead of the user initiating the file-level restore session.

13.0.1.2067

2026-03-12

Security

Vulnerabilities

CVE-2026-21669 | Severity: Critical (9.9)
A vulnerability allowing an authenticated domain user to perform remote code execution (RCE) on the Backup Server.
CVE-2026-21670 | Severity: High (7.7)
A vulnerability allowing a low-privileged user to extract saved SSH credentials.
CVE-2026-21671 | Severity: Critical (9.1)
A vulnerability allowing an authenticated user with the Backup Administrator role to perform remote code execution (RCE) in high availability (HA) deployments of Veeam Backup & Replication.
CVE-2026-21672 | Severity: High (8.8)
A vulnerability allowing local privilege escalation on Windows-based Veeam Backup & Replication servers.
CVE-2026-21708 | Severity: Critical (9.9)
A vulnerability allowing a Backup Viewer to perform remote code execution (RCE) as the postgres user.

Third-Party Component Vulnerabilities

CVE-2026-31431 | Severity: High (7.8) | Commonly known as Copy Fail

New features and enhancements

Veeam Data Cloud Vault

Backup server authorization now communicates directly with Veeam Data Cloud (VDC), removing the need to be a License Admin. Now, any user with the right VDC permissions can register a server.
The Web UI registration process has been improved and is now code-based: the backup server generates a registration code, which is entered into the VDC portal. This replaces the previous redirect-based authentication method to improve security.

General

Improved the Support Log bundle collection tool to more efficiently identify and collect relevant log files needed by support. The net result is that log bundles are now significantly smaller.

Resolved issues

General

Importing a backup from a Windows SMB share may fail when specifying the full path to a .vbk file, with the error:

Failed to create LinuxAbsolutePath from . Reason: An absolute path in Linux must begin with the root (/) character. (Parameter 'value')

When updating RHEL infrastructure servers with the DISA STIG profile enabled, the public GPG key used to validate Veeam packages will be updated as well.
To ensure a smooth update for these systems, it's recommended to temporarily disable the fapolicyd service (if it's in use) during the update.
Fixed an issue where the Veeam vSphere vCenter plugin could fail to initialize and return an HTTP 404 error.
Increased the default Service Version Timeout to 120 seconds to reduce timeout‑related failures.

Scale-Out Backup Repository

Exporting backups to a Scale-Out Backup Repository with an NFS-based performance extent may fail when a retention period is specified.

Object Storage Repository

When backing up to an object storage repository in direct connection mode, the backup server may be incorrectly selected as the gateway server even when other backup proxy servers are available, which can impact performance.

Application Plug-ins

Application plug-in installation may fail with a "no digest" error when using the .rpm package on an OS with FIPS mode enabled.
A "hostname mismatch" error occurs when the plug-in connects to VBR using a custom self-signed certificate.
An "Unable to get local issuer certificate" error occurs when the plug-in connects to VBR using a certificate signed by an internal CA.
When using centralized plug-in management for Oracle RMAN, Microsoft SQL Server, SAP HANA, or SAP on Oracle, the default backup operator role does not have permission to manage the application backup policy.

Unstructured Data Backup

Unstructured Data Backup policies targeting a Hardened Repository may fail when the policy name contains special characters, with the error:
```
Failed to create NAS backup storage
```

Primary Storage

Backup jobs using IBM FlashSystem storage snapshots as a source may complete with a Warning status when Volume Protection mode is enabled on the array.
Dell PowerStore USAPI plug-in fails to connect after upgrading to version 13.0.1 due to an exception caused by an SSL/TLS settings mismatch, causing the error:
```
Could not establish trust relationship for the SSL/TLS secure channel
```
Long-running operations with storage systems could be prematurely canceled due to the default 100-second HTTP client timeout.

Restore to Microsoft Azure

Restoring a Windows-based machine to Microsoft Azure may result in a non-bootable VM. The restore session log contains the following warning:
```
vdmount::CVhdMounter::Mount: step = 5, error = 1392: 00000570
```

Veeam Agents

Veeam Agent for Microsoft Windows 13.0.2.1102
Veeam Agent for Linux 13.0.1.404
- Creating an S3-compatible object storage repository may fail on certain S3-compatible storage systems if the endpoint returns HTTP 503 (Service Unavailable) during the connection test.
Veeam Agent for Mac 13.0.1.402
- Creating an S3-compatible object storage repository may fail on certain S3-compatible storage systems if the endpoint returns HTTP 503 (Service Unavailable) during the connection test.

File-Level Restore

Other OS file-level restore (FLR) mounts may take an excessive amount of time when many preferred networks are configured. To work around this issue, configure the preferred IP address used by the mount server to connect to the backup repository by creating the following registry value on the backup server:

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: FlrMountPreferredIp
Value Type: String Value (REG_SZ)
Value Data:

Tape

Multiple related issues were fixed, resulting in a significantly improved UI experience

Microsoft Entra ID

Adding a Microsoft Entra ID tenant and running Microsoft Entra ID backup jobs may fail in environments where Internet access is available only through an HTTP/HTTPS proxy (proxy settings are not applied).

Veeam Cloud Connect

Cloud Connect service may experience excessive memory consumption when a service provider uses a datastore cluster as a target for replication jobs
Backup configuration jobs targeting an object storage repository fail with the error:
```
Job session with id ‘’ was not found (System.Exception).
```

Web UI

Veeam Intelligence fails to open when multi-factor authentication (MFA) is enabled.

13.0.1.1071

2026-01-06

Security

Vulnerabilities

CVE-2025-55125 | Severity: High (7.2)
This vulnerability allows a Backup or Tape Operator to perform remote code execution (RCE) as root by creating a malicious backup configuration file.
CVE-2025-59468 | Severity: Medium (6.7)
This vulnerability allows a Backup Administrator to perform remote code execution (RCE) as the postgres user by sending a malicious password parameter.
CVE-2025-59469 | Severity: High (7.2)
This vulnerability allows a Backup or Tape Operator to write files as root.
CVE-2025-59470 | Severity: High (9.0)
This vulnerability allows a Backup or Tape Operator to perform remote code execution (RCE) as the postgres user by sending a malicious interval or order parameter.

Post-Release Live Updates

Important features and fixes that were pushed to Veeam Software Appliances via the live-update system.

Improvements to the archive log file management. A new cron job runs hourly to help eliminate older diagnostic log files when the volume storing the Veeam logs exceeds 90% capacity.

Resolved issues

General

Excessive audit failure events are generated within the Windows Event Log during normal operation of the Veeam.Backup.IdentityService.exe process.

Microsoft Hyper-V

During guest interaction proxy selection, the Hyper-V host is skipped, resulting in the Veeam Backup Server being used instead.
Hyper-V replication jobs fail during incremental runs with the error:
```
hexadecimal value 0x00, is an invalid character.
```
The replication job wizard does not save custom destination paths after editing, causing the destination path to reset to the default value instead of retaining the user-defined path.

When attempting to add network mapping for a replication job to a Cloud Connect target, the process fails with the following error:

Unable to cast object of type 'Veeam.Backup.Common.CCloudNetworkInfo' to type 'Veeam.Backup.Common.CHvSwitchInfo'. (System.InvalidCastException)

Editing a standalone Hyper‑V host fails with the error:

Creating configuration database records. Error: Host [] does not exist in database

Unable to cast object of type 'System.DBNull' to type 'System.String'

Guest processing

Backup jobs for Linux VMs fail with the following error when application-aware processing is disabled and indexing is enabled:
```
Cannot find Linux guest credentials.
```

Unstructured data

Copy Backup and Health Check sessions cannot be stopped once initiated.
The Get-VBRUnstructuredBackupFLRItem -Recurse PowerShell cmdlet intermittently fails to return all items.

Old backups fail to be imported with the errors:

Attempted to divide by zero

and

Failed to deserialize long-term meta

It is impossible to create a new directory in an Instant Recovery share when using Samba server version 4.22.4 on the Linux mount server.

Veeam Agent for Windows 13.0.1.1009

The Veeam Agent for Windows executable setup incorrectly blocked installation on Windows 10 21H2 LTSC IoT.
An unexpected synthetic full backup is triggered during a scheduled job launch of Veeam Agent for Windows, even if no previous backup sessions were missed.
After encryption is enabled, local backup chain transformation, after a Health Check, fails with the error:
```
FOREIGN KEY constraint failed
```

Veeam Agent for Linux 13.0.1.203

Added compatibility for RHEL 9.7 & 10.1, Rocky Linux 9.7 & 10.1, AlmaLinux 9.7 & 10.1, and SLES 16.0 Linux distributions.

Object Storage Repository

The immutability setting [For the minimum immutability duration only] was not correctly enforced for GFS backups, resulting in longer-than-intended immutability periods.

Note: This update corrects the enforcement. To avoid unexpectedly shortening immutability for existing GFS backups, all existing object storage repositories will be automatically set to: [For the entire duration of their retention policy]. New repositories will not be affected. Backup administrators can revert existing repositories to [For the minimum immutability duration only] after reviewing which restore points will be impacted by the corrected behavior.

Tape

The Online and Offline subfolders for Media in the Tape Infrastructure node are missing.
Changes to the state of the Archive Incremental checkbox are not saved after editing and closing the backup to tape job.
The "This day" option for a monthly schedule cannot be set correctly, and the selected months are not applied.
File backup to tape jobs hang during incremental backup operations.
Tenant restore from tape fails with the error:
```
Cannot find full backup.
```
Multiple yearly storages are missing under Backups → Tape in the console, despite being displayed correctly under tape properties.

Veeam Plug-In for Kasten

K10 instances cannot be edited or rescanned after upgrading from version 12.3 to 13.0.1.
Sync failed after upgrading from version 12.3 to 13.0.1 when K10 instances have certain specific policies configured.

Microsoft EntraID

Starting a Microsoft Entra ID restore from an encrypted backup after upgrading from version 12.3.2 to 13.0.1 results in the error:
```
Cannot find Microsoft Entra ID backup repository for the backup custom EntraID job.
```

Cloud Connect

The license report for Cloud Connect providers incorrectly displays 0 points for tenant consumption.
Datastore Cluster cannot be selected as a storage within a VMware Hardware Plan wizard.

13.0.1.180

2025-11-19

Release Information:

13.0.0.4967

2025-09-03

Release Information:

Download Information

The installed build number can be found in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.

Patch for 13.1

This patch, available as an ISO or EXE file, is intended ONLY for patching existing Windows-based deployments of Veeam Backup & Replication 13.1 (build 13.1.0.411).

Note: Both the ISO and EXE contain the same patch. The EXE is smaller since it's a self-extracting archive and installer, but it needs more disk space and takes longer to start installing because it has to extract the patch files first. The ISO file is larger, but it can be mounted easily, allowing the patch installation to begin right away since all files are already inside the ISO and don't need to be extracted to a temporary folder.

If you use Veeam Backup Enterprise Manager, update that first, then update Veeam Backup & Replication.

Veeam Backup & Replication embedded installation on a Veeam Recovery Orchestrator server

Veeam Recovery Orchestrator 13.1 utilizes an embedded deployment of Veeam Backup & Replication 13.1.0.411.

Customers are encouraged to update the embedded Veeam Backup & Replication deployment using the patch available in this article.

This patch (ISO/EXE) can only be used to patch build 13.1.0.411. If an earlier version of Veeam Backup & Replication is installed, the installer will display the message:

This update is not compatible with installed product version.

Download Patch ISO

^{Filename: VeeamBackup&Replication_13.1.1.18_20260812_patch.iso}

Size: 2.92 GB

SHA256: D95A58B259FE746C079E72B3022684A40C707EBA8DF0FB594C79F0FABC1B4E38

After downloading the ISO, open the file's properties, select the Unblock option, and click OK. Alternatively, unblock the file using this command:

Unblock-File -Path "C:\Path\to\File\VeeamBackup&Replication_13.1.1.18_20260812_patch.iso"

Failure to unblock the ISO will cause the following warning to appear when attempting to start the patch install:

Unable to run the installer because files from this ISO are blocked for security reasons. Use the "Unblock" option in the file properties to proceed.

Download Patch EXE

^{Filename: VeeamBackup&Replication_13.1.1.18_20260812_patch.zip}

Size: 2.68 GB

SHA256: 73606B92D5160A291D4DA3F9FF45283CFE0BDBC6F8D56938409D864D0DFF929A

Deploying or Upgrading Veeam Backup & Replication on Windows

Use the following ISO for:

New deployments of Veeam Backup & Replication 13.1.1 on Windows machines.
Upgrading existing deployments of Veeam Backup & Replication 12.3.1, 12.3.2, or 13.0 to 13.1.1.

VSA Migration Version Limitation

Please note that deployment migration from Windows-based Veeam Backup & Replication to the new Linux-based Veeam Software Appliance is supported only for version 13.0.x builds.

Customers who plan to migrate deployments should remain on 13.0.2 or 13.0.3 until their migration is complete.

More Information: KB4800: Veeam Backup & Replication Platform Migration Guide (Windows to Linux)

Remember to always review the Upgrade Checklist as part of your upgrade process.

DOWNLOAD latest ISO

See the Current Versions Download Page for ISO hashes.

Note: KB4763: Veeam Backup & Replication 13 In-Place Upgrade Version Requirement

Reboot May Be Required

Please note that a reboot may be required after installing the update.

Please plan accordingly.

Updating Veeam Software Appliance

Upgrading the Veeam Software Appliance can be performed directly within the appliance itself.

Deploying Veeam Software Appliance

Use the following download (ISO, OVA, or VHDX) for:

New deployments of the Veeam Backup & Replication Veeam Software Appliance.

Note: Upgrading the Veeam Software Appliance can be performed directly within the appliance itself.

DOWNLOAD VSA

Addtional Downloads

ISO Release History

^{Previously released files are not publicly available for download. Mouse-over or tap the filenames in the table to view a file's checksum.}

Release Date	ISO Filename	Changelog
Veeam Backup & Replication 13.1.1.18 Releases
2026-09-01	VeeamBackup&Replication_13.1.1.18_20260812.iso^{SHA256: EF7D72458CD617C760D8FE84438CDAE9F1CF7B3CAEB14424446E918492A7384D}	ISO repack to include Veeam Plug-in for Google Cloud v8.
2026-08-27	VeeamSoftwareAppliance_13.1.1.18_20260825.iso^{SHA256: A9AF10FDCBA64EF7FF052AC388CE7AD191FFB73D071565E9AC077E0DB015A0A8}	ISO repack to address an issue preventing the installation ISO from being booted on a machine where the appliance is already deployed.
	VeeamInfrastructureAppliance_13.1.1.18_20260825.iso^{SHA256: 0C4F33B81574BE8CCCC7953ABA8D5DB5E719AE97C7F2A31A2827E86C3A9CF4C3}
2026-08-12	VeeamBackup&Replication_13.1.1.18_20260812.iso^{SHA256: 92A5260543E89E030312DAA571BEAE4CBDEB22895D384A6E6E72F151EE479B8D}	Initial Release
	VeeamSoftwareAppliance_13.1.1.18_20260811.iso^{SHA256: BF8F0393C451FFDF1F30376DA7151BA5A04C24DF8F4568C67D480302C06C2404}
	VeeamInfrastructureAppliance_13.1.1.18_20260811.iso^{SHA256: AD38C75451949E066B98CC1832A2D6D1EC399712956ECBD10DF092244A8D06FF}
Veeam Backup & Replication 13.1.0.411 Releases
2026-07-29	VeeamBackup&Replication_13.1.0.411_20260723.iso^{SHA256: 5781FDCAC228648E3F230EA2B43AD2FC3A145CC34086F56303B8A8B5B6A8AEE2}	Initial Release
	VeeamSoftwareAppliance_13.1.0.411_20260723.iso^{SHA256: 7F0218726496F223D1CF1E48BA188DE9F0E3F8198651D870603D693E44B66C2A}
	VeeamInfrastructureAppliance_13.1.0.411_20260723.iso^{SHA256: E2814BE69B8FBBCD3B1EA4168878A8C452296AF735FE1115F891C148DD14709E}
	VeeamLiveOS_13.1.0.68_20260703.iso^{SHA256: 6ADD1F29743B278E86D58CB18636020CEAC8FB0F78BD40C0D5EFA4AEE63E9C6B}
Veeam Backup & Replication 13.0.3.63 Releases
2026-09-02	VeeamSoftwareAppliance_13.0.3.63_20260828.iso^{SHA256: 582D71CC96F484106D2DB45B29AE85E457B6AA83C2A86D6002B9DE515ACE9F92}	ISO repack to address an issue preventing the installation ISO from being booted on a machine where the appliance is already deployed.
	VeeamInfrastructureAppliance_13.0.3.63_20260828.iso^{SHA256: 0C4F33B81574BE8CCCC7953ABA8D5DB5E719AE97C7F2A31A2827E86C3A9CF4C3}
2026-08-25	VeeamBackup&Replication_13.0.3.63_20260814.iso^{SHA256: F6C6AAE653EA427EB1A0EBAF5647A6B3D09CD00AE21A094E722426DD83A0BD39}	Initial Release
	VeeamSoftwareAppliance_13.0.3.63_20260814.iso^{SHA256: 8511BF75C81F5E6A5A90596C1053373064CA20A206EBF9B4D83EA4D5813153B9}
	VeeamInfrastructureAppliance_13.0.3.63_20260814.iso^{SHA256: 6938F0BE2BA5068F722409E05E4CAF4B225D2F4F4773B94FB7D7254F3A8928F8}
Veeam Backup & Replication 13.0.2.29 Releases
2026-06-23	VeeamSoftwareAppliance_13.0.2.29_20260617.iso^{MD5: 7C4C22EB66C0085B1B68B71FBC72AE49 SHA1: 347DBFAD7156B41524A797D5084473E5435FDE15}	ISO repack to include updated third-party components to address CVEs in those third-party componentsPython (CPython) CVE-2024-12718 CVE-2025-4138 CVE-2025-4330 CVE-2025-4435 CVE-2025-4517 CVE-2026-4519 CVE-2026-4786 CVE-2026-6100 cryptography CVE-2024-26130 urllib3 CVE-2025-66418 CVE-2025-66471 CVE-2026-21441 . Note: Existing deployments have already received these updates automatically from the update server. This repack ensures that new deployments include the updated components from initial installation.
	VeeamInfrastructureAppliance_13.0.2.29_20260618.iso^{MD5: AF189BBD4F824CF0877E0B61AC6A5572 SHA1: 6123E240AAAF32D9094B29913E4E9C0A1C40CC5A}
2026-05-27	VeeamBackup&Replication_13.0.2.29_20260522.iso^{MD5: 32ECCDBE8031364AC642E68A48E50D3C SHA1: E183A817DC4DD5367D79F7F9FAD8C35F913D0FC9}	Initial Release
	VeeamSoftwareAppliance_13.0.2.29_20260523.iso^{MD5: BEA609D5F770E99681C3CB5538E1B18B SHA1: 794515641B631D75EEDE95B6D566E8F068177EC0}
	VeeamInfrastructureAppliance_13.0.2.29_20260523.iso^{MD5: 495A771D7C28D84A466020E952C6BE5C SHA1: B8389C80211FE31368B5AB195DFB2452B557D36B}
Veeam Backup & Replication 13.0.1.2067 Releases
2026-03-12	VeeamBackup&Replication_13.0.1.2067_20260310.iso^{MD5: 9BE58C3B0D26A72175ABE9081A278F36 SHA1: 01F3F63D824EB880DFEEBB9810176D5D872251D1}	Initial Release
	VeeamSoftwareAppliance_13.0.1.2067_20260310.iso^{MD5: CABA0737F06021E57179DB195CA604E3 SHA1: 7A64B01E04D630FF8CCB63826481C64DF5C415BE}
	VeeamInfrastructureAppliance_13.0.1.2067_20260310.iso^{MD5: 277688B82DD16AE6863D9E28589B2551 SHA1: EFF6841F056E4C64C74C95A42C580C0CE84063AC}
Veeam Backup & Replication 13.0.1.1071 Releases
2026-01-06	VeeamBackup&Replication_13.0.1.1071_20251217.iso^{MD5: F293DBEEBE9D9B74DE6D71B028106BDD SHA1: 477F8CE1D872917555909747D59A139EDFC46458}	Initial Release
	VeeamSoftwareAppliance_13.0.1.1071_20251217.iso^{MD5: 89FB186D71EC09BFCC2CB11FD178CFB7 SHA1: 8C2482FFBF59A5875DFC443758FE75BFB5CDDA13}
	VeeamInfrastructureAppliance_13.0.1.1071_20251217.iso^{MD5: F70E3710988D03400AAA51B035E7D04E SHA1: B131F9F787B1262F039026323A59AA01CAE4CD36}
Veeam Backup & Replication 13.0.1.180 Releases
2025-12-1	VeeamBackup&Replication_13.0.1.180_20251130.iso^{MD5: 1F0E016486A33712F639FDE9745E8131 SHA1: 5F10F6D3E4DB5D6A2794675932C89D4544944E2C}	This repack modifies the installer only to address the top 2 issues affecting upgrades and deployments of 13.0.1. The installer's configuration check will now detect if an incompatible Backup service certificate is present, which could prevent interaction with hypervisor and cloud platform plugins, and direct the user to resolve the issue using KB4687. The installer will now allow more time for the RESTful API service to start, ensuring the installer procedure completes without requiring manual adjustment of the service timeout.
2025-11-19	VeeamBackup&Replication_13.0.1.180_20251114.iso^{MD5: 05CFBF8BAED838C07D6B3EB5320DA394 SHA1: 959D260A5EA1DD990168759014BAE18744A53870}	Initial Release
	VeeamSoftwareAppliance_13.0.1.180_20251101.iso^{MD5: 45C004D548AD5DFDBFC111D3A078F12A SHA1: 35DE828AB0A8715D2887A3BE3C2E92646375FE0B}
	VeeamInfrastructureAppliance_13.0.1.180_20251101.iso^{MD5: 26D4587FA6DBDE3BCBC8FFD9BB39CE74 SHA1: 80E2E3402785243C9DAA4B1D4A7E450E25E1F33E}
	VeeamLiveOS_13.0.1.51_20251023.iso^{MD5: 4942A657705C4B57E73A24845A65CC84 SHA1: 9D9DC45CE5A0A1492726620B2FCF642CC78B4386}
Veeam Backup & Replication 13.0.0.4967 Releases
2025-09-03	VeeamSoftwareAppliance_13.0.0.4967_20250822.iso^{MD5: 30BB0EEF0DCA6544C36A2728642D35C9 SHA1: 1AA8624419C71ADCF5425D87C8CF53F90FAFD1F6}	Initial Release
	VeeamJeOS_13.0.0.4967_20250822.iso^{MD5: DBEC5D16A81DC661CA286DA5B71F76BA SHA1: CF9FBF1D6685A3E44AD76FB6D969CCB81AA9C42C}
	VeeamLiveOS_13.0.0.39_20250702.iso^{MD5: A9D92382E2C5276D17F1161333F3D507 SHA1: 6D45A4C26055562DF87C0434859BEC918BCFC481}

Swipe to show more of the table

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

ReFS Known Issues, Considerations, and Limitations

2026-08-27T00:00:00Z

ReFS Known Issues, Considerations, and Limitations

KB ID:	2792
Product:	Veeam Backup & Replication Veeam Agent for Microsoft Windows
Published:	2018-11-06
Last Modified:	2026-08-27

Known Issues

Memory Management Issues

Server 2016 and older

Windows repositories using ReFS on Server 2016 (without the September 2018 updates) or older OS versions are known to have issues during backup job retention enforcement, which manifests as:

The repository server becomes unresponsive or crashes.
Significant reduction in I/O performance on the repository server.
High memory usage on the repository server.

These issues can lead to unexpected job termination.

As described in Microsoft article KB4016173, the root cause lies in the ReFS metadata management logic within the Windows OS system memory manager. This issue was resolved in Windows Server 2016 with updates from September 2018 (KB4343884 or later).

Server 2022 | Azure Stack HCI 21H2 | Azure Stack HCI 22H2

It is recommended to perform only 'clean installs,' as issues have been reported following in-place OS upgrades.

Server 2025 | Server 23H2 | Azure Stack HCI 23H2

There have been several reports of stability issues related to memory consumption with ReFS on Windows Server 2025, Server 23H2, Windows 11 23H2, and Azure Stack HCI 23H2. Microsoft provided fixes in December 2025 [December 9, 2025—KB5072033 (OS Build 26100.7462)].

BSOD after installing Cumulative Update

March Cumulative Update for Server 2025

The March 2025 cumulative updates for Windows Server 2025, 23H2, 2022, and 2019 have a known regression that may lead to a Blue Screen of Death (BSOD) with a bug check of 0x00000149. This issue was later resolved with Microsoft's release of the April 2025 Cumulative Update.

ReFS Version Compatibility Challenges Across OS Versions

Each version of Windows has specific versions of ReFS that it is compatible with. This can lead to complications when performing certain actions within Veeam Backup & Replication.

Guest OS File Level Restore (FLR)
- If the OS of the Mount Server is older than the original Guest OS, the FLR File Browser may not display the content of ReFS volumes.
- If the OS of the Mount Server is newer than the original Guest OS, there may be a delay during file restores because the Mount Server's OS is trying to update the ReFS version of the mounted volume. To mitigate this delay, create the following registry value on the Mount Server to prevent the OS from attempting to upgrade the ReFS filesystem version of mounted volumes:
  
  Key Location: HKLM\System\CurrentControlSet\Control\FileSystem
  Value Name: RefsDisableVolumeUpgrade
  Value Type: DWORD (32-Bit) Value
  Value Data: 1
  
  Set using PowerShell:

New-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\FileSystem\' -Name 'RefsDisableVolumeUpgrade' -Value "1" -PropertyType DWORD -Force
                     
                    

Windows Repository Server Upgrades
There have been instances where customers reported data loss after performing an in-place OS upgrade on a Windows Server hosting an ReFS volume that acts as a Windows Repository. The issue arises when the OS attempts to upgrade the ReFS version of the volume and the process fails. For this reason, Veeam strongly advises against performing in-place OS upgrades for ReFS-based Windows Repositories.
Failover with Re-IP of Replica with ReFS Volume
During the Re-IP procedure, all disks of the replica are mounted to the Veeam Backup Server so the software can update the static IP. If the replica's Guest OS is older than the Veeam Backup Server and the replica has an ReFS volume, the Veeam Backup Server's OS will automatically update the ReFS volume version. As a result, the ReFS volume will become unreadable by the replica's Guest OS because the new ReFS version exceeds the compatibility of the Guest OS.
Note: Veeam's RND team has been made aware of this, and in a future release of Veeam Backup & Replication, the software will detect and block the mounting of ReFS volumes during the Re-IP procedure.

Considerations and Limitations

Configuration Related

Do not use ReFS with iSCSI or FC SANs unless explicitly supported by the hardware vendor.
ReFS supported configurations must use Windows Server Catalog certified hardware.
ReFS does not support SAN storage features such as thin provisioning, TRIM/UNMAP, and ODX.
Do not use deduplication in combination with ReFS block cloning.
Ensure scheduled Data Integrity Scans do not overlap with your backup window.
ReFS relies on flush durability, meaning that if filesystem metadata write operations occur, they must be consistently flushed to disk. If a storage destination is used where a cache acknowledges writes before they are written to disk, for example, by a RAID controller or NAS, and those metadata writes then do not make it to disk due to a power failure, the filesystem may become corrupted.
There were several Windows Updates• Server 2012 R2 - KB5009624
• Server 2019 - KB5009557
• Server 2022 - KB5009555 that broke ReFS functionality with removable media. Microsoft does not support ReFS on removable media. However, Microsoft has released out-of-band updates to restore functionality, but only for ReFS v2 and higher. For more information, review: Veeam Community Discussion: ReFS issues with latest Windows Server Updates

OS Notes

While Microsoft does support booting from ReFS volumes under particular circumstances involving Azure confidential VMs, this configuration is not supported by Veeam Agent for Microsoft Windows. Although it is technically possible to configure Windows to boot from an ReFS volume, doing so may lead to stability issues with Veeam Agent for Microsoft Windows. For example, attempting to back up an ReFS boot volume using Veeam Agent for Microsoft Windows has a high probability of causing a BSOD.
Veeam always recommends keeping all systems fully patched with the latest Windows Updates for best performance and security.
Since Veeam Backup & Replication 10a, the RefsEnableLargeWorkingSetTrim registry value is automatically set, based on Microsoft's recommendation, upon the creation of a Windows-based backup repository. (After adding the repository, a reboot is required for the OS to activate the registry value.)

Hardware

The backup repository server must meet minimum system requirements.
For environments where a single server handles multiple roles (aka All-in-One Installation), ensure that the server has enough RAM based on the combined requirements of all roles assigned to it.

3rd Party Software

Uninstall the following 3rd party software, as these have been reported to cause ReFS instability and/or performance issues:

Antivirus software (except Windows Defender)
Microsoft Configuration Manager Client

Note: To ensure no conflicting software is present, we recommend deploying Windows OS using the original ISO file from Microsoft (instead of using an image provided by the server vendor, which may include bloatware).

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Release Information for NetApp ONTAP Plug-In for Veeam Backup & Replication

2026-08-25T00:00:00Z

Release Information for NetApp ONTAP Plug-In for Veeam Backup & Replication

KB ID:	4904
Product:	Veeam Backup & Replication \| 13.1
Published:	2026-08-25
Last Modified:	2026-08-28

This plug-in leverages the Veeam Universal Storage API, which enables storage OEMs to allow Veeam Backup & Replication integration to the arrays for backup and replication jobs.

Requirements

Before installing NetApp ONTAP Plug-In v2.0.14, ensure that you are running at least Veeam Backup & Replication version 13.1.0.411. You can check the build number in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.

NetApp ONTAP Plug-In v2.0.14 supports integration with the following storage systems:

NetApp FAS/AFF/ASA/ASA r2 (ONTAP 9.10.1 or later)

Coexistence with Built-In NetApp ONTAP Integration

Veeam Backup & Replication has provided built-in NetApp ONTAP storage snapshot integration for years. To avoid conflicts between the built-in integration and the new NetApp ONTAP plug-in (USAPI integration), consider the following:

Using the same cluster or SVM with the same storage role simultaneously for both built-in integration and USAPI integration is not allowed. To migrate a specific cluster or SVM from built-in integration, you must first remove it from Veeam Backup & Replication and then re-add it using the NetApp ONTAP plug-in. This means creating new jobs; existing snapshots will not be subject to retention by the new jobs, so snapshot retention information for that storage will be lost.
Using the same cluster simultaneously in both built-in and USAPI integration is allowed, provided each integration uses a different storage role. For example, MyCluster1 can be added with the NAS role in built-in integration and with the VMware role in USAPI integration.
Replication technologies are not supported between systems added through different integration types. All clusters participating in a replication relationship must be added through the same integration type, either built-in or USAPI.

Known Issues

The following are known issues and limitations for the NetApp ONTAP Plug-In for Veeam Backup & Replication.

General

This plug-in does not support NAS integration (unstructured data backup). For this, you need to use Veeam built-in integration.
Before adding the storage system to the backup infrastructure, make sure a valid FlexClone license is installed on the NetApp storage system. Otherwise, backup and restore tasks will fail.

Replication Support and Scope

Veeam Backup & Replication does not support backup from storage snapshots or snapshot orchestration on the secondary storage array for the replication features listed below. However, you can still use volumes with these features configured as sources for backup from storage snapshots or snapshot-only jobs on the primary storage array.
- MetroCluster
- SVM-DR
- SnapMirror Active Sync (formerly SnapMirror Business Continuity)
If individual SVMs (rather than entire clusters) are added to Veeam Backup & Replication, cross-cluster SnapMirror relationships are not supported for them, since the information required to build such relationships cannot be collected from within a single SVM's context.
If both the source and target SVMs of a cross-cluster SnapMirror Active Sync relationship are added to Veeam Backup & Replication individually, backup jobs may fail due to a conflict between identical volume SCSI IDs.

MetroCluster

In a MetroCluster configuration where entire clusters are added to Veeam Backup & Replication, snapshots created before a switchback are no longer covered by retention management after the switchover and switchback, and such snapshots must be deleted manually. This does not apply when Veeam Backup & Replication works with individual SVMs; retention continues to work correctly with no additional action required.
In a MetroCluster configuration where entire clusters are added to Veeam Backup & Replication, a switchover requires a rescan (storage discovery) of the active node to update information about active volumes. This is not required when Veeam Backup & Replication works with individual SVMs.

SnapMirror Synchronous

SnapMirror Synchronous support requires ONTAP 9.14.1 or later.
If a volume participating in SnapMirror Synchronous replication is used only for source-side backups (without snapshot orchestration), VeeamAUX snapshots are synchronized to the target automatically via SM-S technology but are not removed from the target when the backup job completes. These snapshots are deleted from the target automatically every 6 hours, per the default Sync policy.

SnapMirror Asynchronous

If a SnapMirror relationship uses the async-mirror policy type with all snapshots mirrored, retention settings specified in Veeam Backup & Replication for target snapshots are ignored, and only the source snapshot retention settings are applied. If snapshot orchestration is not configured on the source, target retention defaults to 1.
For volumes participating in a SnapMirror Asynchronous relationship, the immutability period of target snapshots cannot be shorter than that of the source snapshots, including zero. If a job is configured otherwise, the target immutability period is automatically adjusted to match the source.
Backing up from a SnapMirror Asynchronous target on ASA r2 is not supported if SnapLock is enabled on the target volume.
Storage Efficiency (deduplication) is supported for target volumes. However, depending on storage load and replication activity, ONTAP may take a variable amount of time to automatically start the snapshot deduplication process after a transfer completes. Deduplication changes the snapshot ID, so the plug-in waits before checking for the updated ID; this wait time is controlled by the postTransferDwellTimeSeconds setting (60 seconds by default) and can be adjusted if needed.

Consistency Group Replication (ASA r2)

Consistency Group-level replication is supported for ASA r2 only. For all other storage families, replication support is limited to the volume level.
Since SnapMirror replication for ASA r2 is performed at the Consistency Group (CG) level, target-side snapshot orchestration and retention apply to the entire CG snapshot as a single unit rather than per volume. If volumes within the same CG are protected by jobs with different retention settings, the effective retention for every volume in the group is capped to the shortest retention configured among those jobs, meaning that snapshots for volumes with a longer configured retention may be removed earlier than expected once a job with shorter retention performs cleanup. Source-side snapshots (both backup and orchestration) are unaffected and continue to be managed per volume as usual.

Tamperproof Snapshots

Tamperproof Snapshots are not supported on ASA r2.
Tamperproof Snapshots are supported only when the entire cluster is added to Veeam Backup & Replication; individual SVMs are not supported.
Tamperproof Snapshots support requires ONTAP 9.12.1 or later (9.19.1 or later for SnapMirror Synchronous) and a SnapLock license.

NFS

Restoring NFSv3 volumes is not supported on some ONTAP versions when a Load-Sharing Mirror for root volumes (root ls mirror) is configured. For details, see NetApp KB CONTAP-95735.
During NFS volume backup, the plug-in uses temporary export policies for auxiliary clones. For proxies and hosts to access these temporary NFS shares, the corresponding export permissions must also be granted on the root NFS share of the SVM. For security reasons, the plug-in does not add these rules to the root volume export policy automatically, so you must configure them manually. To let the plug-in create these rules automatically instead, set autoCreateRootVolumeExportRules = true in the configuration file.

Configuration File Parameters

For more precise customization of the plug-in's behavior, you can use a configuration file located in the following folder:

For Veeam Backup & Replication on Veeam Software Appliance (see Installing and Updating Plug-Ins on Linux-Based Backup Server):
/etc/veeam/plugins/storages/netapp-ontap/storage_plugin_advanced_settings.json
For Veeam Backup & Replication on Windows (see Installing Plug-Ins on Microsoft Windows-Based Backup Server):
C:\ProgramData\Veeam\Storage\NetApp ONTAP\storage_plugin_advanced_settings.json

It is not necessary to specify all the options. Only those that need to be changed are sufficient. The rest will use the default values. Some options must be specified at the storage level. The name of the cluster or SVM added to Veeam Backup & Replication is used as the identifier.

Example file structure (with default values):

{
  "minimumontapversion": "9.10.0",
  "httpclienttimeoutseconds": 1800,
  "storages": [
    {
      "name": "your-cluster-name",
      "autoCreateRootVolumeExportRules": false,
      "efficiency": {
        "postTransferDwellTimeSeconds": 60,
        "maxPostTransferMonitoringMinutes": 240
      }
    }
  ]
}

Download Information

For Veeam Backup & Replication on Windows

Download NetApp ONTAP Plug-In

^{Release date: 2026-08-25}

SHA256: 80108500AF3B6F277ACC6FBA9AD8C8EDD3E32220BB956CFE89208C38F4652FAE

For Veeam Backup & Replication on Veeam Software Appliance

Download NetApp ONTAP Plug-In

^{Release date: 2026-08-25}

SHA256: E166F83F1FC0099D43FC36A62A6AE3429C0224A1E70EEBFF380A54920C8B9329

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Vulnerability Resolved in Veeam Backup & Replication 13.1

2026-08-25T00:00:00Z

Vulnerability Resolved in Veeam Backup & Replication 13.1

KB ID:	4902
Product:	Veeam Backup & Replication \| 13
Published:	2026-08-25
Last Modified:	2026-08-25

Veeam Software Security Commitment

Veeam® is committed to ensuring its products protect customers from potential risks. As part of that commitment, we operate a Vulnerability Disclosure Program (VDP) for all Veeam products and perform extensive internal code audits. When a vulnerability is identified, our team promptly develops a patch to address and mitigate the risk. In line with our dedication to transparency, we publicly disclose the vulnerability and provide detailed mitigation information. This approach ensures that all potentially affected customers can quickly implement the necessary measures to safeguard their systems. It’s important to note that once a vulnerability and its associated patch are disclosed, attackers will likely attempt to reverse-engineer the patch to exploit unpatched deployments of Veeam software. This reality underscores the critical importance of ensuring that all customers use the latest versions of our software and install all updates and patches without delay.

Issue Details

CVE-2026-58070

A vulnerability that causes guest OS credentials used for Application Aware processing to be recorded in cleartext in logs on the guest machine.

Severity: Medium
CVSS v4.0 Score: 6.8CVSS: AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Affected Deployment Type: Windows-based Veeam Backup & Replication | Veeam Software Appliance
Source: Reported through HackerOne.

Affected Product

Veeam Backup & Replication 13.0.2.29 and all earlier version 13 builds.
_{Note: Older versions (e.g., 12.x) are not affected.}

Solution

This vulnerability was fixed starting in the following builds:

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Vulnerability Resolved in Veeam ONE 13.1 Patch 0

2026-08-25T00:00:00Z

Vulnerability Resolved in Veeam ONE 13.1 Patch 0

KB ID:	4905
Product:	Veeam ONE \| 13
Published:	2026-08-25
Last Modified:	2026-08-24

Veeam Software Security Commitment

Issue Details

CVE-2026-65641

A vulnerability allowing an unauthenticated network attacker to coerce SMB authentication from the service account.

Severity: Critical
CVSS v4.0 Score: 9.3CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:L
Source: Reported through HackerOne.

Affected Product

Veeam ONE 13.1.0.7034 and all earlier version 13 builds.
_{Note: Older versions (e.g., 12.x) are not affected.}

Solution

This vulnerability was fixed starting in the following builds:

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Vulnerabilities Resolved in Veeam ONE 13.1

2026-08-25T00:00:00Z

Vulnerabilities Resolved in Veeam ONE 13.1

KB ID:	4892
Product:	Veeam ONE \| 12 \| 12.1 \| 12.2 \| 12.3 \| 13
Published:	2026-08-04
Last Modified:	2026-08-25

Veeam Software Security Commitment

Issue Details

CVE-2026-64633

A vulnerability allowing remote unauthenticated code execution on the agent host.

Severity: Critical
CVSS v4.0 Score: 10.0CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Source: Reported through HackerOne.

Affected Product

Veeam ONE 13.0.2.6723 and all earlier version 13 builds.
Note: Older versions (e.g., 12.x) are not affected.

Solution

This vulnerability was fixed starting in the following builds:

CVE-2026-58075

A vulnerability allowing an unauthenticated attacker to read arbitrary files from the host, which can be further leveraged to escalate privileges locally.

Severity: High
CVSS v4.0 Score: 8.7CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Source: Reported through HackerOne.

Affected Product

Veeam ONE 13.0.2.6723 and all earlier version 13 builds.
_{Note: Older versions (e.g., 12.x) are not affected.}

Solution

This vulnerability was fixed starting in the following builds:

CVE-2026-58074

A vulnerability allowing a high-privileged user to execute arbitrary code on the server.

Severity: High
CVSS v4.0 Score: 8.6CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Source: Discovered during internal testing.

Affected Product

Veeam ONE 13.0.2.6723 and all earlier version 13 builds.
Veeam ONE 12.3.0.4670 and all earlier version 12 builds.
_{Note: Unsupported product versions are not tested, but are likely affected and should be considered vulnerable.}

Solution

This vulnerability was fixed starting in the following builds:

CVE-2026-64631

A vulnerability allowing a low-privileged user to inject SQL and extract database contents.

Severity: High
CVSS v4.0 Score: 8.6CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/SI:H/SA:H
Source: Reported through HackerOne.

Affected Product

Veeam ONE 13.0.2.6723 and all earlier version 13 builds.
Veeam ONE 12.3.0.4670 and all earlier version 12 builds.
_{Note: Unsupported product versions are not tested, but are likely affected and should be considered vulnerable.}

Solution

This vulnerability was fixed starting in the following builds:

CVE-2026-64632

A vulnerability allowing a low-privileged user to capture the NTLM credentials of the Reporter service account.

Severity: High
CVSS v4.0 Score: 8.5CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H
Source: Reported through HackerOne.

Affected Product

Veeam ONE 13.0.2.6723 and all earlier version 13 builds.
Veeam ONE 12.3.0.4670 and all earlier version 12 builds.
_{Note: Unsupported product versions are not tested, but are likely affected and should be considered vulnerable.}

Solution

This vulnerability was fixed starting in the following builds:

CVE-2026-64634

A vulnerability allowing local privilege escalation to the Reporter service context.

Severity: High
CVSS v4.0 Score: 8.4CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Source: Reported through HackerOne.

Affected Product

Veeam ONE 13.0.2.6723 and all earlier version 13 builds.
_{Note: Older versions (e.g., 12.x) are not affected.}

Solution

This vulnerability was fixed starting in the following builds:

CVE-2026-64630

A vulnerability allowing a low-privileged user to retrieve report data outside the scope of a shared report link.

Severity: Medium
CVSS v4.0 Score: 5.3CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N
Source: Reported through HackerOne.

Affected Product

Veeam ONE 13.0.2.6723 and all earlier version 13 builds.
_{Note: Older versions (e.g., 12.x) are not affected.}

Solution

This vulnerability was fixed starting in the following builds:

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

List of Security Fixes and Improvements in Veeam ONE

2026-08-25T00:00:00Z

List of Security Fixes and Improvements in Veeam ONE

KB ID:	4858
Product:	Veeam ONE
Published:	2026-05-27
Last Modified:	2026-08-21

Purpose

This article describes all security-related fixes and improvements introduced in each release or update of Veeam ONE.

This article aims to provide our customers' security and compliance teams with detailed information on security improvements between releases to help them make an informed decision on whether it is critical to upgrade from their current Veeam ONE version to a later one.

Security Fixes and Improvements

13.1.0.7233

CVE-2026-65641 vulnerability was fixed.

13.1.0.7034

CVE-2026-64633 vulnerability was fixed.
CVE-2026-58075 vulnerability was fixed.
CVE-2026-58074 vulnerability was fixed.
CVE-2026-64631 vulnerability was fixed.
CVE-2026-64632 vulnerability was fixed.
CVE-2026-64634 vulnerability was fixed.
CVE-2026-64630 vulnerability was fixed.
AutoMapper was replaced with MagicMapper 14.0.1.
Azure.Identity upgraded to version 1.17.2
@babel/runtime upgraded to version 7.29.2
dompurify upgraded to version 3.4.11
ip-address upgraded to version 10.1.1
Microsoft.IdentityModel.JsonWebTokens upgraded to version 8.17.0
System.IdentityModel.Tokens.Jwt upgraded to version 8.17.0
System.Private.Uri upgraded to version 4.3.2
System.Security.Cryptography.Xml upgraded to version 10.0.7
vite upgraded to version 8.0.16

13.0.2.7159

CVE-2026-64633 vulnerability was fixed.
CVE-2026-58075 vulnerability was fixed.
CVE-2026-58074 vulnerability was fixed.
CVE-2026-64631 vulnerability was fixed.
CVE-2026-64632 vulnerability was fixed.
CVE-2026-64634 vulnerability was fixed.
CVE-2026-64630 vulnerability was fixed.
CVE-2026-65641 vulnerability was fixed.
d3-color upgraded to version 3.1.0
dompurify upgraded to version 3.4.11
OpenSSL upgraded to version 3.0.21
SQLite (SQLitePCLRaw e_sqlite3) upgraded to version 3.0.3

13.0.2.6723

AutoMapper was replaced with MagicMapper 14.0.1.
dompurify upgraded to version 3.4.2
postcss upgraded to version 8.5.13
System.Security.Cryptography.Xml upgraded to version 8.0.3
uuid upgraded to version 14.0.0
vite upgraded to version 4.5.14

12.3.0.7165

CVE-2026-64631 vulnerability was fixed.
CVE-2026-64632 vulnerability was fixed.
CVE-2026-58074 vulnerability was fixed.

More Information

As we're establishing this new process, we appreciate any feedback on the content or format of this KB article. Please let us know in the corresponding topic on the Veeam Community Forums. If your feedback is too sensitive to be shared publicly, please submit it by opening a support case. We highly appreciate your collaboration!

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Release Information for Veeam ONE 13 and Updates

2026-08-25T00:00:00Z

Release Information for Veeam ONE 13 and Updates

KB ID:	4762
Product:	Veeam ONE \| 13 \| 13.1
Published:	2025-09-03
Last Modified:	2026-08-26

Veeam ONE 13 Releases

13.1.0.7233

2026-08-25

Required Before Upgrading a Monitored Veeam Backup & Replication Server to 13.0.3

Before a monitored Veeam Backup & Replication server is upgraded to version 13.0.3, Veeam ONE 13.1 must be updated to Patch 0 (build 13.1.0.7233). On Veeam ONE 13.1 (build 13.1.0.7034), the backup server version is detected as 13.0 and data collection fails with a timeout.

What's New

Veeam ONE 13.1 Patch 0 is a cumulative patch for Veeam ONE 13.1. It adds support for monitoring Veeam Backup & Replication 13.0.3, resolves a security vulnerability, and fixes several data collection, performance, alarm, and upgrade issues. Applying this patch is recommended for all Veeam ONE 13.1 deployments, and it is required to monitor Veeam Backup & Replication 13.0.3 servers.

Resolved Issues

Security

CVE-2026-65641 | Severity: Critical (9.3)
A vulnerability allowing an unauthenticated network attacker to coerce SMB authentication from the service account.

Data Collection and Infrastructure Monitoring

Data collection from Veeam Backup & Replication 13.0.3 servers fails with a timeout, so the server is shown as Unhealthy and is excluded from the scope of reports and dashboards.
The Veeam ONE Data Collection Service restarts periodically and crashes with exception 0xC0000005 while checking endpoint availability. Endpoints that refuse the connection can also be reported as available.
Veeam ONE Agent data collection stops after a database is locked error on the local collector database and does not recover until the service is restarted.

Scalability and Performance

The Veeam ONE Caching Service may fail with a timeout when retrieving the data collection readiness status of Veeam Backup & Replication servers.
Generating the Job History report locks job session data in the database, which delays data collection and other reports in large environments.
The Backup Billing report keeps SQL Server CPU utilization at 100% in environments with a large number of restore points.

Alarms

A deadlock in the Veeam ONE Data Collection Service causes the client request queue to overflow, so alarms ignore changes to the Acknowledged, Resolved, and Disabled states.

Installation and Upgrade

If Veeam ONE was installed to a non-default folder, Report Booster does not work after a chain upgrade from 12.x to 13.0.x to 13.1 and fails with the error:
```
No connection could be made because the target machine actively refused it
```

Download Information

13.1.0.7034

2026-07-29

13.0.2.7159

2026-08-25

Required Before Upgrading a Monitored Veeam Backup & Replication Server to 13.0.3

Before a monitored Veeam Backup & Replication server is upgraded to version 13.0.3, Veeam ONE must be updated to build 13.0.2.7159 or to Veeam ONE 13.1 Patch 0 (build 13.1.0.7233). On earlier version 13 builds, including Veeam ONE 13.1 (build 13.1.0.7034), the backup server version is detected as 13.0 and data collection fails with a timeout.

What's New

Veeam ONE 13.0.2 Patch 1 is a cumulative maintenance and security update for Veeam ONE 13.0.2. It resolves reported issues across reporting and data collection, and addresses several security vulnerabilities, including externally reported CVEs. Applying this patch is recommended for all Veeam ONE 13.0.2 deployments that are not ready to upgrade to 13.1.

Updated Runtime Prerequisites

This patch updates the bundled .NET Runtime to 8.0.29, delivering the latest security patches for the Veeam ONE server infrastructure.

Updated Third-Party Components

The following third-party components included with Veeam ONE were upgraded with this patch to address vulnerabilities reported within them.

Microsoft .NET Runtime (8.0.29)
System.Security.Cryptography.Xml
DOMPurify
ws
flatted
d3-color

Resolved Issues

Security

CVE-2026-64633 | Severity: Critical (10.0)
A vulnerability allowing remote unauthenticated code execution on the agent host.
CVE-2026-58075 | Severity: High (8.7)
A vulnerability allowing an unauthenticated attacker to read arbitrary files from the host, which can be further leveraged to escalate privileges locally.
CVE-2026-58074 | Severity: High (8.6)
A vulnerability allowing a high-privileged user to execute arbitrary code on the server.
CVE-2026-64631 | Severity: High (8.6)
A vulnerability allowing a low-privileged user to inject SQL and extract database contents.
CVE-2026-64632 | Severity: High (8.5)
A vulnerability allowing a low-privileged user to capture the NTLM credentials of the Reporter service account.
CVE-2026-64634 | Severity: High (8.4)
A vulnerability allowing local privilege escalation to the Reporter service context.
CVE-2026-64630 | Severity: Medium (5.3)
A vulnerability allowing a low-privileged user to retrieve report data outside the scope of a shared report link.
CVE-2026-65641 | Severity: Critical (9.3)
A vulnerability allowing an unauthenticated network attacker to coerce SMB authentication from the service account.

Reporting

The Protected VMs report shows virtual machines that are protected by both a backup job and a backup copy job as unprotected by backup copy.
The Protected VMs report lists Proxmox VE cluster nodes as unprotected virtual machines.
The Protected Computers report shows computers as unprotected even though valid restore points exist for them.
The Job History report does not display source items for unstructured data backups when the protected file share is a root shared folder.
The Job History report does not display all job sessions: when the initial session starts before the beginning of the reporting period, only retry sessions are shown.
The Backup Billing report does not return data for some jobs whose sessions are older than a certain date.
The Backup Billing report returns incomplete or incorrect repository usage data in large environments where the transfer of report data is interrupted.
Kasten policy jobs appear in the Latest Job Status report and cannot be excluded from the report scope.
The Veeam ONE Reporting service crashes repeatedly, which makes the Veeam ONE Web Client inaccessible and prevents reports from running.

Data Collection and Infrastructure Monitoring

The VeeamDCS service crashes intermittently during performance data collection, and also when the AlmExcludedIps parameter is left empty.
The Veeam ONE agent data collection service stops collecting data permanently after a database is locked error on the local collector database, and does not recover until the service is restarted.
The VeeamDCS log file grows without limit when log rotation fails because the file is locked by another process.
Data collection from Veeam Backup & Replication 13.0.3 servers fails with a timeout because the backup server version is detected as 13.0.

Veeam ONE Web Client

The RPO Anomalies dashboard includes deleted virtual machines that have no restore points and no active jobs.

Download Information

Veeam ONE 13.0.2 Patch 1 is distributed as a ZIP archive containing five .msp patch installers, which update an existing 13.0.2 deployment in place. A full ISO image of build 13.0.2.7159 is also available for deployments installed from updated media rather than patched.

Prerequisites and Recommendations

Ensure Veeam ONE 13.0.2 (build 13.0.2.6723) is installed.
Perform a full backup of the Veeam ONE database.
If the Veeam ONE server is virtual, create a VM snapshot or another rollback point.
Close all Veeam ONE Monitor Client sessions. Use Task Manager to verify that no Veeam ONE or Veeam ONE Monitor client processes are running.
Run the update with local administrator privileges.
Allow the .msp installers to stop and start Veeam ONE services during patching.

Updating

Copy the .zip to the Veeam ONE server and extract it to a local folder, for example C:\Temp\VONE1302_P1.
Verify that the five .msp files listed below are present.
Close any running Veeam ONE Monitor Client instances.
Execute all five .msp files. They can be applied in any order.
1. Right-click each .msp file and select Install.
2. Follow the on-screen prompts.
  Services will be stopped and started automatically.

Download 13.0.2 Patch 1

^{Filename: VeeamONEv13.0.2_Patch1.zip}

Size: 330 MB
SHA256: 5414FA5DAA0D45C50F650871C43965843068F46DF1D3BE53AF72B15E1EE3BABF

Contents:

VeeamONE.Agent.x64.msp
VeeamONE.Caching.Service.x64_13.02.7159.msp
VeeamONE.Monitor.Client.x64_13.0.2.7159.msp
VeeamONE.Monitor.Server.x64_13.0.2.7159.msp
VeeamONE.Reporter.Server.x64_13.0.2.7159.msp

Deploying from Updated Media

The following ISO can be used to install Veeam ONE 13.0.2.7159.

Download 13.0.2.7159 ISO

^{Filename: VeeamONE_13.0.2.7159_20260817.iso}

Size: 3.29 GB
SHA256: 1DD00FC9CDF2DDE30183036D6121803B0B6836529A4CB256BB4A329777BB0151

13.0.2.6723

2026-05-27

What's New

New Features and Improvements

Suspicious Incremental Backup Size Alarm — Extended Platform Support
The Suspicious Incremental Backup Size alarm now covers all platforms supported in Veeam ONE v13, including Proxmox VE, oVirt KVM (Oracle Linux KVM and Red Hat Virtualization), and Scale Computing. Administrators monitoring mixed-platform environments will receive consistent anomaly detection across all backup job types without additional configuration.

Updated Runtime and Database Prerequisites
This release ships with updated foundational components on the installation media: .NET Runtime 8.0.27 and PostgreSQL 17.10. These updates deliver the latest security patches and stability improvements for the Veeam ONE server infrastructure.

Updated Third-Party Components

The following third-party components included with Veeam ONE were upgraded with this release to address vulnerabilities reported within them.

Microsoft.NET Runtime (8.0.27)
PostgreSQL (17.10)
Visual C++ Redistributable (vc_redist) (14.50.35719)
AutoMapper
System.Security.Cryptography.Xml
Vite
DOMPurify
PostCSS
uuid
d3plus-viz
d3plus-shape
xmldom

Resolved Issues

Alarms

The root-node alarm indicator (red dot) remains visible in the infrastructure tree after all child-object alarms have been resolved.
The Suspicious Incremental Backup Size alarm triggers incorrectly under certain conditions, generating false-positive notifications.
The Plug-in Backup Data Collection Failure alarm produces frequent false triggers, causing unnecessary alert noise.
The Maximum Allowed Job Duration alarm generates false-positive notifications for jobs that complete within their configured thresholds.
Alarms resolved via ServiceNow integration are matched against incorrect incident statuses, potentially leaving incidents in a stale state.

Data Collection and Infrastructure Monitoring

Veeam Backup & Replication v12 servers display an "Unhealthy" state after upgrading Veeam ONE.
A Veeam Backup Server originally monitored as a stand-alone node via FQDN shows an "Unhealthy" state after being joined to an HA cluster.
A Veeam Backup Server previously monitored in Veeam ONE shows an "Unhealthy" state after it is promoted to the primary node of an HA cluster.
SOBR capacity-tier repositories backed by S3-compatible object storage are incorrectly displayed as "Inaccessible" in Veeam ONE.
Objects managed by Veeam Backup & Replication become inaccessible after a server reboot, requiring manual intervention to restore monitoring.
A broken connection to one Veeam Backup Server can disrupt data collection from other monitored Veeam Backup Servers in distributed deployments.
Business View groups created using vSphere custom attributes appear empty when no categorization groups based on vSphere tags are defined.

Scalability and Performance

The ReFS backup repository monitoring functionality causes high CPU utilization on the database server in large environments.
The default value of the PipeMaxQueueSize parameter is now 1000, improving data-pipeline throughput and reducing processing bottlenecks in large-scale deployments.
The SQL Server tempdb database grows excessively during normal Veeam ONE operations.
The VeeamDCS service becomes unresponsive under heavy load due to a deadlock condition (circular wait).
The Web UI becomes unresponsive due to a deadlock in the Settings.Native component.
Generating a large number of reports in parallel causes the Reporter service to hang, requiring a service restart.

Reporting

The Backup Inventory report fails to generate, returning an error:
```
Failed to cache data for reporting.
```
The Recovery Verification Overview report generates without data for Windows-based Veeam Backup & Replication v13.0.1 servers.
SureReplica jobs from Veeam Software Appliance (Linux-based Veeam Backup & Replication) v13 servers are missing from the Recovery Verification Overview report.
The Restore Operator Activity report is missing the "Restored Object" column, preventing administrators from identifying which objects were restored.
The License report displays incorrect data when there is no license consumption during the previous month.
Scheduled report script generation fails when running under a local account, even though the scheduling status shows "Success."

Installation and Upgrade

Setup fails with an error requiring .NET 10 instead of the expected .NET 8, blocking fresh installations.
Upgrading to v13.0.1 fails when previously saved report parameters contain legacy JSON, producing the error:
```
Failed to install ReportPack VRReportPackCustomReports.pkg.
```
Upgrading to v13 fails when certain property values in the BpJobDump_Parsed table exceed the column size limit, producing the error:
```
String or binary data would be truncated
```
The Analytics Service installer incorrectly blocks installation on Windows Server 2012 R2.
Veeam ONE setup cannot proceed with a remote PostgreSQL server when the service account is placed in the "Deny log on locally" group.
After upgrading, all remote monitoring agents on Windows-based Veeam Backup Servers remain stuck in the "Updating" state.

13.0.1.6168

2026-01-06

What's New

Veeam Backup & Replication Authentication Anomalies
Veeam ONE v13.0.1 Patch 1 introduces first-class visibility and control over sign-in activity in Veeam Backup & Replication by capturing both successful and failed logins, surfacing trends and spikes that may slip past routine checks, and converting them into actionable insights with alarms and reports ready for audits and regulatory reviews. You can route these alerts to ServiceNow, SNMP, Syslog, email, or custom scripts to fit your existing workflows. Correlation with other backup events helps identify risky patterns, such as repeated failures followed by privilege changes or suspicious job launches. This improves your security posture, reduces the chance of undetected malicious access, and shortens investigation time by giving operators a single place to review who accessed what, when, whether access succeeded, and how the system responded.
VM Daily Protection Status - Enhanced View
This enhancement restores the familiar date-as-columns view in the Job Status report, allowing customers to scan a week’s outcomes per VM or job in one pass and instantly spot streaks, gaps, or regressions. It fits daily standups and SLA checks, where you need a quick, heat-map style read of Success, Warning, or Failed statuses across days without paging through rows. The layout reduces cognitive load for large estates, aligns with existing operational workflows, and mirrors exactly in CSV, Excel, and PDF exports. A simple toggle lets you choose between the classic columns view and the newer rows view to match each use case.
Report Builder: Table of Contents for New Reporting Engine
This enhancement restores the optional Table of Contents for PDF reports generated with Report Builder in the new Reporting Engine, providing quick navigation through long documents, clearer structure for audits, and a familiar layout used since v12.3. The TOC is user-controlled via the existing checkbox, allowing teams to include it for executive or compliance packs or omit it for lightweight briefs. The setting is preserved in templates for consistent output across scheduled and ad hoc exports.
Enhanced Reports Exported to CSV for New Reporting Engine
CSV export in the new Reporting Engine now mirrors what enterprises relied on in SSRS by bundling extra datasets inside the export ZIP for deeper offline analysis and audits. When a report includes a Summary, the export adds an additional CSV named “Report Summary” that captures the top-line totals and KPIs, enabling stakeholders to reconcile figures without opening the full report. If a report includes charts, the export also adds one CSV per chart using the chart’s current title as the filename, preserving the exact series and data points that fed the visual. These files sit alongside the main dataset in a single ZIP, work with scheduled and ad hoc exports, and provide teams with faster reconciliation, easier spreadsheet workflows, and cleaner handoffs to finance, compliance, and BI tools.
Enhanced PDF Reporting Layout
v13.0.1 Patch 1 introduces a refined PDF reporting layout that removes unnecessary whitespace and forced page breaks, especially around Summary content. Reports now render header, description, scope, summary, charts, and data as a continuous flow, using natural pagination only when space runs out. Visuals are kept intact on a single page, while data tables can continue onto the next page, preserving readability without blank gaps. In practice, this restores the compact, SSRS-like first page that keeps Summary content up front, reduces page count, and makes printed and archived PDFs easier to scan and share.

13.0.1.5924

2025-11-19

Release Notes

13.0.0.5761

2025-10-03

Note: This patch addressed three issues and only changed the build number listed within the Veeam ONE Web Client; the Veeam ONE Client will still display 13.0.0.5630.

High CPU usage in Veeam Analytics Service: Fixed an issue in Veeam.One.Agent.DataCollectionService that continued collecting after the historical collection completed. This behavior also caused higher CPU usage in dependent satellite services, including *.AgentUpdaterService, *.LogAnalyzer, and *.RemedyService.
Unable to enable Veeam Backup & Replication Servers Analytics in Web Client: Fixed an issue where data sources added using the Veeam Analytics Service offline package could not be enabled via Veeam ONE Web Client.
Internal Server Error on Alarms Overview after upgrade: Addressed an error condition when locations were configured for Platform Health Anomalies after upgrading from Veeam ONE 12.

^{This patch was initially released on 2025-09-24 as build 13.0.0.5729 and subsequently repackaged and released as build 13.0.0.5761.}

13.0.0.5630

2025-09-03

Download Information

Updater ZIP

Veeam ONE 13.1 Patch 0 is distributed as a ZIP archive containing five .msp patch installers, which update an existing 13.1 deployment in place. The .msp installers can only be applied to build 13.1.0.7034. Deployments on any earlier build cannot be patched and must be upgraded using the Deployment ISO instead.

Prerequisites and Recommendations

Ensure Veeam ONE 13.1 (build 13.1.0.7034) is installed.
Perform a full backup of the Veeam ONE database.
If the Veeam ONE server is virtual, create a VM snapshot or another rollback point.
Close all Veeam ONE Monitor Client sessions. Use Task Manager to verify that no Veeam ONE or Veeam ONE Monitor client processes are running.
Run the update with local administrator privileges.
Allow the .msp installers to stop and start Veeam ONE services during patching.

Updating

Copy the .zip to the Veeam ONE server and extract it to a local folder, for example C:\Temp\VONE131_P0.
Verify that the five .msp files listed below are present.
Close any running Veeam ONE Monitor Client instances.
Execute all five .msp files. They can be applied in any order.
1. Right-click each .msp file and select Install.
2. Follow the on-screen prompts.
  Services will be stopped and started automatically.

Download 13.1 Patch 0

^{Filename: VeeamONEv13.1_Patch0.zip}

Size: 533 MB
SHA256: 27CBC616F4F588F472E99F3FBBF50582F43E7A5DF072854F67E9D408DD7DB25D

Contents:

VeeamONE.Agent.x64.msp
VeeamONE.Caching.Service.x64_13.1.0.7233.msp
VeeamONE.Monitor.Client.x64_13.1.0.7233.msp
VeeamONE.Monitor.Server.x64_13.1.0.7233.msp
VeeamONE.Reporter.Server.x64_13.1.0.7233.msp

Deployment ISO

Note: Updates from build 13.1.0.7034 must be performed using the .msp files in the Patch zip above.

Use the following ISO for:

New deployments of Veeam ONE 13.1.0.7233.
Upgrading existing deployments of Veeam ONE 12.x or 13.0.x to 13.1.0.7233.

DOWNLOAD latest 13.1 ISO

See the Current Versions Download Page for ISO hashes.

Reboot May Be Required

Please note that a reboot may be required after installing the update.

Please plan accordingly.

ISO Release History

^{Mouse-over or tap the filenames in the table to view a file's checksum.}

Release Date	ISO Filename	Changelog
Veeam ONE 13.1.0.7233 Releases
2026-08-25	VeeamONE_13.1.0.7233_20260821.iso^{SHA256: 935B10C7AFBDA04D776092E56EF36CFC544B1FE791B9645CAE13D69AA44AA150}	Initial Release
Veeam ONE 13.1.0.7034 Releases
2026-07-29	VeeamONE_13.1.0.7034_20260723.iso^{SHA256: EA38FC44C166253C91AF57504C5967799D545393E85CDCB32754BDF87F7ED75A}	Initial Release
Veeam ONE 13.0.2.7159 Releases
2026-08-25	VeeamONE_13.0.2.7159_20260817.iso^{SHA256: 1DD00FC9CDF2DDE30183036D6121803B0B6836529A4CB256BB4A329777BB0151}	Initial Release
Veeam ONE 13.0.2.6723 Releases
2026-05-27	VeeamONE_13.0.2.6723_20260526.iso^{MD5: 8F0DEA814095321CB7FC40A57BA1BC96 SHA1: 0E952FF0CFC97906BDAF8C48DDC383B51986A674}	Initial Release
Veeam ONE 13.0.1.6168 Releases
2026-01-06	VeeamONE_13.0.1.6168_20260102.iso^{MD5: 8697bee519163f844c83fef93c08e58d SHA1: 0856bfc8740221448cde87d7f4b195243cf44c9e}	Initial Release
Veeam ONE 13.0.1.5924 Releases
2025-09-03	VeeamONE_13.0.1.5924_20251117.iso^{MD5: dc922a51065a11a62db0c17b5eed758d SHA1: ce41fa076156def720db1bc73baa6526b61ada99}	Initial Release
Veeam ONE 13.0.0.5630 Releases
2025-09-03	VeeamONE_13.0.0.5630_20250903.iso^{MD5: 5f8a69165f1f4eb2abc7786dbadaa97c SHA1: 4f1d963889c19fdd9b5a9f02fdc4aa3a3f038f5c}	Initial Release

Swipe to show more of the table

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Release Information for Veeam ONE 12 and Updates

2026-08-25T00:00:00Z

Release Information for Veeam ONE 12 and Updates

KB ID:	4705
Product:	Veeam ONE \| 12 \| 12.1 \| 12.2 \| 12.3
Published:	2024-12-23
Last Modified:	2026-08-25

Veeam ONE v12 Releases

12.3.0.7165

2026-08-25

What's New

Veeam ONE 12.3 Patch 1 is a cumulative maintenance and security update for Veeam ONE 12.3. It resolves reported issues across reporting, monitoring, alarms, licensing, and integrations, adds REST API and ServiceNow enhancements, and addresses externally reported security vulnerabilities. Applying this patch is recommended for all Veeam ONE 12.3 deployments.

New Features and Improvements

Cloud Backup Sizes in the REST API
The public REST API now reports the size of cloud backups and of their restore points.

AWS Account Identification
Veeam ONE now collects the AWS Account ID and account alias for workloads protected by Veeam Backup for AWS, and the public REST API returns both for protected Amazon EC2 workloads.

Customizable ServiceNow Short Description
The short description of incidents created in ServiceNow can now be customized.

Resolved Issues

Security

CVE-2026-58074 | Severity: High (8.6)
A vulnerability allowing a high-privileged user to execute arbitrary code on the server.
CVE-2026-64631 | Severity: High (8.6)
A vulnerability allowing a low-privileged user to inject SQL and extract database contents.
CVE-2026-64632 | Severity: High (8.5)
A vulnerability allowing a low-privileged user to capture the NTLM credentials of the Reporter service account.

Alarms

Veeam ONE repeatedly logs an error because triggered alarms are not synchronized correctly between the alarm cache and the database:
```
Cannot insert the value NULL into column 'triggered_alarm_id'
```
The Backup Copy RPO alarm reports incorrect information because deleted backup copy workers are still taken into account.
The Backup Job State alarm does not raise a Warning when a backup job session finishes with a warning.
The Suspicious Incremental Backup Size alarm produces false-positive triggers for Proxmox VE backup jobs.
The License exceeded for Veeam Backup for Microsoft 365 alarm uses an incorrect threshold. The threshold can now be configured with the VbmLicenseCapacityDepletingThreshold registry value.
Backup policy sessions for Microsoft Azure workloads trigger false-positive alarms.
The Unusual Job Duration rule cannot be added to a newly created empty alarm.

Reporting

The Workload Protection History report shows restore points of SAP HANA plug-in backup jobs beyond the retention configured in Veeam Backup & Replication.
The Job Configuration Change Tracking report fails when a job name contains leading or trailing spaces, with the error:
```
Failed to get data set 'User' from report template
```
The Job Configuration Change Tracking report does not show the names of objects added to or removed from a job.
The Host Configuration Chargeback report includes virtual machines that have already been deleted from the infrastructure.
The Custom Infrastructure report cannot be generated for Veeam Agent objects because of duplicate records in the report data set.
The Data Sovereignty Overview report does not show backups stored in public cloud object storage repositories.

The GFS Backup Files report fails to generate with the error:

Failed to retrieve report data. Unable to load dataset 'dsData' from the database

The Backups on Tape report cannot be generated in large environments and fails after a long timeout with the error:
```
Unable to load dataset from the database
```
The Backup Billing report counts backed-up virtual machines per job instead of per job-and-repository combination.
The Tape GFS Backup Files report fails when the report data exceeds the database column length limit, with the error:
```
Unable to load dataset 'dsSummary'
```
The Capacity Planning for Backup Repositories report calculates incorrect values for S3-compatible object storage repositories.
The Protected Computers report includes failover clusters that should not appear in the report.
The Backups on Tape report displays restore points that have already been deleted.
The Restore Sessions by Application Type chart in the Restore Operator Activity report for Veeam Backup for Microsoft 365 shows incorrect data when a one-day reporting period is selected.
Editing the description of a saved report also resets the report scope.
The Protected Cloud Instances report does not show the protection status of some Microsoft Azure objects.
The Custom Infrastructure report truncates guest OS names that exceed the database column length limit. The column length has been increased.
The Immutable Workloads report shows duplicate entries, and shows only the original backup job name for virtual machines protected by backup, backup copy, and backup-to-tape jobs.
The Latest Job Status report calculates the number of job retries incorrectly.
The Backups on Repository report shows invalid last backup dates after an upgrade of Veeam Backup & Replication.
The GFS Backup Files report is missing restore points created by backup copy jobs.
The Infrastructure Overview (Visio) report cannot be generated and fails with the error:
```
Can not get VLANID property for object: NSX (Network)
```
The SLA Compliance report for Veeam Backup for Microsoft 365 calculates the number of restore points incorrectly.
The SureBackup Job Status chart in the Recovery Verification Overview report calculates job statuses incorrectly.

Monitoring and Data Collection

Object properties data collection from VMware vCenter Server completes with warnings when the vCenter Server uses an untrusted SSL certificate.
Storage consumption information for Veeam Cloud Connect tenants is not updated because deleted entities are included in the data collection scope.
Data collection from a Veeam Backup & Replication server stops because of a numeric overflow in the Veeam ONE database.
Virtual switches are not collected from stand-alone Microsoft Hyper-V clusters.
CPU usage charts may display values that exceed 100%.
Veeam ONE Client does not show Capacity Planning details for Veeam Backup for Microsoft 365 backup repositories.
Free and used space is not displayed for Veeam Backup for Microsoft 365 repositories backed by Azure Blob storage.
The 24110 Cloud Connect tenant has been created event is not displayed in the Veeam ONE event viewer.

Scalability and Performance

The Veeam ONE database may become blocked by long-running transactions, which interrupts data collection and reporting.
Veeam ONE performance degrades significantly in large environments.
Memory consumption of the Veeam ONE data collection service grows over time in large environments.
Scheduled generation of the Latest Job Status report fails in large environments because of excessive memory consumption.

Licensing

License usage may be overstated because of duplicate virtual machine records, and the Applications workload type does not show details about consumed instances.
The number of used license instances does not match the number of managed objects.
Virtual machines that consume a license are not shown in the list of licensed virtual machines.
Veeam ONE reports incorrect current license usage, which affects license reporting in Veeam Service Provider Console.

Integrations

Alarm descriptions sent to ServiceNow are truncated, so incidents do not contain the full alarm details.
Incidents created in ServiceNow are not resolved when the corresponding Veeam ONE alarm returns to the Resolved state.
The cmdb_id value cannot be used as a variable when configuring Veeam ONE integration with ServiceNow incidents.
Alarm notifications are no longer delivered to the syslog server after a period of inactivity.

Business View

Business View operations take a significant amount of time to complete in large environments.
A virtual machine that was excluded from a manually created Business View group cannot be added back on the Virtual Machines tab.

Jobs Calendar

Jobs Calendar does not display charts and fails with the error:

When converting a varchar data type to a datetime data type, the value is outside the valid range

Jobs Calendar shows incorrect future run dates and times for a job until the job runs at least once.

Veeam ONE Web Client

The Backup Immutability Status widget fails to load and returns an error.
The Backup Infrastructure Inventory widget shows unexpected data, and backup policy status is displayed incorrectly in Veeam ONE Client.
The Protected VMs Overview widget displays an incorrect full backup size.
The Repository Free Space heatmap widget displays only a limited number of repositories.
Veeam Threat Center cannot be opened because of an incorrect dashboard position calculation, and returns the error:
```
Cannot find the Veeam Threat Center dashboard
```

REST API

The /protectedData/virtualMachines REST API method returns incorrect values, and restore point data is calculated incorrectly for scale-out backup repositories. Two additional fields have been added to the method output.

Installation and Upgrade

Installing a Veeam ONE patch (.msp) from the command line in unattended mode fails with the error:
```
User name could not be empty
```
Alarms exported from Veeam ONE 12.2 cannot be imported into Veeam ONE 12.3.

General

Veeam ONE services fail to start when the certificate private key is imported into the user profile instead of the local machine certificate store.
The Veeam ONE service fails to start with an entity cache error:
```
Entity not found
```

Download Information

Veeam ONE 12.3 Patch 1 is distributed as a ZIP archive containing three .msp patch installers, which update an existing 12.3 deployment in place. No ISO image is released for this patch.

Prerequisites and Recommendations

Ensure Veeam ONE 12.3 (build 12.3.0.4670) is installed.
Perform a full backup of the Veeam ONE database.
If the Veeam ONE server is virtual, create a VM snapshot or another rollback point.
Close all Veeam ONE Monitor Client sessions. Use Task Manager to verify that no Veeam ONE or Veeam ONE Monitor client processes are running.
Run the update with local administrator privileges.
Allow the .msp installers to stop and start Veeam ONE services during patching.

Updating

Copy the .zip to the Veeam ONE server and extract it to a local folder, for example C:\Temp\VONE123_P1.
Verify that the three .msp files listed below are present.
Close any running Veeam ONE Monitor Client instances.
Execute all three .msp files. They can be applied in any order.
1. Right-click each .msp file and select Install.
2. Follow the on-screen prompts.
  Services will be stopped and started automatically.

Download 12.3 Patch 1

^{Filename: VeeamONEv12.3_Patch1.zip}

Size: 114 MB
SHA256: 31CEE1289558A27B607AEBD293199A19F90CA454D58A1953ED083B6E5FA8166A

Contents:

VeeamONE.Reporter.Server.x64_12.3.0.7165.msp
VeeamOoneMonitorCln_x64_12.3.0.7165.msp
VeeamOneMonitorSrv_x64_12.3.0.7165.msp

12.3.0.4670

2024-12-03

12.2.0.4093

2024-08-28

12.1.0.3208

2023-12-05

12.0.1.2591

2023-03-20

12.0.0.2498

2023-02-14

ISO Release History

^{Mouse-over or tap the filenames in the table to view a file's MD5 and SHA1 checksum.}

Release Date	ISO Filename	Changelog
Veeam ONE 12.3.0.4670 Releases
2024-12-03	VeeamONE_12.3.0.4670_20241129.iso^{MD5: ED68BE6A2494ED307F4E052FD05B498D SHA1: 46D3EB4E60FF35D0B495E82F8BA15F12203816C4}	Initial Release
Veeam ONE 12.2.0.4093 Releases
2024-08-28	VeeamONE_12.2.0.4093.iso^{MD5: FA69B33DF49CE64DB3F21841D4C2910D SHA1: 5B2336FC93D0EEBA183E1040993F072BE7944214}	Initial Release
Veeam ONE 12.1.0.3208 Releases
2023-12-05	VeeamONE_12.1.0.3208_20231130.iso^{MD5: 86F25E5F0638B89BCC86E2F0D51DA2BD SHA1: F37E773235B986B8C4C83107E8AD8E007CC3099B}	Initial Release
Veeam ONE 12.0.1.2591 Releases
2023-03-20	VeeamONE_12.0.1.2591_20230314.iso^{MD5: 60A35696D7EBBE4DB64D94144F2DAF20 SHA1: F28DA79BBF8A0AC9D1542F5E68FF6975FAF14BF2}	Initial Release
Veeam ONE 12.0.0.2498 Releases
2023-02-14	VeeamONE_12.0.0.2498_20230125.iso^{MD5: F5FF6B929B88B7776CA4C740C97EF2C9 SHA1: 6F20284449B8EA637BC32A8DEFAA199F9C0EFA9B}	Initial Release

Swipe to show more of the table

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Build Numbers and Versions of Veeam Agent for Linux

2026-08-25T00:00:00Z

Build Numbers and Versions of Veeam Agent for Linux

KB ID:	2681
Product:	Veeam Agent for Linux \| 1.0 \| 2.0 \| 2.0.1 \| 3.0 \| 4.0 \| 5.0 \| 6.0 \| 6.1 \| 6.2 \| 6.3 \| 6.3.1 \| 6.3.2 \| 13 \| 13.1
Published:	2022-09-22
Last Modified:	2026-08-25

This KB article lists all versions of Veeam Agent for Linux and their respective build numbers.

For more information on downloading the latest version of Veeam Agent for Linux, visit:

Version	Build Number	Release Date	Release Notes
*Veeam Agent for Linux* 13 Releases**
Veeam Agent for Linux 13.1.1 ^{included with Veeam Backup & Replication 13.1.1}	13.1.1.4	2026-08-12	HTML
Veeam Agent for Linux 13.1 ^{included with Veeam Backup & Replication 13.1}	13.1.0.252	2026-07-29	HTML
Veeam Agent for Linux 13.0.3 ^{included with Veeam Backup & Replication 13.0.3}	13.0.3.213	2026-08-25	HTML
Veeam Agent for Linux 13.0.2 ^{included with Veeam Backup & Replication 13.0.2}	13.0.2.2	2026-05-27	HTML
Veeam Agent for Linux 13.0.1 P2 ^{included with Veeam Backup & Replication 13.0.1 P2}	13.0.1.404	2026-03-12	HTML
Veeam Agent for Linux 13.0.1 P1 ^{included with Veeam Backup & Replication 13.0.1 P1}	13.0.1.203	2026-01-06	HTML
Veeam Agent for Linux 13.0.1 ^{included with Veeam Backup & Replication 13.0.1}	13.0.1.94	2025-11-19	HTML
Veeam Agent for Linux 13 ^{included with Veeam Backup & Replication 13 Veeam Software ApplianceThis build of Veeam Agent for Linux is included with the Veeam Software Appliance, but will become available for standalone download at a later date.}	13.0.0.772	2025-09-03
*Veeam Agent for Linux* 6 Releases**
Veeam Agent for Linux 6.3.2 P2 ^{included with Veeam Backup & Replication 12.3.2.4854}	6.3.2.1405	2026-06-09	HTML
Veeam Agent for Linux 6.3.2 P1 ^{included with Veeam Backup & Replication 12.3.2.4465}	6.3.2.1307	2026-03-12	HTML
Veeam Agent for Linux 6.3.2 ^{included with Veeam Backup & Replication 12.3.2}	6.3.2.1207	2025-06-17	HTML
Veeam Agent for Linux 6.3.1 ^{included with Veeam Backup & Replication 12.3.1}	6.3.1.1016	2025-03-19	HTML
Veeam Agent for Linux 6.3 ^{included with Veeam Backup & Replication 12.3}	6.3.0.73	2024-12-03	HTML
Veeam Agent for Linux 6.2 ^{included with Veeam Backup & Replication 12.2}	6.2.0.101	2024-08-28	HTML
Veeam Agent for Linux 6.1.2 ^{included with Veeam Backup & Replication 12.1.2}	6.1.2.1781	2024-05-21	PDF
Veeam Agent for Linux 6.1 ^{included with Veeam Backup & Replication 12.1}	6.1.0.1498	2023-12-05	—
Veeam Agent for Linux 6.0.3 ^{included with Veeam Backup & Replication 12 P20230718}	6.0.3.1221	2023-07-20	PDF
Veeam Agent for Linux 6.0.2 ^{included with Veeam Backup & Replication 12 P20230412}	6.0.2.1168	2023-04-13	PDF
Veeam Agent for Linux 6.0 GA ^{included with Veeam Backup & Replication 12 GA}	6.0.0.1060	2023-02-14	PDF
Veeam Agent for Linux 6.0 RTM ^{included with Veeam Backup & Replication 12 RTM}	6.0.0.1058	2023-01-30	—
*Veeam Agent for Linux* 5 Releases**
Veeam Agent for Linux 5.0.2.4707 ^{included with Veeam Backup & Replication 11a P20240304}	5.0.2.4707	2024-03-07	( ! )This build was included within the Veeam Backup & Replication 11a P20240304 package. See KB4245
Veeam Agent for Linux 5.0.2 ^{included with Veeam Backup & Replication 11a P20211211}	5.0.2.4567	2021-12-22	PDF
Veeam Agent for Linux 5.0.1 GA ^{included with Veeam Backup & Replication 11a GA}	5.0.1.4493	2021-10-07	PDF
Veeam Agent for Linux 5.0.1 RTM ^{included with Veeam Backup & Replication 11a RTM}	5.0.1.4493	2021-09-24	—
Veeam Agent for Linux 5 GA ^{included with Veeam Backup & Replication 11 GA}	5.0.0.4318	2021-02-24	PDF
Veeam Agent for Linux 5 RTM ^{included with Veeam Backup & Replication 11 RTM}	5.0.0.4318	2021-02-11	—
*Veeam Agent for Linux* 4 Releases**
Veeam Agent for Linux 4.0.1 ^{included with Veeam Backup & Replication 10a GA}	4.0.1.2365	2020-07-21	PDF
Veeam Agent for Linux 4.0 ^{included with Veeam Backup & Replication 10 GA}	4.0.0.1961	2020-02-18	PDF
*Veeam Agent for Linux* 3 Releases**
Veeam Agent for Linux 3.0.2 ^{included with Veeam Backup & Replication 9.5 U4b}	3.0.2.1185	2019-07-16	PDF
Veeam Agent for Linux 3.0.1 ^{included with Veeam Backup & Replication 9.5 U4a}	3.0.1.1046	2019-03-26	PDF
Veeam Agent for Linux 3.0 ^{included with Veeam Backup & Replication 9.5 U4}	3.0.0.865	2019-01-22	PDF
*Veeam Agent for Linux* 2 Releases**
Veeam Agent for Linux 2.0.1	2.0.1.665	2018-07-03	PDF
Veeam Agent for Linux 2.0	2.0.0.400	2017-12-19	—
*Veeam Agent for Linux* 1 Releases**
Veeam Agent for Linux 1.0.1	1.0.1.364	2017-05-22	PDF
Veeam Agent for Linux 1.0	1.0.0.944	2016-12-13	—

Swipe to show more of the table

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Build Numbers and Versions of Veeam ONE

2026-08-25T00:00:00Z

Build Numbers and Versions of Veeam ONE

KB ID:	4357
Product:	Veeam ONE \| 6.0 \| 6.5 \| 7.0 \| 8.0 \| 9.0 \| 9.5 \| 10 \| 11 \| 12 \| 12.1 \| 12.2 \| 12.3 \| 13 \| 13.1
Published:	2022-09-22
Last Modified:	2026-08-21

This KB article lists all versions of Veeam ONE and their respective build numbers.

For more information on downloading the latest version of Veeam ONE, visit:

Version	Build Number	Release Date	Release Notes
Veeam ONE 13 Releases
Veeam ONE 13.1 P0	13.1.0.7233	2026-08-25	KB4762
Veeam ONE 13.1	13.1.0.7034	2026-07-29	HTML
Veeam ONE 13.0.2 P1	13.0.2.7159	2026-08-25	KB4762
Veeam ONE 13.0.2	13.0.2.6723	2026-05-27	KB4762
Veeam ONE 13.0.1 P1	13.0.1.6168	2026-01-06	KB4762
Veeam ONE 13.0.1 GA	13.0.1.5924	2025-11-19	HTML
Veeam ONE 13.0.1 RTM	13.0.1.5860	2025-11-04
Veeam ONE 13 Patch 1	13.0.0.5761	2025-10-03	KB4762
~~Veeam ONE 13 Patch 1~~ (Note)This build was retracted and rereleased as build 13.0.0.5761.	~~13.0.0.5729~~	2025-09-24	KB4762
Veeam ONE 13	13.0.0.5630	2025-09-03	HTML
Veeam ONE 12 Releases
Veeam ONE 12.3 P1	12.3.0.7165	2026-08-25	KB4705
Veeam ONE 12.3	12.3.0.4670	2024-12-03	HTML
Veeam ONE 12.2	12.2.0.4093	2024-08-28	HTML
Veeam ONE 12.1	12.1.0.3208	2023-12-05	PDF
Veeam ONE 12 P20230314	12.0.1.2591	2023-03-20	KB4430
Veeam ONE 12 GA	12.0.0.2498	2023-02-14	PDF
Veeam ONE 12 RTM	12.0.0.2498	2023-01-30	-
Veeam ONE 11 Releases
Veeam ONE 11a GA	11.0.1.1880	2021-10-07	PDF KB4197
Veeam ONE 11a RTM	11.0.1.1880	2021-09-28	-
Veeam ONE 11 GA	11.0.0.1379	2021-02-24	PDF KB4109
Veeam ONE 11 RTM	11.0.0.1379	2021-02-09	-
Veeam ONE 10 Releases
Veeam ONE 10a	10.0.2.1094	2020-07-21	PDF KB3227
Veeam ONE 10	10.0.0.750	2020-02-18	KB3011
Veeam ONE 9.5 Releases
Veeam ONE 9.5 U4a	9.5.4.4587	2019-09-11	PDF KB3002
Veeam ONE 9.5 U4	9.5.4.4566	2019-02-22	KB2876
Veeam ONE 9.5 U3	9.5.0.3801	2017-12-19	PDF KB2354
Veeam ONE 9.5 U1	9.5.0.3254	2017-01-20	KB2223
Veeam ONE 9.5 GA	9.5.0.3201	2016-11-16	-
Veeam ONE 9 Releases
Veeam ONE 9 U1	9.0.0.2088	2016-03-24	KB2115
Veeam ONE 9 GA	9.0.0.2062	2016-01-12	PDF
Veeam ONE 8 Releases
Veeam ONE 8 U2	8.0.0.1669	2015-04-27	PDF KB2025
Veeam ONE 8 P1	8.0.0.1615	2015-02-26	KB1986
Veeam ONE 8 GA	8.0.0.1569	2014-11-06	-
Veeam ONE 8 RTM	8.0.0.1567	-	-
Veeam ONE 7 Releases
Veeam ONE 7 P2	7.0.0.949	2014-09-18	KB1927
Veeam ONE 7 R2	7.0.0.919	2013-12-05	PDF KB1841
Veeam ONE 7	7.0.0.876	2013-08-15	-
Veeam ONE 6.5 Releases
Veeam ONE 6.5 P1	6.5.0.686	2012-12-18	KB1700
Veeam ONE 6.5	6.5.0.676	2012-11-01	-
Veeam ONE 6 Releases
Veeam ONE 6	6.0.0.520	2012-04-23	-

Swipe to show more of the table

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Build Numbers and Versions of Veeam Agent for Oracle Solaris

2026-08-25T00:00:00Z

Build Numbers and Versions of Veeam Agent for Oracle Solaris

KB ID:	4356
Product:	Veeam Agent for Oracle Solaris \| 1.0 \| 2.0 \| 2.1 \| 3.0 \| 4.0 \| 4.1 \| 4.5 \| 4.6 \| 4.6.1 \| 13 \| 13.1
Published:	2022-09-22
Last Modified:	2026-08-21

This KB article lists all versions of Veeam Agent for Oracle Solaris and their respective build numbers.

For more information on downloading the latest version of Veeam Agent for Oracle Solaris, visit:

Version	Build Number	Release Date	Release Notes
*Veeam Agent for Oracle Solaris* 13 Releases**
Veeam Agent for Oracle Solaris 13.1 ^{included with Veeam Backup & Replication 13.1}	13.1.0.2260	2026-07-29	HTML
Veeam Agent for Oracle Solaris 13.0.3 ^{included with Veeam Backup & Replication 13.0.3}	13.0.3.2122	2026-08-25	HTML
Veeam Agent for Oracle Solaris 13.0.2 ^{included with Veeam Backup & Replication 13.0.2}	13.0.2.2108	2026-05-27	HTML
Veeam Agent for Oracle Solaris 13.0.1 P1 ^{included with Veeam Backup & Replication 13.0.1 P2}	13.0.1.2106	2026-03-12	HTML
Veeam Agent for Oracle Solaris 13.0.1 ^{included with Veeam Backup & Replication 13.0.1}	13.0.1.2030	2025-11-19	HTML
Veeam Agent for Oracle Solaris 13 ^{included with Veeam Backup & Replication 13 Veeam Software ApplianceThis build of Veeam Agent for Oracle Solaris is included with the Veeam Software Appliance, but will become available for standalone download at a later date.}	13.0.0.1973	2025-09-03
*Veeam Agent for Oracle Solaris* 4 Releases**
Veeam Agent for Oracle Solaris 4.6.1 ^{included with Veeam Backup & Replication 12.3.1}	4.6.1.1789	2025-03-19	HTML
Veeam Agent for Oracle Solaris 4.6 ^{included with Veeam Backup & Replication 12.3}	4.6.0.1772	2024-12-03	HTML
Veeam Agent for Oracle Solaris 4.5 ^{included with Veeam Backup & Replication 12.2}	4.5.0.1616	2024-08-28	HTML
Veeam Agent for Oracle Solaris 4.1.1 ^{included with Veeam Backup & Replication 12.1.2}	4.1.1.1423	2024-05-21	PDF
Veeam Agent for Oracle Solaris 4.1 ^{included with Veeam Backup & Replication 12.1}	4.1.0.1401	2023-12-05	—
Veeam Agent for Oracle Solaris 4.0.1 ^{included with Veeam Backup & Replication 12 P20230412}	4.0.1.1173	2023-04-13	PDF
Veeam Agent for Oracle Solaris 4.0 ^{included with Veeam Backup & Replication 12 GA}	4.0.0.1029	2022-12-05	PDF
*Veeam Agent for Oracle Solaris* 3 Releases**
Veeam Agent for Oracle Solaris 3.0 ^{included with Veeam Backup & Replication 11a GA}	3.0.0.561	2021-10-07	PDF
*Veeam Agent for Oracle Solaris* 2 Releases**
Veeam Agent for Oracle Solaris 2.1	2.1.0.276	2020-10-26	PDF
Veeam Agent for Oracle Solaris 2.0	2.0.0.126	2020-06-01	PDF
*Veeam Agent for Oracle Solaris* 1 Releases**
Veeam Agent for Oracle Solaris 1.0	1.0.0.41	2018-09-20	PDF

Swipe to show more of the table

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Veeam Support Knowledge Base

Applications Restored by Veeam Kasten Disaster Recovery Fail to Export with: invalid repository password

Applications Restored by Veeam Kasten Disaster Recovery Fail to Export with: invalid repository password

Challenge

Cause

Solution

More Information

Release Information for Veeam Service Provider Console 9 and Updates

Release Information for Veeam Service Provider Console 9 and Updates

Veeam Service Provider Console 9 Builds

9.3.0.35706

2026-09-04

Resolved Issues

Scalability

Veeam Backup & Replication Integration

REST API

9.3.0.35057

2026-07-29

Release Information

9.2.1.33875

2026-05-27

Resolved Issues

Security

General

Upgrade

Veeam Backup & Replication Integration

Veeam Cloud Connect Integration

Veeam Backup for Microsoft 365 Integration

Veeam Vault Integration

Veeam Agent Integration

REST API

9.2.0.33215 (9.2 GA)

2026-04-09

Release Information

9.1.0.30713

2025-12-05

New Features and Enhancements

General

Resolved Issues

9.1.0.30636 (9.1 GA)

2025-11-19

Release Information

9.1.0.30345 (9.1 RTM)

2025-11-07

Release Information

9.0.0.29860

2025-10-21

Resolved Issues

Upgrade

Data Collection

Licensing

9.0.0.29555

2025-09-03

Release Information

Download Information

Deployment Guidance

Patch Install

Deployment ISO

ISO Release History

Build Numbers and Versions of Veeam Service Provider Console

Build Numbers and Versions of Veeam Service Provider Console

Related Articles

After Veeam ONE 13.1.0.7034 Upgrade: No connection could be made because the target machine actively refused it. (localhost:2743)

After Veeam ONE 13.1.0.7034 Upgrade: No connection could be made because the target machine actively refused it. (localhost:2743)

Challenge

Cause

Solution

How to Allow Company Users to Open Veeam Backup & Replication Web UI Wizards From Veeam Service Provider Console

How to Allow Company Users to Open Veeam Backup & Replication Web UI Wizards From Veeam Service Provider Console

Purpose

Solution

More Information

Build Numbers and Versions of Veeam Backup for Google Cloud

Build Numbers and Versions of Veeam Backup for Google Cloud

Related Articles

Proxmox VE Worker VM Deployment Fails When Default Local Storage Is Disabled

Proxmox VE Worker VM Deployment Fails When Default Local Storage Is Disabled

Challenge

Cause

Solution

**Veeam Backup for Microsoft 365 Integration**