Veeam Intelligent Diagnostics updates

[RomanK]

Veeam Intelligent Diagnostics (VID) is a feature that automatically detects known issues in the configuration and performance of backup infrastructure.
This thread will be used for tracking VID signature updates.

Follow this link to get information on how to update VID signatures.

Veeam Intelligent Diagnostics packages are cumulative and include previously released packages.

Previous updates: Veeam Intelligent Diagnostics updates (archive)

[RomanK]

Download link: Signatures v1.7.90
Compatibility: Veeam ONE 12.2, Veeam ONE 12.3

Backup fails with "Root element is missing" error after a summary.xml write failure
After a failure on the summary.xml write, each subsequent run tries to deliver it, resulting in a crash.

VBR server becomes unresponsive as a result of "Unexpected end of stream" errors
Failed connections leave orphaned threads, which have memory allocated, in the backup service. The build up of such threads leads to the possible consumption of all available RAM on the VBR server.

[RomanK]

Download link: Signatures v1.7.102
Compatibility: Veeam ONE 12.2, Veeam ONE 12.3

NAS backup job fails with "An existing connection was forcibly closed by the remote host"
The proxy agent is unable to get file information about a backup's root object and throws a wrong exception, leading to the proxy crash.

[RomanK]

Download link: Signatures v1.7.105
Compatibility: Veeam ONE 12.2, Veeam ONE 12.3

Veeam Backup & Replication 12.3.1 (build 12.3.1.1139) is available
It is strongly recommended that you upgrade your existing Veeam Backup & Replication installations to the latest version to get the best experience when using this product.

Security vulnerability CVE-2025-23120 in Veeam Backup & Replication
The issue is caused by a malfunction that allows all standard domain accounts to execute code on the Backup Server.

Security vulnerability CVE-2025-1094 in Veeam Backup & Replication (PostgreSQL)
Improper neutralization of quoting syntax in PostgreSQL functions allows a database input provider to achieve SQL injection in certain usage patterns.

Log backup is performed twice during the same run
Root cause is related to RPC connectivity breaking during calls to backup logs resulting in a duplication of calls.

[RomanK]

Download link: Signatures v1.7.110
Compatibility: Veeam ONE 12.2, Veeam ONE 12.3

NAS backup job failed to complete with "Container doesn't exist in backup"
The issue occurs when NetApp native changed files tracking data can contain info about the objects not added to file share backup, hidden system directories or excluded folders.

NAS backup job failed to complete with "Unable to process the file share: source was changed from NFS v3 to NFS v4"
A preceding hidden issue causes this problem during rescanning of NFS access validation to the shares on the affected NetApp storage system. Later, when validation is successful, NFS 4.1 use is forced, which can cause a conflict if NFS 3 was already used for this NAS filer.

Potential issues with Veeam Backup & Replication log folder size
The issue is caused by archival sessions endlessly looping at writing the backup files which were detected to freeze and move to the archive tier. As a result, archival session log excessively grows which might cause Veeam Backup & Replication server to run out of free space on a disk that stores Veeam log folder.