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:
The patch is now publicly available and can be downloaded from https://www.veeam.com/kb4738.The fix is embedded in the product ISO, meaning all new installations are automatically patched and do not require any additional steps.Resolved with the Day 0 patch.
#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: Reduced the severity of these warnings with the Day 0 patch. The patch is now publicly available and can be downloaded from https://www.veeam.com/kb4738. The fix is embedded in the product ISO, meaning all new installations are automatically patched and do not require any additional steps.
#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.
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.
Status: Resolved with the Day 0 patch. The patch is now publicly available and can be downloaded from https://www.veeam.com/kb4738. The fix is embedded in the product ISO, meaning all new installations are automatically patched and do not require any additional steps.
#4: Jobs pointed to Cloud Connect repository may fail after upgrade to 13.1.
Scope: After upgrading tenant environments to Veeam Backup & Replication 13.1, Cloud Connect Backup Copy jobs may fail when connecting to a service provider that uses a publicly trusted SSL certificate. The issue occurs when the certificate revocation cache is empty, causing certificate validation to fail.
Workaround: Contact support team to enable the registry/configuration option to ignore the certificate validation error. Manually refresh the certificate revocation cache. Reconnect to the service provider and accept the certificate again.
Status: Status: Resolved with the Day 0 patch. The patch is now publicly available and can be downloaded from https://www.veeam.com/kb4738. The fix is embedded in the product ISO, meaning all new installations are automatically patched and do not require any additional steps.