[V13] Top Issues Tracker

[Gostev]

Last updated: December 12th

53200 unique users downloaded
26000 deployments seen by license server

#1: All hypervisor and cloud plug-ins are missing
Scope: Installable software for Microsoft Windows with MFA enabled.
Symptoms: AWS, GCP, Azure, Kasten, KVM, PVE, SCP plugins are missing.
Cause 1: NT AUTHORITY\SYSTEM account lacks service account privileges, which prevents plug-in operations when MFA is enabled.
Cause 2: Your backup server certificate is too old and does not support generating child certificates that are essential to plug-in operations.
Status: To work around the issue, add NT AUTHORITY\SYSTEM as a service account under Users & Roles. If this does not help, you may also need to generate new backup server certificate using the Options > Security > Install dialog. For more information, please refer to KB4687. ISO versions 20251130 and later detects and warns about the presence of incompatible certificates.

#2: Unable to connect to a backup server after upgrading it to V13
Scope: Installable software for Microsoft Windows.
Symptoms: Setup fails to start with the VeeamBackupRESTSvc service at the end of the upgrade. The service also times out starting after reboot, preventing the dependent services from starting. As a result, it's not possible to connect to the backup server with a backup console or open its web UI.
Cause: Likely related to a limited backup server performance.
Status: To work around the issue, increase the services time out using the following command (default timeout is 30 sec, this will change it to 60 sec):
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control" -Name ServicesPipeTimeout -Value 60000 -Type DWORD
ISO versions 20251130 and later set this value automatically.

[Gostev]

Last updated: October 6th (1 month in)

9000 unique users downloaded
4000 deployed appliances seen by our license server
2500 appliances are streaming extended telemetry (new to V13)
18 JeOS security updates published

The following is the list of top V13 software appliance issues resulting in significant number of questions, support cases or just critical enough to be aware of.

#1: Unable to establish connection to Windows machines and SMB shares.
Scope: All functionality.
Symptoms: Error messages may vary depending on functionality but usually refer to Windows credentials and includes some of the following: "Cannot find KDC for requested realm", "NT_STATUS_NO_SUCH_DOMAIN".
Cause: Kerberos authentication is not properly configured or not available at all.
Status: This is by design, software appliance does not support NTLM authentication because it's insecure and has been deprecated by Microsoft. For environments without Kerberos, install the Veeam Deployment Kit on the Windows system to enable certificate-based authentication.

#2: Incorrect TOTP codes for MFA
Scope: MFA configuration for host administrator and security officer accounts in TUI.
Symptoms: Setting up MFA using the QR code always works while using the secret key provided for manual entry does not always work.
Cause: Clicking "Show QR Code" button generates a new secret key, rendering the currently displayed one no longer valid for usage.
Status: The issue is fixed in version 13.0.1

#3: Misbehaving DNS and network configuration settings
Scope: Managing software appliance network settings using the Host Management web UI and in the TUI.
Symptoms: DNS and network settings appear not to apply correctly, settings values remain empty.
Cause: Bug: DNS settings cannot be saved with the Host Management web UI when using a static IP address. By design: using advanced network settings in the TUI instead always works, however some changed settings will not apply until the host is rebooted which may leave a false impression of an issue.
Status: The issue with static IP addresses is fixed in version 13.0.1