[V13.1] Top Issues Tracker

[Dima P.]

Last updated: August 10th @ 22K unique downloads (multiple downloads from the same account within one week are deduplicated)

Known Issues
The following is a list of common V13.1 issues that have resulted in a significant number of recurring support cases.

#1: Direct backup to immutable object storage may fail with "Blockset blocks immutability mismatch." error
Scope: backup jobs that write directly to immutable object storage may fail with a "Blockset blocks immutability mismatch" error. In some cases, an inconsistency can occur while updating immutability metadata, causing checkpoint creation to fail for the affected job. Existing backups and restore points remain intact and recoverable; however, the affected backup job will continue to fail until the issue is resolved.
Status: Hotfix is under investigation.

#2: Backup job reports "Failed to explore PostgreSQL instance" after upgrading to v13.1
Scope: After upgrading to v13.1, backup jobs with Application-Aware Processing enabled may start reporting "Failed to explore PostgreSQL instance" warnings for Windows guest machines. This can occur when Veeam detects a PostgreSQL process, including embedded PostgreSQL instances installed by third-party applications, but cannot establish a connection using the discovered configuration. As a result, jobs that were previously successful may begin generating warnings after the upgrade.
Status: A hotfix to reduce the severity of these warnings is under investigation.

#3: Core services fail to start after upgrading a Veeam Software Appliance that is configured to use an HTTP/HTTPS proxy.
Scope: After upgrading to Veeam Backup & Replication 13.1, the appliance may become inaccessible because local service communication is incorrectly routed through the configured proxy. This can result in Web UI HTTP 502 errors and "Failed to connect to identity service" messages. Clean installations are not affected.
Status: Hotfix is under investigation.
Workaround: In the Host Manager TUI, go to Host Configuration → HTTP proxy, enable the proxy, enter its address, and select OK. VBR restarts automatically, which resolves the issue.