Veeam Support Knowledge Base https://www.veeam.com/services/open/kb/rss-feed 2026-09-18T15:26:39Z Veeam Software <![CDATA[How to Configure HTTP Proxy for Veeam Service Provider Console 9.3+]]> https://www.veeam.com/kb4930 2026-09-18T00:00:00Z 2026-09-18T00:00:00Z

How to Configure HTTP Proxy for Veeam Service Provider Console 9.3+

KB ID: 4930
Product: Veeam Service Provider Console | 9.3
Published: 2026-09-18
Last Modified: 2026-09-18

Purpose

This article explains how to configure an HTTP proxy for Veeam Service Provider Console 9.3 and later, which introduced a dedicated proxy configuration mechanism that is disabled by default and does not use the WinHTTP, Internet Options, or environment variable proxy settings described in KB4875.

If a proxy is required to reach the internet and this mechanism is not configured, product update, license auto-update, and single sign-on features fail. Typical entries appear in Server.log:

VeeamAutoLk>>AutoLkClient: Failed to get data from the AutoLk service ... A connection attempt failed ... (vac.butler.veeam.com:443)

Saml2IdentityProvider: Failed to retrieve data from 'https://login.microsoftonline.com/...' due network error. Exception: System.Net.WebException: The operation has timed out.

 

In versions prior to Veeam Service Provider Console 9.3, the software had no dedicated proxy setting and always used the .NET defaults: the HTTPS_PROXY/HTTP_PROXY environment variables first, then the Internet Options (WinINET) proxy of the service account, as described in KB4875.

Solution

Summary

Veeam Service Provider Console 9.3 introduced a central HttpClient configuration section. All HTTP clients created by the Veeam Service Provider Console Server, Web UI, REST API, and Management Agent read from it, and the default value of HttpClient_UseProxy is False. Until this key is set to True, every outbound connection is sent directly, regardless of OS-level proxy settings.

Configuration Key Reference

Key Type Default Description
HttpClient_UseProxy Boolean False

Master switch.

  • False: no proxy is used, and OS-level settings are ignored.
  • True: uses HttpClient_ProxyAddress if set, otherwise the OS proxy.
HttpClient_ProxyAddress String   Proxy URI, for example http://proxy.corp.example:8080
  • Empty: the OS proxy is used, as described in Option 2 below (see also KB4875).
  • Set: the proxy is configured directly in Veeam Service Provider Console, as described in Option 1 below.

The settings below apply only when HttpClient_ProxyAddress is set, and do not affect the legacy OS proxy settings (KB4875).
HttpClient_ProxyBypassOnLocal Boolean True Sends local destinations directly rather than through the proxy.
HttpClient_ProxyBypassList List
|-separated		   Regular expressions for additional destinations that bypass the proxy.
HttpClient_ProxyUsername String   Proxy user. Credentials are sent only when this is non-empty.
HttpClient_ProxyPassword String   Proxy password. Stored in clear text in the configuration file.
Swipe to show more of the table

Part 1: Identify Configuration File Location

The HttpClient_* keys are added to one of two JSON files, depending on which Veeam Service Provider Console component is being configured:

  • Veeam Service Provider Console Server, Web UI, and REST API:
    %ProgramData%\Veeam\Veeam Availability Console\Configuration\Service\configuration.overrides.json
  • Veeam Service Provider Console Management Agent:
    %ProgramData%\Veeam\Veeam Availability Console\Configuration\Agent\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.

Part 2: Add the Keys to the Configuration File

Add the HttpClient_* keys to the GeneratedConfiguration object in the file identified above. Keep any existing keys already present in the file. Every value, including Boolean values, must be written as a quoted JSON string, for example "True", not true.

Option 1: Use Modern Built-In Proxy Client (Recommended)

This mode is recommended because it does not depend on Windows Internet Options, and unlike legacy proxy methods, it supports proxy authentication.

Configuration Example

{
  "GeneratedConfiguration": {
    "HttpClient_UseProxy": "True",
    "HttpClient_ProxyAddress": "http://proxy.domain.tld:8080",
    "HttpClient_ProxyBypassList": "^https?://[^/]+\\.domain\\.tld(:\\d+)?$|^https?://10\\."
  }
}
  • Important: an invalid HttpClient_ProxyAddress value makes every HTTP client creation fail, which breaks license auto-update, single sign-on, and other HTTP-based features until it is corrected.
  • HttpClient_ProxyBypassList is one string with entries separated by |, where each entry is a .NET regular expression matched against scheme://host. Remember to double the backslashes inside JSON.

Using Proxy Authentication

If the proxy requires authentication, add the username and password keys as well, for example:

{
  "GeneratedConfiguration": {
    "HttpClient_UseProxy": "True",
    "HttpClient_ProxyAddress": "http://proxy.domain.tld:8080",
    "HttpClient_ProxyUsername": "DOMAIN\\username",
    "HttpClient_ProxyPassword": "<password>"
  }
}
Credentials are sent when the proxy challenges the connection (Basic, Digest, NTLM, or Negotiate, depending on what the proxy offers). Because the password is stored in plaintext, customers are advised to restrict NTFS permissions on the Configuration folder, or use an unauthenticated proxy rule for the Veeam Service Provider Console server's IP address instead.
Option 2: Use Legacy OS Proxy Behavior

This mode makes Veeam Service Provider Console resolve the proxy the same way any .NET application does on Windows: the HTTPS_PROXY and HTTP_PROXY environment variables first, then the Internet Options (WinINET) proxy of the account running the service. See KB4875 for how to configure either of these. Note: The netsh winhttp proxy is never used by Veeam Service Provider Console.

Configuration Example

{
  "GeneratedConfiguration": {
    "HttpClient_UseProxy": "True"
  }
}

Part 3: Restart Services

The keys are read once at process start, so the running process will not pick up the edit until it restarts:

  • Veeam Service Provider Console Server, Web UI, and REST API: restart the Veeam Service Provider Console Server service and recycle the IIS application pools for the Web UI and RESTful APIs sites (or run iisreset).
  • Veeam Service Provider Console Management Agent: restart the Veeam Service Provider Console Management Agent service.

Part 4: Verify Functionality

Confirm the proxy is being used by checking the proxy's access logs for CONNECT requests from the Veeam Service Provider Console server, or by retrying the operation that previously failed, such as a license auto-update or single sign-on.

More Information

What This Affects

Once enabled, HttpClient_UseProxy covers:

  • Server: AutoLK/Butler license and update checks, license auto-update, plugin package downloads, support-bundle API calls, SAML 2.0 SSO metadata retrieval, and REST calls to managed Veeam Backup & Replication, Veeam Backup for Microsoft 365, and Veeam ONE servers.
  • Web UI and REST API: the same HTTP client traffic as the Server, since the Web UI reads the Server's configuration file.
  • Management Agent: REST calls to the managed products it monitors. Keep those products in the bypass list if the agent must also reach the internet, or their traffic is sent to the proxy too.

A few flows are not covered by HttpClient_UseProxy and continue to use the .NET defaults, that is, the OS proxy via environment variables or Internet Options as described in KB4875, regardless of this setting:

  • Download of Veeam Backup & Replication and Veeam ONE deployment answer files.
  • Upload of the support bundle to the pre-signed storage URL.
  • Time synchronization for TOTP multi-factor authentication.
  • Google OAuth client-secret validation for Veeam Plug-In for Google Cloud credentials in the Web UI.
  • Webhook alarm actions.

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.

]]> <![CDATA[How to Configure HTTP Proxy for Windows-based Veeam Components]]> https://www.veeam.com/kb4875 2026-09-18T00:00:00Z 2026-09-18T00:00:00Z

How to Configure HTTP Proxy for Windows-based Veeam Components

KB ID: 4875
Product: Veeam Backup & Replication
Veeam ONE
Veeam Agent for Microsoft Windows
Veeam Cloud Connect
Published: 2026-07-14
Last Modified: 2026-09-18

Purpose

This article explains how to configure an HTTP proxy for Windows-based Veeam components when the server must reach the internet through a proxy. It applies to Veeam products installed on Windows, including Veeam Backup & Replication, Veeam Cloud Connect, Veeam ONE, Veeam Service Provider Console, and Veeam Agent for Microsoft Windows.

Note: This article covers Windows-based components only. For Linux-based components (the Veeam Software Appliance and JeOS-deployed appliances), see KB4807.

Connecting to a Veeam Cloud Connect Provider

A tenant's Veeam Backup & Replication server cannot reach a Veeam Cloud Connect provider through an HTTP or HTTPS proxy. Cloud Connect traffic from the tenant's backup server is not HTTP(S)-based and therefore ignores proxy settings.

Veeam Service Provider Console 9.3 and Later

Starting with Veeam Service Provider Console 9.3, the WinHTTP, Internet Options, and environment variable proxy methods described below have no effect on the Veeam Service Provider Console Server, Web UI, REST API, or Management Agent clients. These components read their own HttpClient_UseProxy setting, which is disabled by default. For information about configuring HTTP proxy with Veeam Service Provider Console 9.3, review KB4930.

Solution

Summary

Configuring an HTTP proxy for Veeam components on Windows requires setting the proxy in up to three different places:

  • WinHTTP is used by various Veeam components and is configured with netsh.
  • WinINET (Internet Options) is used by components that rely on Windows Internet and is configured per user account.
  • System-wide environment variables (HTTP_PROXY, HTTPS_PROXY, and NO_PROXY) are new in Veeam Backup & Replication 13.

In Veeam Backup & Replication 13, many components were moved to modern .NET Core, and as such, they read their proxy configuration from environment variables first, falling back to WinINET (Internet Options) only when no environment variables are set. These components will not read the WinHTTP (netsh) configuration at all.

HTTP Proxy Authentication Is Not Supported

Proxy authentication is not supported. Because WinHTTP cannot authenticate to a proxy, the HTTP proxy must not require authentication. Use a proxy that permits connections without credentials, for example one that authorizes clients by source IP address.

Configure WinHTTP Proxy
System-Wide Configuration
This change is system-wide and will affect all applications that use WinHTTP, including other third-party or Windows services that use WinHTTP (e.g., Windows Update).

Check Current WinHTTP Proxy Settings

This command will display the current WinHTTP settings:

netsh winhttp show proxy

Set WinHTTP Proxy Settings

This command can be used to set a WinHTTP proxy:

netsh winhttp set proxy proxy-server="<proxy>:<port>"

Note: Replace <proxy> and <port> in quotes with the actual proxy server's hostname or IP and the port it uses. For example, this command would set the proxy for all protocols to use proxy.domain.tld (192.168.111.111) port 8080:

netsh winhttp set proxy proxy-server="192.168.111.111:8080"

netsh winhttp set proxy proxy-server="proxy.domain.tld:8080"

A more advanced example using a specific protocol and exclusions:

netsh winhttp set proxy proxy-server="http=proxy.domain.tld:8080" bypass-list="*.labdomain.tld;*.devlab.tld"

Reset WinHTTP Proxy

This command can be used to reset the WinHTTP settings back to default (no proxy).

netsh winhttp reset proxy
Configure Internet Options (WinINET) Proxy
Proxy settings within Internet Options are configured per user. While the account you are logged in as may be able to access the internet through the proxy, the backup service account may not have access if that account hasn't had its internet connection settings configured.
Account-Level Configuration
Assigning the Proxy Settings for an account, whether a dedicated account or LocalSystem, will allow all services and applications that use that account to access the internet using the configured proxy.

Identify the Service Account

Open Services and check which account is listed in the 'Log On As' column for the following services, based on the Veeam product in use:

  • Veeam Backup & Replication — Veeam Backup Service
  • Veeam Agent for Microsoft Windows — Veeam Agent for Microsoft Windows
  • Veeam ONE — Veeam ONE Monitoring Service
  • Veeam Cloud Connect — Veeam Backup Service
  • Veeam Service Provider Console — Veeam Management Portal Service

The account can also be checked using PowerShell. The following example is for Veeam Backup & Replication or Veeam Cloud Connect:

Get-CimInstance Win32_Service -Filter "Name='VeeamBackupSvc'" | Select-Object Name, StartName

Service Account is Local or Domain User

If the Service Account is a user, perform the following steps.

  1. Log on to the machine using that Service Account.
  2. Open Internet Options (inetcpl.cpl)
  3. Switch to the Connections tab.
  4. Click 'LAN settings'.
  5. Configure the Proxy settings in the 'Proxy server' section.

Service Account is LocalSystem

If the Service Account is the account LocalSystem, it will not be possible to log in as that user.
Documented below are two methods that can be used to configure the proxy settings for the LocalSystem account.

Method 1: Use PsExec to Configure Internet Options as LocalSystem
  1. Download PsExec from Microsoft's website: https://learn.microsoft.com/en-us/sysinternals/downloads/psexec.
  2. Open the zip and place PsExec.exe in a location that is convenient to access from a command line. (C:\temp\)
  3. Open an Administrative Console (Command Prompt or PowerShell).
  4. Change to the folder where you placed PsExec.exe in Step 2.
  5. Run the following command to launch a Command Prompt as LocalSystem:
PsExec.exe -s -i cmd.exe
  1. In the new command prompt window that appears, open Internet Options by running the command:
inetcpl.cpl
  1. In the Internet Options window that opens, switch to the Connections tab.
  2. Click 'LAN settings'.
  3. Configure the Proxy settings in the 'Proxy server' section.
    Be sure to include all proxy settings you want the LocalSystem to use, including bypasses and exclusions.
Method 2: Copy Proxy Connection Settings From Current User to LocalSystem
  1. Configure the proxy settings for the current user.
    1. Open Internet Options (inetcpl.cpl)
    2. Switch to the Connections tab.
    3. Click 'LAN settings'.
    4. Configure the Proxy settings in the 'Proxy server' section.
      Note: The settings you configure will be duplicated to the LocalSystem account, so be sure to include all settings you want the LocalSystem to use, including bypasses and exclusions.
  2. Open an Administrative PowerShell console.
  3. Run the following command to copy the DefaultConnectionSettings from the current user's settings to the setting used by the LocalSystem account:
Copy-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections" -Name "DefaultConnectionSettings" -Destination "Registry::HKEY_USERS\S-1-5-18\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections"
Configure the System-Wide Environment Variables (VBR 13+)
Three environment variables are used by .NET Core-based Veeam Backup & Replication 13+ components:
Variable Purpose
HTTP_PROXY Proxy used for HTTP requests.
HTTPS_PROXY Proxy used for HTTPS requests.
Most relevant for Veeam Backup & Replication, since traffic to public clouds is HTTPS.
NO_PROXY A comma-separated list of hosts to exclude from proxying.
Swipe to show more of the table

Each proxy variable is a URL that includes the scheme used to reach the proxy itself (normally http), for example http://proxy.domain.tld:8080. The scheme refers to how the proxy is contacted, not to the target, so an HTTPS target reached through a standard proxy still uses HTTPS_PROXY=http://proxy.domain.tld:8080.

Set the variables machine-wide (not per user) so the Veeam services can read them. Environment variables are read only when a process starts, so the services must be restarted (or the server rebooted) afterward.

Set $ProxyUrl and $NoProxy at the top of the script below for your environment, then run it in an elevated PowerShell terminal:

# Run in an elevated PowerShell console. Set these two values for your environment first.
$ProxyUrl = "http://proxy.domain.tld:8080"
$NoProxy  = "localhost,127.0.0.1,[::1],vbr01,vbr01.domain.tld,10.0.0.10,domain.tld,.domain.tld"

# Apply the variables machine-wide
[Environment]::SetEnvironmentVariable("HTTPS_PROXY", $ProxyUrl, "Machine")
[Environment]::SetEnvironmentVariable("HTTP_PROXY",  $ProxyUrl, "Machine")
[Environment]::SetEnvironmentVariable("NO_PROXY",    $NoProxy,  "Machine")

# Restart the Veeam services so they read the new variables
Get-Service veeam* | Restart-Service -Force
NO_PROXY — Considerations and Limitations

Traffic between Veeam Backup & Replication components, on the backup server itself and on other internal servers, must not be sent to the proxy. Entries must be configured within the NO_PROXY variable:

  • Comma-separated, with no spaces between entries.
  • Wildcards are not accepted (unlike the WinHTTP bypass-list).
  • A leading dot matches subdomains but not the apex domain, so list both forms:
    • domain.tld
    • .domain.tld
  • Exact IP addresses must be used. (CIDR ranges are not supported.)
  • IPv6 literals must be bracketed: use [::1], not ::1.
  • Exclude the backup server itself, or local inter-service traffic will be sent to the proxy and fail. Include at a minimum localhost, 127.0.0.1, and [::1]; the server's short hostname and FQDN; the server's IP address(es); and your internal domains.

Extend NO_PROXY with any other internal endpoints the server must reach directly, such as remote Veeam Backup & Replication servers you manage from this console, remote mount servers, backup proxies, and repositories.

Verify

Confirm the variables are set at machine scope, then retry the operation that previously failed (for example, a Veeam Vault repository rescan or a license update):

[Environment]::GetEnvironmentVariable("HTTP_PROXY", "Machine")
[Environment]::GetEnvironmentVariable("HTTPS_PROXY", "Machine")
[Environment]::GetEnvironmentVariable("NO_PROXY", "Machine")

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.

]]> <![CDATA[Veeam Backup for Microsoft 365 Upgrade Paths]]> https://www.veeam.com/kb4098 2026-09-18T00:00:00Z 2026-09-18T00:00:00Z

Veeam Backup for Microsoft 365 Upgrade Paths

KB ID: 4098
Product: Veeam Backup for Microsoft 365 | 8 | 8.1 | 8.2 | 8.3 | 8.4 | 8.5 | 8.6
Published: 2021-02-09
Last Modified: 2026-09-18
Shared Server with Veeam Backup & Replication

If Veeam Backup & Replication is installed on the same server as Veeam Backup for Microsoft 365, upgrade Veeam Backup for Microsoft 365 before upgrading Veeam Backup & Replication.

Shared Server Compatibility of Veeam Backup for Microsoft 365 and Veeam Backup & Replication

Purpose

This article documents the upgrade path to be taken to get to the most recent version of Veeam Backup for Microsoft 365.

Solution

Consider the following when planning for an upgrade:

  • All backup jobs are stopped during the upgrade process.
  • After the upgrade, backup jobs settings and global configuration options (e.g., notifications and file exclusions) will be preserved.
  • After the upgrade, Repositories, Proxy Servers, and Proxy Pools may require manual interaction to upgrade.
  • Veeam Explorers must be upgraded along with Veeam Backup for Microsoft 365.
End of Support Upgrade Path

If you are using a version of Veeam Backup for Microsoft 365 (VB365) that has reached its End of Support (EOS) and cannot be directly upgraded to a supported version, you will need to install a new instance of VB365 using the latest VB365 version.

Clarification: If the Upgrade Instructions in the User Guide for a currently supported version of VB365 include an upgrade path from an older, unsupported version, this upgrade pathway is still considered supported. This article provides details on upgrade processes for such situations, provided that a currently supported version of VB365 supports a direct upgrade from these older versions.

For example:

  • When VB365 versions 7 and 7a were supported, they provided an upgrade path from VB365 versions 5 and 6. However, VB365 version 8 does not support upgrading directly from those versions. As a result, after VB365 versions 7 and 7a reached EOS, the upgrade paths for VB365 versions 5 and 6 were removed from this document.
  • VB365 version 8.4, which is currently supported, allows upgrading directly from VB365 versions 7 and 7a. Thus, although VB365 7 and 7a are no longer supported themselves, the upgrade details for 7 and 7a are included in this document because an upgrade to VB365 8.4 from those versions is officially supported.

7 to 8.6

Path: 7 (7.0.x) → 8.4 → 8.6
  1. Upgrade to Veeam Backup for Microsoft 365 8.4
  2. Upgrade Proxies and Repositories
  3. Upgrade to Veeam Backup for Microsoft 365 8.6
  4. Review the "What You Do After Upgrade" section of the user guide.

7a to 8.6

Path: 7a (7.1.x) → 8.4 → 8.6
  1. Upgrade to Veeam Backup for Microsoft 365 8.4
  2. Upgrade Proxies and Repositories
  3. Upgrade to Veeam Backup for Microsoft 365 8.6
  4. Review the "What You Do After Upgrade" section of the user guide.

8.0 to 8.6

Path: 8.0 (8.0.x) → 8.6
  1. Upgrade to Veeam Backup for Microsoft 365 8.6
  2. Review the "What You Do After Upgrade" section of the user guide.

8.1 to 8.6

Path: 8.1 (8.1.x) → 8.6
  1. Upgrade to Veeam Backup for Microsoft 365 8.6
  2. Review the "What You Do After Upgrade" section of the user guide.

8.2 to 8.6

Path: 8.2 (8.2.x) → 8.6
  1. Upgrade to Veeam Backup for Microsoft 365 8.6
  2. Review the "What You Do After Upgrade" section of the user guide.

8.3 to 8.6

Path: 8.3 (8.3.x) → 8.6
  1. Upgrade to Veeam Backup for Microsoft 365 8.6
  2. Review the "What You Do After Upgrade" section of the user guide.

8.4 to 8.6

Path: 8.4 (8.4.x) → 8.6
  1. Upgrade to Veeam Backup for Microsoft 365 8.6
  2. Review the "What You Do After Upgrade" section of the user guide.

8.5 to 8.6

Path: 8.5 (8.5.x) → 8.6
  1. Upgrade to Veeam Backup for Microsoft 365 8.6
  2. Review the "What You Do After Upgrade" section of the user guide.
What You Do After Upgrade
After upgrading Veeam Backup for Microsoft 365, be sure to review the "What You Do After Upgrade" section of the user guide.

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.

]]> <![CDATA[Veeam Agent for Linux - veeamsnap and blksnap Extended Linux Distribution Support]]> https://www.veeam.com/kb2804 2026-09-18T00:00:00Z 2026-09-18T00:00:00Z

Veeam Agent for Linux - veeamsnap and blksnap Extended Linux Distribution Support

KB ID: 2804
Product: Veeam Agent for Linux | 6.3.2 | 13.1
Published: 2018-11-29
Last Modified: 2026-09-18

This article provides supplementary information regarding the compatibility of the veeamsnap and blksnap kernel modules with various Linux distributions and kernel versions. It specifically addresses distributions and versions that are not explicitly listed in the System Requirements for Veeam Agent for Linux.

Important Note:
The absence of a Linux distribution or version from the tables in this article does not indicate that it is unsupported or supported. This article exists solely to provide more granular kernel compatibility information for reference purposes. For determining supported platforms, always refer to the Veeam Agent for Linux User Guide.

The veeamsnap and blksnap kernel modules are used for Volume-Level Backup (excluding btrfs volumes) and File-level Backup (excluding Snapshot-Less File-Level Backup).

For more information, review the following:
Veeam Agent for Linux - Considerations and Limitations

Veeam Agent for Linux 13.1.1

blksnap kernel module

In addition to the veeamsnap kernel module, Veeam Agent for Linux 6 introduced the blksnap kernel module for use on newer Linux kernels. Both modules are used for the same purpose: snapshot creation.

  • Veeamsnap module is supported up to Linux kernel 5.18
  • The Blksnap module is supported for Linux kernels starting from 5.10

The default installed module is listed in the Details column for each supported distribution and version.

Version Max Supported Kernel VAL Build Shipped with VBR Build
Red Hat Enterprise Linux (RHEL) / Rocky / AlmaOnly Rocky/Alma 8.10 and 9.4 or higher are supported.
10.0-10.2 6.12.0-211.56.1.el10_2 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the blksnap kernel module.
9.0-9.8 5.14.0-687.49.1.el9_8 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the blksnap kernel module.
8.4-8.10 4.18.0-553.164.1.el8_10 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the veeamsnap kernel module.
7.9 ELS
RHEL Only		 3.10.0-1160.159.1.el7 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the veeamsnap kernel module.
Oracle Linux
10.0-10.2
(RHCK)		 6.12.0-211.56.1.el10_2 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the blksnap kernel module.
10.0-10.1
(UEK8)		 6.12.0-206.104.4.4.el10uek 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the blksnap kernel module.
9.0-9.8
(RHCK)		 5.14.0-687.49.1.el9_8 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the blksnap kernel module.
9.5-9.7
(UEK8)		 6.12.0-206.104.4.4.el9uek 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the blksnap kernel module.

Note: Building the veeamblksnap kernel module on Oracle Linux 9 with UEK R8 kernel requires additional steps. For more information, refer to KB4732
9.0-9.7
(UEK7)		 5.15.0-324.217.5.3.el9uek 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the blksnap kernel module.
8.0-8.10
(RHCK)		 4.18.0-553.164.1.el8_10 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the veeamsnap kernel module.
8.5-8.10
(UEK7)		 5.15.0-324.217.5.3.el8uek 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the veeamsnap kernel module.

Note: Building the veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information, refer to KB4394
8.1-8.10
(UEK6)		 5.4.17-2136.359.3.2.el8uek 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the veeamsnap kernel module.
7.7-7.9
(UEK6)		 5.4.17-2136.338.4.2.el7uek 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the veeamsnap kernel module.
7.5-7.9
(UEK5)		 4.14.35-2047.542.2.el7uek 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the veeamsnap kernel module.
7.1-7.9
(UEK4)		 4.1.12-124.93.1.el7uek 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
16.0 6.12.0-160000.37 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the blksnap kernel module.
15 SP7 6.4.0-150700.53.81 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the blksnap kernel module.
15 SP6 6.4.0-150600.23.130 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the blksnap kernel module.
15 SP5 5.14.21-150500.55.182 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the blksnap kernel module.
15 SP4 5.14.21-150400.24.235 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the blksnap kernel module.
15 SP3 5.3.18-150300.59.229 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the blksnap kernel module.
12 SP5 4.12.14-122.323 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the veeamsnap kernel module.
Ubuntu
26.04 7.0.0-15 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the blksnap kernel module.
24.04 6.8.0-138 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the blksnap kernel module.
22.04 5.15.0-190 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the blksnap kernel module.
Debian
13.5 6.12.105-deb13 13.1.1.4

Veeam Backup & Replication 13.1.1.18

Uses the blksnap kernel module.
Swipe to show more of the table

Veeam Agent for Linux 6.3.2

blksnap kernel module

In addition to the veeamsnap kernel module, Veeam Agent for Linux 6 introduced the blksnap kernel module for use on newer Linux kernels. Both modules are used for the same purpose (snapshot creation).

  • Veeamsnap module is supported up to Linux kernel 5.18
  • The Blksnap module is supported for Linux kernels starting from 5.10

The default installed module is listed in the Details column for each supported distribution and version.

Version Maximum Supported Kernel VAL Build Shipped with VBR Build
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported. / Rocky / AlmaOnly Rocky/Alma 8.10 and 9.3 or higher are supported.
10.0-10.2 6.12.0-211.56.1.el10_2 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
9.0-9.8 5.14.0-687.49.1.el9_8 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
8.0-8.10 4.18.0-553.164.1.el8_10 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the veeamsnap kernel module.
7.0-7.9 3.10.0-1160.159.1.el7 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the veeamsnap kernel module.
6.4-6.10 2.6.32-754.53.1 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the veeamsnap kernel module.

Please note that RHEL6 reached "End of life," and the EPEL repository has archived the version 6 packages. If you are looking for the dkms package (a VAL prerequisite), check: https://archives.fedoraproject.org/pub/archive/epel/6/

See also: https://access.redhat.com/discussions/4768501.
Oracle Linux

10.0-10.2
(RHCK)		 6.12.0-211.56.1.el10_2 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.

10.0-10.1
(UEK8)		 6.12.0-206.104.4.4.el10uek 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
9.0-9.8
(RHCK)		 5.14.0-687.49.1.el9_8 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
9.5-9.7
(UEK8)		 6.12.0-206.104.4.4.el9uek 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.

Note: Building the veeamsnap kernel module on Oracle Linux 9 with UEK R8 kernel requires additional steps. For more information, refer to KB4732
9.0-9.7
(UEK7)		 5.15.0-324.217.5.3.el9uek 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
8.0-8.10
(RHCK)		 4.18.0-553.164.1.el8_10 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the veeamsnap kernel module.
8.5-8.10
(UEK7)		 5.15.0-324.217.5.3.el8uek 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the veeamsnap kernel module.

Note: Building the veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information, refer to KB4394
8.1-8.10
(UEK6)		 5.4.17-2136.359.3.2.el8uek 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the veeamsnap kernel module.
7.0-7.9
(RHCK)		 3.10.0-1160.156.1.el7 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the veeamsnap kernel module.
7.7-7.9
(UEK6)		 5.4.17-2136.338.4.2.el7uek 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the veeamsnap kernel module.
7.5-7.9
(UEK5)		 4.14.35-2047.542.2.el7uek 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the veeamsnap kernel module.
7.1-7.9
(UEK4)		 4.1.12-124.93.1.el7uek 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the veeamsnap kernel module.
6.4-6.10
(RHCK)		 2.6.32-754.35.1.el6 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the veeamsnap kernel module.
6.8-6.10
(UEK4)		 4.1.12-124.16.4 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
16 6.12.0-160000.37 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
15 SP7 6.4.0-150700.53.81 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
15 SP6 6.4.0-150600.23.130 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
15 SP5 5.14.21-150500.55.182 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
15 SP4 5.14.21-150400.24.235 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
15 SP3 5.3.18-150300.59.229 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
15 SP2 5.3.18-24.96.1 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the veeamsnap kernel module.
12 SP5 4.12.14-122.323 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the veeamsnap kernel module.
12 SP4 4.12.14-122.320 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the veeamsnap kernel module.
openSUSE
Leap 16.0 6.12.0-160000.37 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
Leap 15.6 6.4.0-150600.23.103 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
Leap 15.5 5.14.21-150500.55.83 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
Leap 15.4 5.14.21-150400.24.100 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
Leap 15.3 5.3.18-150300.59.106 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
Tumbleweed 6.14.6-2 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the veeamsnap kernel module.
Ubuntu
25.04 6.14.0-36 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
24.10 6.11.0-26 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
24.04 6.8.0-138 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
22.04 5.15.0-190 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
Debian
13.5 6.12.105-deb13 6.3.2.1405

Veeam Backup & Replication 12.3.2.4854

Uses the blksnap kernel module.
Swipe to show more of the table

Veeam Agent for Linux 6.3.1

blksnap kernel module

In addition to the veeamsnap kernel module, Veeam Agent for Linux 6 introduced the blksnap kernel module for use on newer Linux kernels. Both modules are used for the same purpose (snapshot creation).

  • Veeamsnap module is supported up to Linux kernel 5.18
  • The Blksnap module is supported for Linux kernels starting from 5.10

The default installed module is listed in the Details column for each supported distribution and version.

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported. / Rocky / AlmaOnly Rocky/Alma 8.10 and 9.3 or higher are supported.
9.6 5.14.0-570.60.1.el9_6 6.3.1.1016

This kernel is supported using a patch available from:
My Account portal > Product updates
This kernel module patch for VAL 6.3.1.1016 adds support for kernels between 5.14.0-570.12.1.el9_6 and the kernel listed in this row.

Kernel module patch install instructions.

For assistance, please create a support case.

Uses the blksnap kernel module.
9.0-9.5 5.14.0-503.35.1.el9_5 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.10 4.18.0-553.92.1.el8_10 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.0-7.9 3.10.0-1160.144.1.el7 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.4-6.10 2.6.32-754.53.1 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.

Please note that RHEL6 reached "End of life," and therefore EPEL repository has archived version 6 packages. If you are looking for the dkms package (a VAL prerequisite), check: https://archives.fedoraproject.org/pub/archive/epel/6/

See also: https://access.redhat.com/discussions/4768501.
Oracle Linux
9.0-9.5
(RHCK)		 5.14.0-503.35.1.el9_5 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.5-9.6
(UEK8)		 6.12.0-106.55.4.2.el9uek 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.0-9.5
(UEK7)		 5.15.0-315.196.5.2.el9uek 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.10
(RHCK)		 4.18.0-553.71.1.el8_10 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.5-8.10
(UEK7)		 5.15.0-316.196.4.1.el8uek 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.

Note: Building the veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information, refer to KB4394
8.1-8.10
(UEK6)		 5.4.17-2136.351.3.1.el8uek 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.7-7.9
(UEK6)		 5.4.17-2136.338.4.2.el7uek 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.5-7.9
(UEK5)		 4.14.35-2047.542.2.el7uek 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.1-7.9
(UEK4)		 4.1.12-124.93.1.el7uek 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.8-6.10
(UEK4)		 4.1.12-124.16.4 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
15 SP6 6.4.0-150600.23.81 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP5 5.14.21-150500.55.127 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP4 5.14.21-150400.24.187 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP3 5.3.18-150300.59.229 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP2 5.3.18-24.96.1 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP5 4.12.14-122.275 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP4 4.12.14-95.54.1 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
openSUSE
Leap 15.6 6.4.0-150600.23.81 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Leap 15.5 5.14.21-150500.55.83 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Leap 15.4 5.14.21-150400.24.100 6.3.1.1016

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Leap 15.3 5.3.18-150300.59.106 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Tumbleweed 6.13.6-1 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Ubuntu
24.10 6.11.0-26 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
24.04 6.8.0-90 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
22.04 5.15.0-164 6.3.1.1016

6.3.1.1016 initially shipped with Backup & Replication 12.3.1.1139

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Swipe to show more of the table

Veeam Agent for Linux 6.3

blksnap kernel module

In addition to the veeamsnap kernel module, Veeam Agent for Linux 6 introduced the blksnap kernel module for use on newer Linux kernels. Both modules are used for the same purpose (snapshot creation).

  • Veeamsnap module is supported up to Linux kernel 5.18
  • The Blksnap module is supported for Linux kernels starting from 5.10

The default installed module is listed in the Details column for each supported distribution and version.

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported. / Rocky / AlmaOnly Rocky/Alma 8.10 and 9.3 or higher are supported.
9.0-9.5 5.14.0-503.35.1.el9_5 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.10 4.18.0-553.92.1.el8_10 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.0-7.9 3.10.0-1160.144.1.el7 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.4-6.10 2.6.32-754.53.1 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.

Please note that RHEL6 reached "End of life," and therefore EPEL repository has archived version 6 packages. If you are looking for the dkms package (a VAL prerequisite), check: https://archives.fedoraproject.org/pub/archive/epel/6/

See also: https://access.redhat.com/discussions/4768501.
Oracle Linux
9.0-9.5
(RHCK)		 5.14.0-503.35.1.el9_5 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.5-9.6
(UEK8)		 6.12.0-102.36.5.2.el9uek 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.0-9.5
(UEK7)		 5.15.0-314.193.5.3.el9uek 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.10
(RHCK)		 4.18.0-553.71.1.el8_10 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.5-8.10
(UEK7)		 5.15.0-316.196.4.1.el8uek 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.

Note: Building the veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information, refer to KB4394
8.1-8.10
(UEK6)		 5.4.17-2136.351.3.1.el8uek 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.7-7.9
(UEK6)		 5.4.17-2136.337.5.1 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.5-7.9
(UEK5)		 4.14.35-2047.542.2 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.1-7.9
(UEK4)		 4.1.12-124.48.6 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.8-6.10
(UEK4)		 4.1.12-124.16.4 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
15 SP6 6.4.0-150600.23.81 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP5 5.14.21-150500.55.130 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP4 5.14.21-150400.24.187 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP3 5.3.18-150300.59.229 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP2 5.3.18-24.96.1 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP5 4.12.14-122.275 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP4 4.12.14-95.54.1 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
openSUSE
Leap 15.6 6.4.0-150600.23.81 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Leap 15.5 5.14.21-150500.55.83 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Leap 15.4 5.14.21-150400.24.100 6.3.0.73

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Leap 15.3 5.3.18-150300.59.106 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Tumbleweed 6.13.0-1 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Ubuntu
24.10 6.11.0-26 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
24.04 6.8.0-90 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
22.04 5.15.0-164 6.3.0.73

6.3.0.73 initially shipped with Backup & Replication 12.3.0.310

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Swipe to show more of the table

Veeam Agent for Linux 6.2

blksnap kernel module

In addition to the veeamsnap kernel module, Veeam Agent for Linux 6 introduced the blksnap kernel module for use on newer Linux kernels. Both modules are used for the same purpose (snapshot creation).

  • Veeamsnap module is supported up to Linux kernel 5.18
  • The Blksnap module is supported for Linux kernels starting from 5.10

The default installed module is listed in the Details column for each supported distribution and version.

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported. / Rocky / AlmaOnly Rocky/Alma 9.3 and higher are supported.
9.5 5.14.0-503.35.1.el9_5 6.2.0.101

This kernel is supported using a patch available from Veeam Support.
Please create a support case to request it.

Uses the blksnap kernel module.
9.0-9.4 5.14.0-427.42.1.el9_4 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.10 4.18.0-553.92.1.el8_10 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.0-7.9 3.10.0-1160.144.1.el7 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.4-6.10 2.6.32-754.53.1 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.

Please note that RHEL6 reached "End of life," and therefore EPEL repository has archived version 6 packages. If you are looking for the dkms package (a VAL prerequisite), check: https://archives.fedoraproject.org/pub/archive/epel/6/

See also: https://access.redhat.com/discussions/4768501.
Oracle Linux
9.0-9.4
(RHCK)		 5.14.0-427.42.1.el9_4 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.5-9.6
(UEK8)		 6.12.0-102.36.5.2.el9uek 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.0-9.4
(UEK7)		 5.15.0-314.193.5.3.el9uek 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.10
(RHCK)		 4.18.0-553.71.1.el8_10 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.5-8.10
(UEK7)		 5.15.0-316.196.4.1.el8uek 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.

Note: Building the veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information, refer to KB4394
8.1-8.10
(UEK6)		 5.4.17-2136.351.3.1.el8uek 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.7-7.9
(UEK6)		 5.4.17-2136.338.4.2.el7uek 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.5-7.9
(UEK5)		 4.14.35-2047.542.2.el7uek 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.1-7.9
(UEK4)		 4.1.12-124.93.1.el7uek 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.8-6.10
(UEK4)		 4.1.12-124.16.4 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
15 SP6 6.4.0-150600.23.81 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP5 5.14.21-150500.55.130 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP4 5.14.21-150400.24.187 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP3 5.3.18-150300.59.229 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP2 5.3.18-24.96.1 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP5 4.12.14-122.275 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP4 4.12.14-95.54.1 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
openSUSE
Leap 15.6 6.4.0-150600.23.81 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Leap 15.5 5.14.21-150500.55.83 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Leap 15.4 5.14.21-150400.24.100 6.2.0.101

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Leap 15.3 5.3.18-150300.59.106 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Tumbleweed 6.11.8-1 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Ubuntu
24.10 6.11.0-26 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
24.04 6.8.0-90 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
22.04 5.15.0-164 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Swipe to show more of the table

Veeam Agent for Linux 6.1.2

New Distribution Support

Veeam Agent for Linux 6.1.2 introduces support for the following Linux Distributions:

blksnap kernel module

In addition to the veeamsnap kernel module, Veeam Agent for Linux 6 introduced the blksnap kernel module for use on newer Linux kernels. Both modules are used for the same purpose (snapshot creation).

  • Veeamsnap module is supported up to Linux kernel 5.18
  • The Blksnap module is supported for Linux kernels starting from 5.10

The default installed module is listed in the Details column for each supported distribution and version.

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported. / Rocky / AlmaOnly Rocky/Alma 9.3 and higher are supported.
9.0-9.4 5.14.0-427.42.1.el9_4 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.10 4.18.0-553.92.1.el8_10 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.0-7.9 3.10.0-1160.144.1.el7 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.4-6.10 2.6.32-754.53.1 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.

Please note that RHEL6 reached "End of life," and therefore EPEL repository has archived version 6 packages. If you are looking for the dkms package (a VAL prerequisite), check: https://archives.fedoraproject.org/pub/archive/epel/6/

See also: https://access.redhat.com/discussions/4768501.
Oracle Linux
9.0-9.4
(RHCK)		 5.14.0-427.31.1.el9_4 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.5-9.6
(UEK8)		 6.12.0-102.36.5.2.el9uek 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.0-9.5
(UEK7)		 5.15.0-314.193.5.3.el9uek 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.10
(RHCK)		 4.18.0-553.71.1.el8_10 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.5-8.10
(UEK7)		 5.15.0-316.196.4.1.el8uek 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.

Note: Building the veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information, refer to KB4394
8.1-8.10
(UEK6)		 5.4.17-2136.351.3.1.el8uek 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.7-7.9
(UEK6)		 5.4.17-2136.334.6.1 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.5-7.9
(UEK5)		 4.14.35-1902.300.11 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.1-7.9
(UEK4)		 4.1.12-112.16.4 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.8-6.10
(UEK4)		 4.1.12-124.16.4 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
15 SP5 5.14.21-150500.55.130 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
15 SP4 5.14.21-150400.24.187 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
15 SP3 5.3.18-150300.59.229 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP2 5.3.18-24.96.1 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP5 4.12.14-122.275 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP4 4.12.14-95.54.1 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
openSUSE
Leap 15.5 5.14.21-150500.55.73 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Leap 15.4 5.14.21-150400.24.100 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Leap 15.3 5.3.18-150300.59.106 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Tumbleweed 6.8.9-1 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Ubuntu
24.04 6.8.0-90 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
22.04 5.15.0-164 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Swipe to show more of the table

Veeam Agent for Linux 6.1

blksnap kernel module

In addition to the veeamsnap kernel module, Veeam Agent for Linux 6 introduced the blksnap kernel module for use on newer Linux kernels. Both modules are used for the same purpose (snapshot creation).

  • Veeamsnap module is supported up to Linux kernel 5.18
  • The Blksnap module is supported for Linux kernels starting from 5.10

The default installed module is listed in the Details column for each supported distribution and version.

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported.
9.3-9.4 5.14.0-427.20.1.el9_4 6.1.0.1498 This kernel is supported using a patch available from Veeam Support.
Please create a support case to request it.

Uses the blksnap kernel module.
9.0-9.3 5.14.0-362.13.1.el9_3 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.10 4.18.0-553.5.1.el8_10 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.0-7.9 3.10.0-1160.118.1.el7 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.4-6.10 2.6.32-754.53.1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.

Please note that RHEL6 reached "End of life," and therefore EPEL repository has archived version 6 packages. If you are looking for the dkms package (a VAL prerequisite), check: https://archives.fedoraproject.org/pub/archive/epel/6/

See also: https://access.redhat.com/discussions/4768501.
Oracle Linux
9.0-9.3
(RHCK)		 5.14.0-362.13.1.el9_3 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.0-9.3
(UEK7)		 5.15.0-205.149.5.1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.8
(RHCK)		 4.18.0-513.9.1.el8_9 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.5-8.9
(UEK7)		 5.15.0-205.149.5.1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.

Note: Building the veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information, refer to KB4394
8.1-8.9
(UEK6)		 5.4.17-2136.330.7.1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.7-7.9
(UEK6)		 5.4.17-2136.330.7.1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.5-7.9
(UEK5)		 4.14.35-1902.300.11 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.1-7.9
(UEK4)		 4.1.12-112.16.4 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.8-6.10
(UEK4)		 4.1.12-124.16.4 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
15 SP5 5.14.21-150500.55.52 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
15 SP4 5.14.21-150400.24.100 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
15 SP3 5.3.18-150300.59.106.1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP2 5.3.18-24.96.1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP5 4.12.14-122.201 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP4 4.12.14-95.54.1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
openSUSE
Leap 15.5 5.14.21-150500.55.52 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Leap 15.4 5.14.21-150400.24.100 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Leap 15.3 5.3.18-150300.59.106 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Tumbleweed 6.7.2-1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Ubuntu
22.04 5.15.0-126 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Swipe to show more of the table

Veeam Agent for Linux 6.0.3

blksnap kernel module

In addition to the veeamsnap kernel module, Veeam Agent for Linux 6 introduced the blksnap kernel module for use on newer Linux kernels. Both modules are used for the same purpose (snapshot creation).

  • Veeamsnap module is supported up to Linux kernel 5.18
  • The Blksnap module is supported for Linux kernels starting from 5.10

The default installed module is listed in the Details column for each supported distribution and version.

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported.
9.3 5.14.0-362.13.1.el9_3 6.0.3.1228

To acquire Veeam Agent for Linux 6.0.3.1228 packages and instructions, please open a support ticket.

 

Uses the blksnap kernel module.
9.0-9.2 5.14.0-284.25.1.el9_2 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.9 4.18.0-513.11.1.el8_9 6.0.3.1228

To acquire Veeam Agent for Linux 6.0.3.1228 packages and instructions, please open a support ticket.

 

Uses the blksnap kernel module.
8.0-8.8 4.18.0-477.21.1.el8_8 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.0-7.9 3.10.0-1160.108.1.el7 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.0-6.10 2.6.32-754.50.1.el6 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
Please note that RHEL6 reached "End of life," and therefore EPEL repository has archived version 6 packages. If you are looking for a dkms package (VAL prerequisite), check: https://archives.fedoraproject.org/pub/archive/epel/6/

See also: https://access.redhat.com/discussions/4768501.
Oracle Linux
9.0-9.2
(RHCK)		 5.14.0-284.25.1.el9_2 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.0-9.2
(UEK7)		 5.15.0-202.135.2 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.8
(RHCK)		 4.18.0-477.21.1.el8_8 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.0-8.7
(UEK6)		 5.4.17-2136.327.2 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.0-8.8
(UEK7)		 5.15.0-202.135.2 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
Note: Building the veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information, refer to KB4394
7.0-7.9
(UEK6)		 5.4.17-2136.327.2 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
15 SP5 5.14.21-150500.55.44 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

 

Also available at repository.veeam.com
Recovery media


Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
15 SP4 5.14.21-150400.24.100 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
15 SP3 5.3.18-150300.59.106.1 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP2 5.3.18-24.96.1 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP5 4.12.14-122.189 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com
Recovery media

 

Uses the veeamsnap kernel module.
12 SP4 4.12.14-95.54.1 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
openSUSE
Leap 15.5 5.14.21-150500.55.44 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

 

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Leap 15.4 5.14.21-150400.24.100 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Leap 15.3 5.3.18-150300.59.106 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Tumbleweed 6.2.10-1 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Ubuntu
22.04 5.15.0-126 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Swipe to show more of the table

Veeam Agent for Linux 6.0.2

blksnap kernel module

In addition to the veeamsnap kernel module, Veeam Agent for Linux 6 introduces the blksnap kernel module for use on newer Linux kernels. Both modules are used for the same purpose (snapshot creation).

  • Veeamsnap module is supported up to Linux kernel 5.18
  • The Blksnap module is supported for Linux kernels starting from 5.10

The default installed module is listed in the Details column for each supported distribution and version.

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported.
9.0-9.2 5.14.0-284.25.1.el9_2 6.0.2.1173 To acquire Veeam Agent for Linux 6.0.2.1173 packages and instructions, please open a support ticket.

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.8 4.18.0-477.21.1.el8_8 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.0-7.9 3.10.0-1160.108.1.el7 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.0-6.10 2.6.32-754.50.1.el6 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
Please note that RHEL6 reached "End of life," and therefore EPEL repository has archived version 6 packages. If you are looking for a dkms package (VAL prerequisite), check: https://archives.fedoraproject.org/pub/archive/epel/6/

See also: https://access.redhat.com/discussions/4768501.
Oracle Linux
9.0-9.2
(RHCK)		 5.14.0-284.25.1.el9_2 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412 .

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.0-9.1
(UEK7)		 5.15.0-100.96.32.el9uek 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.8
(RHCK)		 4.18.0-477.21.1.el8_8 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.0-8.7
(UEK6)		 5.4.17-2136.327.2 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.0-8.8
(UEK7)		 5.15.0-202.135.2 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
Note: Building the veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information, refer to KB4394
7.0-7.9
(UEK6)		 5.4.17-2136.327.2 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
15 SP4 5.14.21-150400.24.100 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
15 SP3 5.3.18-150300.59.106.1 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP2 5.3.18-24.96.1 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP5 4.12.14-122.189 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP4 4.12.14-95.54.1 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
openSUSE
Leap 15.4 5.14.21-150400.24.100 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Leap 15.3 5.3.18-150300.59.106 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Tumbleweed 6.2.10-1 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Ubuntu
22.04 5.15.0-126 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Swipe to show more of the table

Veeam Agent for Linux 6.0

blksnap kernel module

In addition to the veeamsnap kernel module, Veeam Agent for Linux 6 introduces the blksnap kernel module for use on newer Linux kernels. Both modules are used for the same purpose (snapshot creation).

  • Veeamsnap module is supported up to Linux kernel 5.18
  • The Blksnap module is supported for Linux kernels starting from 5.10

The default installed module is listed in the Details column for each supported distribution and version.

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported.
9.0-9.1 5.14.0-162.12.1.el9_1 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.8 4.18.0-477.21.1.el8_8 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.0-7.9 3.10.0-1160.108.1.el7 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.0-6.10 2.6.32-754.50.1.el6 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
Please note that RHEL6 reached "End of life" and therefore EPEL repository has archived version 6 packages. If you are looking for dkms package (VAL prerequisite), check: https://archives.fedoraproject.org/pub/archive/epel/6/

See also: https://access.redhat.com/discussions/4768501.
Oracle Linux
9.0-9.1
(RHCK)		 5.14.0-162.12.1.el9_1 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420 .

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.0-9.1
(UEK7)		 5.15.0-7.86.6.1.el9uek 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses blksnap kernel module.
8.0-8.8
(RHCK)		 4.18.0-477.21.1.el8_8 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.0-8.8
(UEK7)		 5.15.0-202.135.2 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
Note: Building veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information refer to KB4394
8.0-8.7
(UEK6)		 5.4.17-2136.327.2 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.0-7.9
(UEK6)		 5.4.17-2136.327.2 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
15 SP4 5.14.21-150400.24.100 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on available workaround, refer to KB4183
15 SP3 5.3.18-150300.59.106.1 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP2 5.3.18-24.96.1 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP5 4.12.14-122.189 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP4 4.12.14-95.54.1 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
openSUSE
Leap 15.4 5.14.21-150400.24.100 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on available workaround, refer to KB4183
Leap 15.3 5.3.18-150300.59.106 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Tumbleweed 6.1.12-1 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on available workaround, refer to KB4183
Ubuntu
22.04 5.15.0-126 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Swipe to show more of the table

End of Life Versions

All Veeam Agent for Linux builds listed below have reached End-of-Support.

The information below is retained for historical reference only.

Any customer operating a version listed below is strongly encouraged to upgrade to the latest version.

Veeam Agent for Linux 5.0.2

Intended Audience for this Update

As of March 1, 2024, Veeam Agent for Linux 5.x is no longer supported.

On March 14, 2024, a final update, Cumulative Patch P20240304, was released for Veeam Backup & Replication 11a. This update included a new build of Veeam Agent for Linux. Veeam Backup & Replication 11a, P20240304, is provided as a courtesy to customers who wish to continue using Veeam Backup & Replication 11a for an extended time.

Veeam Agent for Linux 5.0.2.4707 is only available with Veeam Backup & Replication 11a P20240304. The table below has been updated to reflect the compatibility introduced by this new version of Veeam Agent for Linux.

CRITICAL: If you choose to install 11a P20240304, you will not be able to upgrade to version 12.1 until the next minor update, 12.1.2, is available (scheduled to be released in Q2 2024).

We strongly recommend that all customers use actively supported versions of Veeam products.

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported.
9.0-9.3
 5.14.0-362.24.1.el9_3 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
8.6-8.9 4.18.0-513.18.1.el8_9 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
8.0-8.5 4.18.0-348.20.1.el8_5

5.0.2.4567

Veeam Agent for Linux 5.0.2.4567 Shipped with Backup & Replication 11.0.1.1261 P20211211.

Also available at repository.veeam.com.
Recovery media.
7.0-7.9 3.10.0-1160.114.2.el7 5.0.2.4567

Veeam Agent for Linux 5.0.2.4567 shipped with Backup & Replication 11.0.1.1261 P20211211.

Also available at repository.veeam.com.
Recovery media.
6.0-6.10 2.6.32-754.50.1.el6 5.0.2.4567

Veeam Agent for Linux 5.0.2.4567 shipped with Backup & Replication 11.0.1.1261 P20211211.

Also available at repository.veeam.com.
Recovery media.


Please note that RHEL6 reached "End of life" and therefore EPEL repository has archived version 6 packages. If you are looking for dkms package (VAL prerequisite), check 
https://archives.fedoraproject.org/pub/archive/epel/6/

See also
https://access.redhat.com/discussions/4768501.
Oracle Linux
9.0-9.3
 5.14.0-362.24.1.el9_3
(RHCK)		 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
5.15.0-204.147.6.2.el9uek
(UEK7)		 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
8.6-8.9
 4.18.0-513.18.1.el8_9
(RHCK)		 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
5.15.0-204.147.6.2.el8uek
(UEK7)		 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
5.4.17-2136.329.3.1.el8uek
(UEK6)		 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
7.0-7.9
 5.4.17-2136.329.3.1.el7uek
(UEK6)		 5.0.2.4567

Veeam Agent for Linux 5.0.2.4567 shipped with Backup & Replication 11.0.1.1261 P20211211.

Also available at repository.veeam.com.
Recovery media.
SUSE Linux Enterprise (SLES)
15 SP5 5.14.21-150500.55.52 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
15 SP4 5.14.21-150400.24.100 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
15 SP3 5.3.18-150300.59.106.1 5.0.2.4567

Veeam Agent for Linux 5.0.2.4567 shipped with Backup & Replication 11.0.1.1261 P20211211.

 

Also available at repository.veeam.com.
Recovery media.
15 SP2 5.3.18-24.96.1 5.0.2.4567

Veeam Agent for Linux 5.0.2.4567 shipped with Backup & Replication 11.0.1.1261 P20211211.

 

Also available at repository.veeam.com.
Recovery media.
12 SP5 4.12.14-122.194 5.0.2.4567

Veeam Agent for Linux 5.0.2.4567 shipped with Backup & Replication 11.0.1.1261 P20211211.

 

Also available at repository.veeam.com.
Recovery media.
openSUSE Leap
15.5 5.14.21-150500.55.52 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
15.4 5.14.21-150400.24.100 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
15.3 5.3.18-150300.59.106 5.0.2.4567

Veeam Agent for Linux 5.0.2.4567 shipped with Backup & Replication 11.0.1.1261 P20211211.

 

Also available at repository.veeam.com.
Recovery media.
Ubuntu
22.04 5.15.0-101 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
Swipe to show more of the table

Veeam Agent for Linux 5.0.1

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported.
8.0-8.4 4.18.0-305.25.1.el8_4

5.0.1.4493

Veeam Agent for Linux version 5.0.1. Shipped with Backup & Replication 11a GA.
7.0-7.9 3.10.0-1160.76.1.el7 5.0.1.4493

Veeam Agent for Linux version 5.0.1. Shipped with Backup & Replication 11a GA.
6.0-6.10 2.6.32-754.35.1.el6 5.0.1.4493 Veeam Agent for Linux version 5.0.1. Shipped with Backup & Replication 11a GA.

Please note that RHEL6 reached "End of life" and therefore EPEL repository has archived version 6 packages. If you are looking for dkms package (VAL prerequisite), check 
https://archives.fedoraproject.org/pub/archive/epel/6/

See also
https://access.redhat.com/discussions/4768501.
Swipe to show more of the table

Veeam Agent for Linux 5.0

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported.
8.4 4.18.0-305.25.1.el8_4

5.0.0.4325

Known issue: deployment via Agent Management fails.

For packages and instructions please open a support ticket.
8.0-8.3 4.18.0-240.22.1.el8_3

5.0.0.4318

Veeam Agents for Linux version 5.0. Shipped with Backup & Replication 11.0 GA.
7.0-7.9 3.10.0-1160.76.1.el7 5.0.0.4325

Known issue: deployment via Agent Management fails. 

For packages and instructions please open a support ticket.
6.0-6.10 2.6.32-754.35.1.el6 5.0.0.4318 Veeam Agents for Linux version 5.0. Shipped with Backup & Replication 11.0 GA.

Please note that RHEL6 reached "End of life" and therefore EPEL repository has archived version 6 packages. If you are looking for dkms package (VAL prerequisite), check 
https://archives.fedoraproject.org/pub/archive/epel/6/

See also
https://access.redhat.com/discussions/4768501.
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.

]]> <![CDATA[How to Identify and Repair Files That Cannot Be Opened After Restore]]> https://www.veeam.com/kb4874 2026-09-17T00:00:00Z 2026-09-17T00:00:00Z

How to Identify and Repair Files That Cannot Be Opened After Restore

KB ID: 4874
Product: Veeam Backup for Microsoft 365 | 8
Published: 2026-06-29
Last Modified: 2026-09-17
Updated for Veeam Backup for Microsoft 365 8.6

This article has been updated to document new Integrity Check capabilities included with Veeam Backup for Microsoft 365 8.6. The integrity check can now process JET-based repositories and immutable repositories.

Customers who ran an Integrity Check while running Veeam Backup for Microsoft 365 8.5, are advised to upgrade to version 8.6 and run the Integrity Check again.

Purpose

This article provides steps to identify and repair SharePoint, OneDrive, Teams files, and list attachments that were backed up with corrupted content due to the issue described in KB4835.

Solution

Before You Begin

Ensure you’re running Veeam Backup for Microsoft 365 version 8.5 or later before proceeding.

When the Integrity Check is performed on an object storage repository, there will be a temporary increase in the number of API calls the storage system handles while previously written files are scanned for inconsistencies. The redownloading of affected files afterward also increases storage usage on that same repository.

Repair Procedure

The following steps are to be completed for each repository that contains SharePoint, OneDrive, and Teams files. The steps in this section use PowerShell commands that reference variables defined in one step and used in later steps, so all 5 steps should be completed sequentially for each repository.

  • In Veeam Backup for Microsoft 365 8.5, this procedure only supports non-immutable object storage repositories.
  • In version 8.6 and later, support for immutable object storage repositories and JET-based repositories was added.
Step 1: Run an Integrity Check
  1. Open Veeam Backup for Microsoft 365.
  2. In the main menu ( ☰ ), expand Console, and select PowerShell.
    Note: Launching PowerShell from outside Veeam Backup for Microsoft 365 may require manual loading of PowerShell modules.
  3. In the PowerShell console, run the following command to import the module used by this article:
    This DLL module must be loaded directly to ensure the Start-VBORepositoryRepairSession cmdlet is available.
Import-Module "C:\Program Files\Veeam\Backup365\Veeam.Archiver.PowerShell.dll"
  1. Run the following cmdlet for the repository being investigated:
$repository = Get-VBORepository -Name "Repository Name"
Test-VBORepository -Repository $repository
Step 2: Review the Results

If the Test-VBORepository output contains any of the following messages, proceed to Step 3:

For Veeam Backup for Microsoft 365 8.5

The following site has corrupted file data

The following list contains items referencing corrupted files

For Veeam Backup for Microsoft 365 8.6

The following site has inconsistent file data

The following list contains items referencing inconsistent files

WARNING: The following list contains items that reference files with incomplete downloads
 
 
  • If no messages appear, no further action is required for that repository.
  • If you see messages other than those listed above, please contact Veeam Technical Support for assistance in investigating further.
Step 3: Scan Repository and Flag Affected Items

Run the following cmdlet to scan the repository and flag the affected items for re-backup. Their correct content will be redownloaded during the next backup job run in Step 4. Note that during scanning, the repository remains locked for any other operations, including backups, restores, and management. All backup and restore sessions related to this repository must be stopped before running a repair session.

  • For an object storage repository:
$session = Start-VBORepositoryRepairSession -Repository $repository -Type CleanMissingFilesData -Mode Full -Scope Full
  • For a JET-based repository (Veeam Backup for Microsoft 365 8.6+ Only):
$session = Start-VBORepositoryRepairSession -Repository $repository -Type CleanMissingFilesData -Mode Full
  • To limit the scope to a specific SharePoint site, use the -WebIds parameter:
$session = Start-VBORepositoryRepairSession -Repository $repository -Type CleanMissingFilesData -Mode Full -WebIds '{InternalWebId}','{InternalWebId}'
Wait for the session to complete before proceeding to Step 4. To verify that a session has completed, check its status using the session object returned in Step 3: 
Get-VBORepositoryRepairSession -Id $session.Id
Step 4: Run Backup Jobs

After the repair session has finished, run the backup jobs containing impacted SharePoint, OneDrive, and Teams files data. Files that are still present in production will be redownloaded with their correct content.

Step 5: Review Outcome and Identify Unrecoverable Files

To identify files that could not be redownloaded in Step 4, run the following cmdlet:

Test-VBORepository -Repository $repository -DetailedOutput

The output will be saved to logs located in: C:\ProgramData\Veeam\Backup365\Logs\IntegrityVerification\

Files that could not be redownloaded will have log entries containing both of the following. The first message varies by object type:

File preview has empty content length
Item has empty content length
Attachment has empty content length

repair history: FileWasReset

Error line example for an object storage repository:

  • [Info] File preview has empty content length (repository ID: {repo-guid}, organization: {tenant}.onmicrosoft.com, web: OrganizationId: {orgGuid}, SiteId: {siteID-guid}, WebId: {webID-guid}, InternalWebId: {intwebID-guid}, web URL: /sites/example, list ID: {listID-guid}, item ID: {itemID-guid}, item title: example item, file name: example.png, file ref: /sites/example/Lists/example/2_.000, file ID: {fileID-guid}, file version: 2, OneDrive: False, file size: 8675309, from: mm/dd/yyyy hh:mm:ss PM, to: mm/dd/yyyy hh:mm:ss AM, data loss type: AllVersionsLost, repair history: FileWasReset)

Error line examples for a JET-based repository:

  • [Info] Item has empty content length (repository ID: {repo-guid}, site ID: {siteID-guid}, web ID: {webID-guid}, list ID: {listID-guid}, item ID: {itemID-guid}, version: 4, repair history: FileWasReset, file URL: /sites/example.pdf, file reference: /sites/example.pdf)

  • [Info] Attachment has empty content length (repository ID: {repo-guid}, site ID: {siteID-guid}, web ID: {webID-guid}, list ID: {listID-guid}, item ID: {itemID-guid}, file ID: {fileID-guid}, file version: 2, repair history: FileWasReset, file URL: /sites/example.pdf, item file reference: /sites/example/Lists/example/2_.000)

To simplify this process, open the log files in Notepad++ and use the following regex search:

^(?=.*has empty content length)(?=.*repair history: FileWasReset).*$

Repairing Backup Copies

Test-VBORepository cannot be run against a repository that serves as the target of a backup copy job. If inconsistent files were copied to such a repository before they were repaired, scan and fix the source repository first, following Steps 1 through 4 above.

In Veeam Backup for Microsoft 365 8.6* and later, once inconsistent files have been repaired in the source repository, no manual action is required to repair them in the backup copy target repository. On the next scheduled run of the backup copy job, the job automatically detects that the source backup contains repaired files, re-reads those files from the source repository, and re-copies them to the target repository. Every file repaired in the source repository is copied, and only those files are copied. The job does not perform a full resync of unaffected data, and each repaired file is copied once.

Note: The detailed report described in Step 5 is not available for a backup copy target repository. Verify the outcome against the source repository instead.

*The automatic triggering of the Backup Copy to repair files on its destination storage that were redownloaded on the primary backup storage will only occur if the Integrity Check was performed using version 8.6 or newer. If an Integrity Check was run using Veeam Backup for Microsoft 365 v8.5, after upgrading to version 8.6, the backup copy must be manually triggered to repair its destination files:

$job = Get-VBOJob -Name "Backup Job Name"
$copyJob = Get-VBOCopyJob -BackupJob $job
Start-VBOCopyJob -Job $copyJob -Full -SharePointData

More Information

For the description of the root cause, see KB4835: Potential Issue With Backing up SharePoint, OneDrive, Teams Files, and List Attachments.

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.

]]> <![CDATA[Veeam Backup for Microsoft 365 Restore Portal Error: "The server has rejected the client credentials"]]> https://www.veeam.com/kb4292 2026-09-17T00:00:00Z 2026-09-17T00:00:00Z

Veeam Backup for Microsoft 365 Restore Portal Error: "The server has rejected the client credentials"

KB ID: 4292
Product: Veeam Backup for Microsoft 365 | 6.0 | 7.0 | 7a | 8 | 8.1 | 8.2 | 8.3 | 8.4 | 8.5 | 8.6
Published: 2022-03-24
Last Modified: 2026-09-17

Challenge

When attempting to login to the Veeam Backup for Microsoft 365 Restore Portal, the following error occurs:

The server has rejected the client credentials.
screenshot of error

Solution

At this time, three known scenarios cause this error. Each scenario is described below with its corresponding resolution.

Scenario 1: Restore operator authentication certificate is installed in the wrong certificate store

When the "Enable restore operator authentication with Microsoft credentials" option was configured, a certificate was selected from the certificate store or imported from a PFX file. That certificate is not installed in the location required for its type, so the certificate chain cannot be validated.

The required placement depends on the certificate type:

  • Self-signed certificate: The certificate is its own trust anchor. It must be present in the Personal certificate store of the Veeam Backup for Microsoft 365 server with an exportable private key. If the Veeam Backup for Microsoft 365 REST API component is installed on a separate machine, this certificate must also be imported into the Trusted Root Certification Authorities store on that machine.
  • Certificate issued by a Certification Authority: The certificate must remain in the Personal certificate store of the Veeam Backup for Microsoft 365 server with its private key. Only the issuing root CA certificate belongs in the Trusted Root Certification Authorities store.

If a certificate issued by a Certification Authority has been installed in the Trusted Root Certification Authorities store, it is treated as a trust anchor, and the following error occurs:

Failed to validate remote certificate.
Failed to validate the certificate chain:
The revocation function was unable to check revocation for the certificate.

Reference: Enabling Restore Operator Authentication

Authentication settings

Scenario 2: Updated application certificate has not been added to Microsoft Entra

The application certificate within the Restore Portal settings has been updated, but it has not been added to the application settings of Microsoft Entra.

When the certificate is updated within Veeam Backup for Microsoft 365, it must also be added in the application settings through the Microsoft Entra admin center.

Reference: Restore Portal Settings

Restore Portal settings

Scenario 3: Tenant-side configuration has not been completed

For Backup as a Service for Microsoft 365 usage scenarios, the tenant must complete the configuration steps that assign the permissions required for Restore Portal access.

Ensure that all steps provided in the Restore Portal Configuration for "On Tenant Side" have been completed.

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.

]]> <![CDATA[Avoiding Unplanned Reboots and Service Restarts When Upgrading Veeam Analytics Service]]> https://www.veeam.com/kb4927 2026-09-16T00:00:00Z 2026-09-16T00:00:00Z

Avoiding Unplanned Reboots and Service Restarts When Upgrading Veeam Analytics Service

KB ID: 4927
Product: Veeam ONE | 13 | 13.1
Published: 2026-09-16
Last Modified: 2026-09-16

Purpose

The Veeam Analytics Service runs on every Veeam Backup & Replication server connected to Veeam ONE. When Veeam ONE is upgraded, it automatically upgrades the Veeam Analytics Service on each connected server.

On Windows-based Veeam Backup & Replication deployments, this upgrade can install a missing or outdated prerequisite runtime (Microsoft .NET Runtime or Microsoft ASP.NET Core Runtime), which can trigger an unplanned reboot of the server. A restart only occurs when a prerequisite actually has to be installed; a server that already has the required versions is upgraded without any restart. Veeam ONE cannot control or postpone this restart, because the prerequisites are installed by the platform's own installers rather than by Veeam ONE itself.

Note: The Veeam Software Appliance (VSA) is not affected. Its prerequisites are supplied differently and do not require a restart to install.

This article describes how to install the prerequisites on connected Windows-based Veeam Backup & Replication servers in advance, at a time chosen by the administrator, so that the Veeam ONE upgrade does not restart them.

Affected upgrade paths

The Veeam Analytics Service was introduced in Veeam ONE 13, so this behavior applies to upgrades between Veeam ONE 13 releases. It has been identified, on Windows-based Veeam Backup & Replication deployments, for upgrades from any Veeam ONE 13.0 build to Veeam ONE 13.1. For a full list of builds, see KB4357.

Solution

To mitigate the possibility of an unplanned reboot of the Veeam Backup & Replication server, manually install the .NET components on each connected Windows-based Veeam Backup & Replication server before the Veeam ONE server is upgraded.

The current list of Veeam Backup & Replication servers connected to Veeam ONE is available in the Veeam ONE Web Client, under Configuration → Data Collection Overview.

  1. Copy the following  redistributables from the the \Redistr\x64\ folder on the Veeam ONE installation ISO to the connected Veeam Backup & Replication server:
    • aspnetcore-runtime-10.0.10-win-x64.exe
    • dotnet-runtime-10.0.10-win-x64.exe
  2. Run both installers on the Veeam Backup & Replication server, in any order.
  3. Open Apps & features (or Programs and Features) on the Veeam Backup & Replication server and confirm both of the following are listed before proceeding to upgrade Veeam ONE:
    • Microsoft .NET Runtime - 10.0.10 (x64)
    • Microsoft ASP.NET Core Runtime - 10.0.10 (x64)

 

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.

]]> <![CDATA[Kanister Pods Fail Image Pulls on Kubernetes 1.35]]> https://www.veeam.com/kb4929 2026-09-15T00:00:00Z 2026-09-15T00:00:00Z

Kanister Pods Fail Image Pulls on Kubernetes 1.35

KB ID: 4929
Product: Veeam Kasten for Kubernetes
Published: 2026-09-15
Last Modified: 2026-09-15

Challenge

On Kubernetes 1.35 or later, Veeam Kasten for Kubernetes worker pods fail with ImagePullBackOff errors when the cluster uses a private container registry. These pods run in the application namespace and have no image pull credentials.

The following operations are affected:

  • Backup and restore of applications protected by a Kanister blueprint
  • Backup of volumes not attached to a running workload
  • Execution hooks whose blueprint creates a pod
  • Generic Storage Backup operations

Kanister times out after approximately 15 minutes per attempt.

Cause

This issue occurs because Kubernetes 1.35 enables the KubeletEnsureSecretPulledImages feature gate by default. Every pod must now present valid registry credentials to pull an image, and cached images no longer bypass authentication.

Veeam Kasten for Kubernetes runs certain worker pods in the application namespace. The image pull secret (by default, k10-ecr) exists only in the kasten-io namespace. Those worker pods have no imagePullSecrets and reference no service account credentials, so they cannot authenticate against a private registry.

On Kubernetes 1.34 and earlier, cached images did not require re-authentication. This masked the missing credentials.

Solution

Copy the image pull secret into each protected namespace, then attach it to the default service account of that namespace. Both steps are required. A secret that exists in the namespace but is not referenced by the service account has no effect.

Prerequisites

  • kubectl access to the cluster
  • Permission to create secrets and patch service accounts in the target namespace
  • The name of the image pull secret used during Veeam Kasten for Kubernetes installation (default: k10-ecr)

Procedure

1. Set variables for the target namespace and secret name. If a name other than k10-ecr was provided to global.imagePullSecret during installation, replace the value accordingly:

export APP_NAMESPACE=<application-namespace>
export SECRET_NAME=k10-ecr

2. Copy the image pull secret from the kasten-io namespace into the application namespace:

kubectl get secret ${SECRET_NAME} --namespace=kasten-io --output=json \
    | jq '{apiVersion, kind, metadata: {name: .metadata.name}, type, data}' \
    | kubectl apply --namespace=${APP_NAMESPACE} --filename=-

3. Patch the default service account to reference the secret:

kubectl patch serviceaccount default \
    --namespace=${APP_NAMESPACE} \
    --patch="{\"imagePullSecrets\":[{\"name\":\"${SECRET_NAME}\"}]}"

4. Repeat steps 1–3 for each protected application namespace.

5. Delete any Kanister pods stuck in ImagePullBackOff. Veeam Kasten for Kubernetes recreates them with the updated credentials.

Important

  • The kubectl patch command replaces the imagePullSecrets field rather than merging into it. If the default service account already lists other image pull secrets, include them in the patch value.
  • To restore an application into a namespace that does not yet exist, create and configure that namespace before you run the restore.

More Information

  • This is a documented workaround. A product-side fix is tracked internally.
  • Clusters that use a public registry are not affected.
  • For more information on private registry configuration, see the Air-Gapped Installation section of the Veeam Kasten documentation.
  • For details on the upstream Kubernetes change, see KEP-2535 (KubeletEnsureSecretPulledImages).

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.

]]> <![CDATA[Veeam Backup & Replication Upgrade Paths]]> https://www.veeam.com/kb2053 2026-09-15T00:00:00Z 2026-09-15T00:00:00Z

Veeam Backup & Replication Upgrade Paths

KB ID: 2053
Product: Veeam Backup & Replication | 10 | 11 | 12 | 12.1 | 12.2 | 12.3 | 12.3.1 | 12.3.2 | 13 | 13.1
Published: 2015-07-10
Last Modified: 2026-09-15
Languages: JP
Tenants of Veeam Cloud Service Providers

If your Veeam Backup & Replication installation is connected to a Veeam Cloud Service Provider, contact your Service Provider before upgrading to ensure that the intended upgrade will not break compatibility.

A tenant cannot be on a newer version of Veeam Backup & Replication than the Service Provider.

Purpose

This article documents upgrade paths available to Windows-based Veeam Backup & Replication deployments to reach the latest version.

Solution

End of Support Upgrade Path

If you are using a version of Veeam Backup & Replication (VBR) that has reached its End of Support (EOS) and cannot be directly upgraded to a supported version, you will need to install a new instance of VBR using the latest VBR version.

Clarification: If the Upgrade Instructions in the User Guide for a currently supported version of VBR include an upgrade path from an older, unsupported version, this upgrade pathway is still considered supported. This article provides details on upgrade processes for such situations, provided that a currently supported version of VBR supports a direct upgrade from these older versions.

For example:

  • When VBR version 11a was supported, it provided an upgrade path from VBR version 9.5 Update 4b. However, VBR version 12 does not support upgrading directly from 9.5 Update 4b. As a result, after VBR 11a reached EOS, the upgrade path for 9.5 Update 4b was removed from this document.
  • VBR version 12.0, which is currently supported, allows upgrading directly from VBR version 10a. Thus, although VBR 10a is no longer supported itself, the upgrade details for 10a are included in this document because an upgrade to VBR 12.0 from that version is officially supported.
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.3 until after the migration is completed.

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

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

The upgrade paths shown below for 13.1 are the same for 13.0.

10a to 13.1.1

Path: 10a (10.0.1.x) → 12.0 → 12.3.2 → 13.1.1
  1. Upgrade to Veeam Backup & Replication 12.0
    Note: It is necessary to first upgrade to Veeam Backup & Replication 12.0 to allow components such as Veeam Backup for Nutanix AHV Proxy to be upgraded to a version that is compatible with being upgraded to the version included with Veeam Backup & Replication 12.3.2.
  2. Upgrade to Veeam Backup & Replication 12.3.2
  3. Upgrade to Veeam Backup & Replication 13.1.1

11 to 13.1.1

Path: 11 (11.0.0.x) → 12.0 → 12.3.2 → 13.1.1
  1. Upgrade to Veeam Backup & Replication 12.0
    Note: It is necessary to first upgrade to Veeam Backup & Replication 12.0 to allow components such as Veeam Backup for Nutanix AHV Proxy to be upgraded to a version that is compatible with being upgraded to the version included with Veeam Backup & Replication 12.3.2.
  2. Upgrade to Veeam Backup & Replication 12.3.2
  3. Upgrade to Veeam Backup & Replication 13.1.1

11a to 13.1.1

Veeam Backup & Replication 11a Upgrade Path Notes
  • If the Veeam Backup & Replication 11a deployment does not interact with Nutanix AHV, it can be upgraded directly to the latest version 12.3 release, skipping version 12.0.
  • If Veeam Backup & Replication 11a P20240304 is installed, it is only compatible with upgrading to version 12.1.2 or higher (such as 12.3). Upgrading to version 12.0 is not supported.
Path: 11a (11.0.1.x) → 12.0 → 12.3.2 → 13.1.1
  1. Upgrade to Veeam Backup & Replication 12.0
    Note: It is necessary to first upgrade to Veeam Backup & Replication 12.0 to allow components such as Veeam Backup for Nutanix AHV Proxy to be upgraded to a version that is compatible with being upgraded to the version included with Veeam Backup & Replication 12.3.2.
  2. Upgrade to Veeam Backup & Replication 12.3.2
  3. Upgrade to Veeam Backup & Replication 13.1.1

12.0 to 13.1.1

Path: 12.0 → 12.3.2 → 13.1.1
  1. Upgrade to Veeam Backup & Replication 12.3.2
  2. Upgrade to Veeam Backup & Replication 13.1.1

12.1 to 13.1.1

Path: 12.1 → 12.3.2 → 13.1.1
  1. Upgrade to Veeam Backup & Replication 12.3.2
  2. Upgrade to Veeam Backup & Replication 13.1.1

12.2 to 13.1.1

Path: 12.2 → 12.3.2 → 13.1.1
  1. Upgrade to Veeam Backup & Replication 12.3.2
  2. Upgrade to Veeam Backup & Replication 13.1.1

12.3 to 13.1.1

Path: 12.3 → 12.3.2 → 13.1.1
  1. Upgrade to Veeam Backup & Replication 12.3.2
  2. Upgrade to Veeam Backup & Replication 13.1.1

12.3.1 to 13.1.1

Path: 12.3.1 → 13.1.1
  1. Upgrade to Veeam Backup & Replication 13.1.1

12.3.2 to 13.1.1

Path: 12.3.2 → 13.1.1
  1. Upgrade to Veeam Backup & Replication 13.1.1

13.0.1 to 13.1.1

Path: 13.0.1 → 13.1.1
  1. Upgrade to Veeam Backup & Replication 13.1.1

13.0.2 to 13.1.1

Path: 13.0.2 → 13.1.1
  1. Upgrade to Veeam Backup & Replication 13.1.1

13.0.3 to 13.1.1

Path: 13.0.3 → 13.1.1
  1. Upgrade to Veeam Backup & Replication 13.1.1

13.1 to 13.1.1

Path: 13.1 → 13.1.1
  1. Update to Veeam Backup & Replication 13.1.1 using the Updater Package

More Information

Latest Veeam Backup & Replication Platform Support:
Latest Veeam Backup & Replication System Requirements:

 

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.

]]> <![CDATA[Release Information for Veeam Backup for Microsoft 365 8.6]]> https://www.veeam.com/kb4913 2026-09-14T00:00:00Z 2026-09-14T00:00:00Z

Release Information for Veeam Backup for Microsoft 365 8.6

KB ID: 4913
Product: Veeam Backup for Microsoft 365 | 8.6
Published: 2026-09-14
Last Modified: 2026-09-14

Requirements

This release can be used to:

  • upgrade an existing v8, v8.1, v8.2, v8.3, v8.4, or v8.5 deployment of Veeam Backup for Microsoft 365 to v8.6.
  • install a new deployment of Veeam Backup for Microsoft 365 v8.6.

After installing this release, the Veeam Backup for Microsoft 365 build number will be 8.6.0.1102.

Release Information

8.6.0.1102

2026-09-14

New Features and Enhancements

  • Added PowerShell cmdlets to remediate data in JET-based repositories, repositories with backup copies, and immutable repositories affected by the issue described in KB4835. For more information, see KB4874.
  • When an organization is added or edited, the backup app registrations in Microsoft Entra ID automatically receive the permissions required to support Exchange mailbox protection after EWS retirement. For more information, see KB4820.
  • Added the ability to place object storage backup repositories into maintenance mode using PowerShell cmdlets or the REST API. While a repository is in maintenance mode, Veeam Backup for Microsoft 365 blocks all operations on that repository, allowing administrators to safely perform storage-level maintenance without interference.

Bug Fixes

General
  • A retention task gets stuck and times out after the NATS server restarts.
Backup and Backup Copy
  • When the public folder hierarchy root stored in the backup no longer matches the root folder reported by Microsoft 365, public folder mailbox backup fails while processing the hierarchy root (IPM_SUBTREE) with the error: 
    Object reference not set to an instance of an object
  • In multi-geo organizations where location protection is disabled, SharePoint backup jobs fail with the error: 
    Failed to resolve sites: ambiguous locations found
  • SharePoint incremental backup jobs process all site changes from the beginning instead of continuing from the last backup point after SharePoint rejects a change token as outdated.
  • When redirect site URL lookups are throttled and cannot acquire a request slot within the allowed wait time, even if throttling is not reported at the tenant level, a SharePoint backup job fails at the site resolution stage with the error: 
    Request must be retried
  • In organizations with a hybrid Exchange deployment, some mailboxes are skipped during backup with the warning: 
    Exchange account was not found.
  • A backup job that fails at the resolve stage because of Microsoft 365 throttling is reported as Failed. No restore point is created and no retry is attempted, even when some objects were processed successfully.
  • A backup job processing SharePoint or Teams data does not trigger a retry run when all objects fail with the error: 
    Access to this site is blocked.
  • In multi-geo Microsoft 365 organizations, a throttling event in one geo region causes backup jobs in all other regions to slow down or fail.
  • A Teams backup job fails with an out-of-memory error when processing channels that contain a very large number of messages.
  • In multi-geo SharePoint environments, a backup job fails for sites whose data location cannot be resolved to any configured geo region.
  • A SharePoint backup job intermittently fails during the resolve stage with the error: 
    Object reference not set to an instance of an object
  • When the backup scope includes archived Microsoft Teams, a backup job fails with the error: 
    The response status code does not indicate success: 400 (Bad Request)
Restore
  • Browsing or restoring OneDrive and SharePoint data from archive-tier object storage hangs and eventually times out.
  • Search in Veeam Explorer for Microsoft Exchange fails with an ArgumentOutOfRangeException error when a mailbox item contains an RTF-formatted body with emoji or other characters outside the Basic Multilingual Plane.
  • Saving OneDrive items using Veeam Explorer for Microsoft OneDrive fails with the error: 
    Object reference not set to an instance of an object.
REST APIs
  • Advanced search across Exchange items filtered by DateReceived using an ISO-8601 UTC timestamp, for example 2025-01-02T05:59:59Z, fails with HTTP 500.
  • The (GET) v8/BackupRepositories/{repositoryId}/UserData REST API endpoint responds very slowly on large repositories.
PowerShell and Data Management
  • Repository integrity check and repair operations fail with an out-of-memory error on large repositories.

Download Information

Download VB365 8.6 ISO
See Veeam Backup for Microsoft 365 Current Version Download Page for ISO hashes.

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.

]]> <![CDATA[List of Security Fixes and Improvements in Veeam Kasten for Kubernetes]]> https://www.veeam.com/kb4825 2026-09-14T00:00:00Z 2026-09-14T00:00:00Z

List of Security Fixes and Improvements in Veeam Kasten for Kubernetes

KB ID: 4825
Product: Veeam Kasten for Kubernetes | 7 | 7.5 | 8 | 8.5 | 9
Kasten K10 by Veeam | 3 | 5 | 5.5 | 6 | 6.5
Published: 2026-03-02
Last Modified: 2026-09-14

Purpose

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

This article aims to provide our customers' security and compliance teams with detailed information on security improvements.

Full product release notes are available here:

Security Fixes and Improvements

Veeam Kasten for Kubernetes 9.0.5

  • Upgraded to latest UBI base image to resolve multiple CVEs in base OS packages.
  • Updated the Go runtime to resolve additional upstream Go CVEs.
  • Updated the bundled Prometheus Helm chart to resolve security issues.

Veeam Kasten for Kubernetes 9.0.4

  • Upgraded to latest UBI base image to resolve multiple CVEs in base OS packages.
  • Patched go-ntlmssp in the Dex component to resolve CVE-2026-32952.
  • Updated the Go runtime and golang.org/x/mod dependency to resolve CVE-2026-56865 and additional upstream Go CVEs.

Veeam Kasten for Kubernetes 9.0.3

Veeam Kasten for Kubernetes 9.0.2

  • Upgraded to the latest UBI base image to resolve multiple CVEs.
  • Updated third-party dependencies (gomplate, logger base image) in the dex and logger components to address known vulnerabilities.

Veeam Kasten for Kubernetes 9.0.1

  • Upgraded to Go 1.26.5 to resolve CVE-2026-39822 & CVE-2026-42505
  • Updated the UBI minimal base image to incorporate the latest security fixes.
  • Improved logging security for Veeam Backup & Replication API credentials and other sensitive values previously written to Kasten logs.
    • It is recommended to upgrade Veeam Kasten and to refresh the token by manually logging out.
  • Upgraded components of Kasten's bundled Prometheus monitoring stack to resolve multiple CVEs

Veeam Kasten for Kubernetes 8.5.13

  • Updated base images used in the Red Hat Marketplace operator bundle to fix multiple Critical and High CVEs

Veeam Kasten for Kubernetes 8.5.12

  • Upgraded to the latest UBI base image to resolve CVE-2026-45186 and CVE-2026-45447
  • Upgraded to Go 1.26.4 to resolve CVE-2026-42504
  • Kasten Multi-cluster Permissions: Hardened multi-cluster security by tightening the permissions granted to the impersonation `ClusterRole` on managed secondary clusters and removing sensitive token values from debug logs.

Veeam Kasten for Kubernetes 8.5.10

  • Upgraded to latest UBI base image to resolve CVE-2026-40356 and CVE-2026-4878
  • Immutability regression in Kasten 8.5.1–8.5.9 (S3 / GCS / Azure)
    Newly written backup objects were not stamped with a retain-until date at write time and remained deletable until the Blob Lifecycle Manager applied protection on its next refresh cycle. A user, script, or attacker with bucket delete permissions could permanently delete those objects during this window, potentially rendering the affected restore points unrecoverable.

    Mitigation: Configure a bucket-level Default Object Lock retention so the object store stamps new objects at write time, or upgrade to Kasten 8.5.10.

Veeam Kasten for Kubernetes 8.5.5

Veeam Kasten for Kubernetes 8.5.3

Veeam Kasten for Kubernetes 8.5.2

  • Updated base image used to build Veeam Kasten container images to pull in latest security updates.

Veeam Kasten for Kubernetes 8.5.1

Veeam Kasten for Kubernetes 8.0.15

  • Upgrade to Go 1.25.5 to address CVE-2025-61727 and CVE-2025-61729.
  • Updated base image used to build Veeam Kasten container images to pull in latest security updates.

Veeam Kasten for Kubernetes 8.0.14

  • Improved logging security for specific block mode datamover upload Pod invocations. It is recommended to upgrade Veeam Kasten to get this fix.

Veeam Kasten for Kubernetes 8.0.13

  • Updated base image used to build Veeam Kasten container images to pull in latest security updates.

Veeam Kasten for Kubernetes 8.0.11

  • Upgrade to Go 1.25.3 to mitigate security vulnerabilities.
  • Upgrade to golang.org/x/net@v0.46.0 to address CVE-2025-58190 and CVE-2025-47911.
  • Updated base image used to build Veeam Kasten container images to pull in latest security updates.

Veeam Kasten for Kubernetes 8.0.10

  • Updated base image used to build Veeam Kasten container images to pull in latest security updates.

Veeam Kasten for Kubernetes 8.0.8

  • Upgrade to Go 1.24.7 to mitigate security vulnerabilities.

Veeam Kasten for Kubernetes 8.0.7

  • Updated base image used to build Veeam Kasten container images to pull in latest security updates.

Veeam Kasten for Kubernetes 8.0.6

  • Updated base image used to build Veeam Kasten container images to pull in latest security updates.
  • Upgrade to Go 1.24.6 to mitigate security vulnerabilities.

Veeam Kasten for Kubernetes 8.0.5

  • Increased the security of the generated backup repository passwords.
  • Updated base image used to build Veeam Kasten container images to pull in latest security updates.

Veeam Kasten for Kubernetes 8.0.4

  • Updated base image used to build Veeam Kasten container images to pull in latest security updates.
  • Upgrade to Go 1.24.5 to mitigate security vulnerabilities.

Veeam Kasten for Kubernetes 8.0.3

  • Updated base image used to build Veeam Kasten container images to pull in latest security updates.

Veeam Kasten for Kubernetes 8.0.2

  • Updated base image used to build Veeam Kasten container images to pull in latest security updates.
  • Upgrade to Go 1.24.4 to mitigate security vulnerabilities.

Veeam Kasten for Kubernetes 8.0.1

  • Updated base image used to build Veeam Kasten container images to pull in latest security updates.
  • Upgrade to Go 1.24.3 to mitigate CVE-2025-22873.

Veeam Kasten for Kubernetes 8.0.0

  • Updated base image used to build Veeam Kasten container images to pull in latest security updates.

Veeam Kasten for Kubernetes 7.5.9

  • Updated base image used to build Veeam Kasten container images to pull in latest security updates.
  • Upgrade to Go 1.23.8 to mitigate CVE-2025-22871.

Veeam Kasten for Kubernetes 7.5.8

  • Updated base image used to build Veeam Kasten container images to pull in latest security updates.

Veeam Kasten for Kubernetes 7.5.5

  • Upgrade to Go 1.23.7 to mitigate security vulnerabilities.

Veeam Kasten for Kubernetes 7.5.4

  • Update K10 services base image to pull in latest security updates.
  • Updated base image used to build Veeam Kasten container images to pull in latest security updates.
  • Upgrade to Go 1.23.6 to mitigate security vulnerabilities.

Veeam Kasten for Kubernetes 7.5.3

  • Upgraded Prometheus to chart version v26.1.0 to pull in latest security updates.
  • Update K10 services base image to pull in latest security updates.
  • Redacted sensitive information in Kasten logging.

Veeam Kasten for Kubernetes 7.5.2

  • Update K10 services base image to pull in latest security updates.

Veeam Kasten for Kubernetes 7.5.1

  • Basic users are now restricted from viewing application details of applications in other namespaces.
  • Basic users now require specific permission to view each action type through the Veeam Kasten dashboard.
  • Update K10 services base image to pull in latest security updates.

Veeam Kasten for Kubernetes 7.5.0

  • Improved algorithm for authentication cookie validation in OIDC mode. All the users will need to re-login.

Veeam Kasten for Kubernetes 7.0.14

  • Update K10 services base image to pull in latest security updates.

Veeam Kasten for Kubernetes 7.0.13

  • Update Grafana version to 8.5.8 to pull in the latest security updates.
  • Upgraded Prometheus chart version to 25.28.0 to pull in latest security updates.

Veeam Kasten for Kubernetes 7.0.10

  • Update K10 services base image to pull in latest security updates.

Veeam Kasten for Kubernetes 7.0.9

  • Update K10 services base image to pull in latest security updates.

Veeam Kasten for Kubernetes 7.0.8

  • Update K10 services base image to pull in latest security updates.

Veeam Kasten for Kubernetes 7.0.6

  • Fixed critical authentication vulnerability. This upgrade is recommended for all users.

Veeam Kasten for Kubernetes 7.0.5

  • Update K10 services base image to pull in latest security updates.

Veeam Kasten for Kubernetes 7.0.4

  • Upgrade Fluent Bit to mitigate CVE-2024-4323.
  • Upgrade to Go 1.22.5 to mitigate security vulnerabilities.

Veeam Kasten for Kubernetes 7.0.2

  • Upgrade Python packages to mitigate security vulnerabilities.
  • Update K10 services base image to pull in latest security updates.

Veeam Kasten for Kubernetes 7.0.1

  • Upgrade to Go 1.22.4 to mitigate security vulnerabilities.
  • Update K10 services base image to pull in latest security updates.

Veeam Kasten for Kubernetes 7.0.0

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.5.14

  • Limited the scope of infrastructure credentials to improve security posture.
  • Upgrade to Go 1.22.3 to mitigate security vulnerabilities.
  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.5.13

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.5.11

  • Upgraded to Go v1.21.9 to mitigate security vulnerabilities.

Kasten K10 by Veeam 6.5.9

  • Users are now restricted from listing actions in namespaces without proper authorization. All customers are encouraged to upgrade to get the fix for this issue.

Kasten K10 by Veeam 6.5.7

  • Upgraded google.golang.org/protobuf to mitigate CVE-2024-24786.
  • Upgraded to Go v1.21.8 to mitigate security vulnerabilities.
  • Changes in SecurityContextConstraints resource were made to reflect the latest securityContext updates on K10 workloads.
  • Explicitly set runAsNonRoot=true, seccompProfile=RuntimeDefault, allowPrivilegeEscalation=false and capabilities.drop=["ALL"] for K10 service containers.
  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.5.4

  • Explicitly set runAsNonRoot=true, seccompProfile=RuntimeDefault, allowPrivilegeEscalation=false and capabilities.drop=["ALL"] for K10 service containers.
  • Users are now restricted from restoring data without proper authorization. All customers are encouraged to upgrade to get the fix for this issue.
  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.5.3

  • Improve logging to prevent logging of sensitive backup location connection details.

Kasten K10 by Veeam 6.5.2

  • Upgrade golang.org/x/crypto to mitigate security vulnerability CVE-2023-48795.
  • Updates dependencies to address security vulnerabilities in 3rd party libraries.

Kasten K10 by Veeam 6.5.1

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.5.0

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.0.10

  • Upgrade to Go v1.21.3 to mitigate security vulnerabilities.
  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.0.8

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.0.7

  • Upgrade to Go 1.20.8 to mitigate security vulnerabilities.

Kasten K10 by Veeam 6.0.5

  • Upgrade golang.org/x/net to v0.13.0 to mitigate CVE-2023-3978.
  • Upgrade to Go 1.20.7 to mitigate security vulnerabilities.
  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.0.3

  • Updates emissary's Go dependencies to address security vulnerabilities.
  • Upgrade to Go 1.20.6 to mitigate security vulnerabilities.

Kasten K10 by Veeam 6.0.2

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.5.11

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.5.9

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.5.7

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.5.6

  • Upgrade to Go 1.19.6 to mitigate security vulnerabilities.

Kasten K10 by Veeam 5.5.5

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.5.4

  • Basic users are now restricted from using transforms in RestoreActions.

Kasten K10 by Veeam 5.5.3

  • It is now possible to prevent basic users from creating ImportActions or RestoreActions. In some multi-tenant environments, these actions should only be available to administrators.
  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.5.2

  • Upgrade to Go 1.19.4 to mitigate security vulnerabilities.
  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.5.1

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.5.0

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.0.11

  • Upgrade Dex image to mitigate security vulnerabilities.
  • Upgrade to Go 1.19.2 to mitigate security vulnerabilities.

Kasten K10 by Veeam 5.0.9

  • Update Grafana version to 9.1.5 to pull in the latest security updates.
  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.0.8

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.0.5

  • Update K10 services base image to pull in latest security updates.
  • Update Emissary Ingress to 3.1.0 to include latest security updates.

Kasten K10 by Veeam 5.0.3

  • Upgrade to Go 1.17.12 to include the latest security patches.

Kasten K10 by Veeam 5.0.2

  • Update K10 services base image to pull in latest security updates.
  • Update Emissary Ingress (Ambassador) to 3.0.0 to include latest security updates.

Kasten K10 by Veeam 5.0.0

  • Upgrade to Go 1.17.10 to include the latest security patches.

Kasten K10 by Veeam 4.5.15

  • Update Grafana version to 8.5.0 to pull in the latest security updates.
  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.5.13

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.5.12

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.5.11

  • Update Ambassador to 1.14.3 to include latest security updates.

Kasten K10 by Veeam 4.5.10

Kasten K10 by Veeam 4.5.9

  • Fix CVE-2021-23017 discovered in the previous nginx versions.
  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.5.7

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.5.6

Kasten K10 by Veeam 4.5.2

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.0.13

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.0.10

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.0.9

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.0.6

  • Fix proxy requests to secondary clusters to be restricted to the secondary cluster.
  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.0.5

  • Update Go to pull in latest security fixes.
  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.0.4

  • Update Ambassador to 1.13.6 to include latest security updates.
  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.0.3

  • Upgrade golang.org/x/net prevent denial of service (CVE-2021-33194).

Kasten K10 by Veeam 4.0.2

  • Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 3.0.13

  • Update Ambassador version to pull in security fixes in Envoy 1.15.4

Kasten K10 by Veeam 3.0.1

  • Mitigate potential crashes caused by malicious certificates.

Kasten K10 by Veeam 2.5.14

  • Module upgrades to address CVE-2020-14040.
  • Upgraded Ambassador to incorporate the Envoy 1.14.3 security update.

Kasten K10 by Veeam 2.5.12

  • When K10 is deployed with OIDC, user-initiated actions (via the API, CLI, or the dashboard) will be attributed to the user instead of the K10 service account.

Kasten K10 by Veeam 2.5.9

  • Upgraded several JavaScript packages to address recently disclosed CVEs.

More Information

Related Articles

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.

]]> <![CDATA[Shared Server Compatibility of Veeam Backup for Microsoft 365 and Veeam Backup & Replication]]> https://www.veeam.com/kb4325 2026-09-14T00:00:00Z 2026-09-14T00:00:00Z

Shared Server Compatibility of Veeam Backup for Microsoft 365 and Veeam Backup & Replication

KB ID: 4325
Product: Veeam Backup & Replication | 12 | 12.1 | 12.2 | 12.3 | 13 | 13.1
Veeam Backup for Microsoft 365 | 8 | 8.1 | 8.2 | 8.3 | 8.4 | 8.5 | 8.6
Published: 2022-08-10
Last Modified: 2026-09-14

Purpose

It is important to remember that Veeam Backup for Microsoft 365 and Veeam Backup & Replication are separate backup products designed to operate separately from each other. However, both Veeam Backup for Microsoft 365 and Veeam Backup & Replication utilize Veeam Explorers as secondary applications to perform application item restores. The Veeam Explorers are installed alongside either backup application. Due to this shared use of the Veeam Explorer applications, it is imperative that when both Veeam Backup for Microsoft 365 and Veeam Backup & Replication are installed on the same server, that only specific compatible versions be installed (see table below). Failure to ensure compatibility could lead to a situation where one backup product may not be able to utilize the Veeam Explorer application installed by the other backup product, thus causing application item restores to fail.

Solution

When installing Veeam Backup & Replication (VBR) and Veeam Backup for Microsoft 365 (VB365) on the same server, be mindful of the following compatibility when upgrading.

Note: As new versions of either product are released, they will be added to the table, and as versions reach End of Support, they will be removed. The release schedule of these products is not synchronized. If a version of either product is released before the compatible version of the other, it is critical to wait until inter-compatible versions are available. For example, if a new version of Veeam Backup & Replication is released and a compatible version of Veeam Backup for Microsoft 365 is not available yet, upgrading Veeam Backup & Replication would lead to the issue documented in KB3028.

  VBR13.1 VBR 13 VBR
12.1, 12.2, 12.3		 VBR
12.0
VB365 8.6  [1], [2]  [1], [2]  [1], [2]  [1]
VB365 8.5  [1], [2]  [1], [2]  [1], [2]  [1]
VB365 8.4  [1], [2]  [1], [2]  [1], [2]  [1]
VB365 8.3  [1], [2]  [1], [2]  [1], [2]  [1]
VB365 8.2  [1], [2]  [1], [2]  [1], [2]  [1]
VB365 8.1  [1], [2]  [1], [2]  [1], [2]  [1]
VB365 8  [1], [2]  [1], [2]  [1], [2]  [1]

This table lists only actively supported versions.

Swipe to show more of the table

1 KB4638: How to Use Existing Veeam Backup & Replication PostgreSQL instance for Veeam Backup for Microsoft 365 Deployment

2 KB4639: Veeam Backup & Replication Install Fails with: "A later version of Veeam Explorer for Microsoft Exchange is already installed."

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.

]]> <![CDATA[Build Numbers and Versions of Veeam Backup for Microsoft 365]]> https://www.veeam.com/kb4106 2026-09-14T00:00:00Z 2026-09-14T00:00:00Z

Build Numbers and Versions of Veeam Backup for Microsoft 365

KB ID: 4106
Product: Veeam Backup for Microsoft 365 | 6.0 | 7.0 | 7a | 8 | 8.1 | 8.2 | 8.3 | 8.4 | 8.5 | 8.6
Veeam Backup for Microsoft Office 365 | 1.0 | 1.5 | 2.0 | 3.0 | 4.0 | 5.0
Published: 2021-02-17
Last Modified: 2026-09-14

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

For more information on downloading the latest version of Veeam Backup for Microsoft 365, visit:

Version Console Build Build in Logs Release Date Release Notes
Veeam Backup for Microsoft 365 8 Releases
Veeam Backup for Microsoft 365 8.6 8.6.0.1102 13.6.0.1102 2026-09-14

KB4913

HTML
Veeam Backup for Microsoft 365 8.5 8.5.0.1014 13.5.0.1014 2026-06-29

KB4873

HTML
Veeam Backup for Microsoft 365 8.4 8.4.0.1457 13.4.0.1457 2026-04-16

KB4843

HTML
Veeam Backup for Microsoft 365 8.3 8.3.0.2201 13.3.0.2201 2025-12-18

KB4809

HTML
Veeam Backup for Microsoft 365 8.2 P20251031 8.2.0.2202 13.2.0.2202 2025-11-06 KB4751
Veeam Backup for Microsoft 365 8.2 8.2.0.2008 13.2.0.2008 2025-10-23

KB4751

HTML
Veeam Backup for Microsoft 365 8.1.2.3301 8.1.2.3301 13.1.2.3301 2025-10-24 KB4711
HTML
Veeam Backup for Microsoft 365 8.1.2.180 8.1.2.180 13.1.2.180 2025-07-01
Veeam Backup for Microsoft 365 8.1.1.159 8.1.1.159 13.1.1.159 2025-04-02
Veeam Backup for Microsoft 365 8.1.0.3503 8.1.0.3503 13.1.0.3503 2025-02-27
Veeam Backup for Microsoft 365 8.1.0.331
 8.1.0.331
 13.1.0.331 2025-02-11
Veeam Backup for Microsoft 365 8.1 8.1.0.305 13.1.0.305 2025-01-23
Veeam Backup for Microsoft 365 8.0.5 8.0.5.20 13.0.5.20 2024-11-14 KB4656
HTML
Veeam Backup for Microsoft 365 8.0.4 8.0.4.29 13.0.4.29 2024-10-30
Veeam Backup for Microsoft 365 8.0.3.1073 8.0.3.1073 13.0.3.1073 2024-10-16
Veeam Backup for Microsoft 365 8 P20241004 8.0.3.1044 13.0.3.1044 2024-10-08
Veeam Backup for Microsoft 365 8 P20240910 8.0.2.200 13.0.2.200 2024-09-11
Veeam Backup for Microsoft 365 8 8.0.2.159 13.0.2.159 2024-09-03
Veeam Backup for Microsoft 365 7 Releases
Veeam Backup for Microsoft 365 7a P20240418 7.1.0.2031 12.1.0.2031 2024-04-24 KB4533
Veeam Backup for Microsoft 365 7a P20240411 7.1.0.1502 12.1.0.1502 2024-04-15
Veeam Backup for Microsoft 365 7a P20240123 7.1.0.1501 12.1.0.1501 2024-01-25
Veeam Backup for Microsoft 365 7a P20231218 7.1.0.1401 12.1.0.1401 2023-12-26
Veeam Backup for Microsoft 365 7a 7.1.0.1301 12.1.0.1301 2023-12-05 PDF
Veeam Backup for Microsoft 365 7 P20240123 7.0.0.4901 12.0.0.4901 2024-01-25 KB4425
Veeam Backup for Microsoft 365 7 P20231218 7.0.0.4551 12.0.0.4551 2023-12-25
Veeam Backup for Microsoft 365 7 P20231015 7.0.0.4388 12.0.0.4388 2023-10-15
Veeam Backup for Microsoft 365 7 P20231005 7.0.0.4385 12.0.0.4385 2023-10-12
Veeam Backup for Microsoft 365 7 P20230704 7.0.0.3968 12.0.0.3968 2023-07-13
Veeam Backup for Microsoft 365 7 P20230512 7.0.0.3604 12.0.0.3604 2023-05-24
Veeam Backup for Microsoft 365 7 P20230421 7.0.0.3007 12.0.0.3007 2023-04-25
Veeam Backup for Microsoft 365 7 P20230302 7.0.0.2914 12.0.0.2914 2023-03-09
Veeam Backup for Microsoft 365 7 7.0.0.2911 12.0.0.2911 2023-02-28 PDF
Veeam Backup for Microsoft 365 6 Releases
Veeam Backup for Microsoft 365 6a P20230322 6.1.0.1015 11.2.0.1015 2023-03-28 KB4347
Veeam Backup for Microsoft 365 6a P20221215 6.1.0.438 11.2.0.438 2022-12-20
Veeam Backup for Microsoft 365 6a P20220926 6.1.0.423 11.2.0.423 2022-10-06
Veeam Backup for Microsoft 365 6a P20220825 6.1.0.254 11.2.0.254 2022-08-25
Veeam Backup for Microsoft 365 6a 6.1.0.222 11.2.0.222 2022-08-10 PDF

KB4344
Veeam Backup for Microsoft 365 6 P20220718 6.0.0.400 11.1.0.400 2022-07-27 KB4285
Veeam Backup for Microsoft 365 6 P20220524 6.0.0.385 11.1.0.385 2022-05-31
Veeam Backup for Microsoft 365 6 P20220413 6.0.0.379 11.1.0.379 2022-05-05
Veeam Backup for Microsoft 365 6 GA 6.0.0.367 11.1.0.367 2022-03-09

PDF

KB4286
Veeam Backup for Microsoft Office 365 5 Releases
Veeam Backup for Microsoft Office 365 5d Cumulative Patch KB4278 5.0.3.1063 10.0.5.1063 2022-02-08 KB4278
Veeam Backup for Microsoft Office 365 5d Cumulative Patch KB4270 5.0.3.1060 10.0.5.1060 2022-01-10 KB4270
Veeam Backup for Microsoft Office 365 5d Cumulative Patch KB4235 5.0.3.1051 10.0.5.1051 2021-12-16 KB4235
Veeam Backup for Microsoft Office 365 5d Cumulative Patch KB4222 5.0.3.1035 10.0.5.1035 2021-10-22 KB4222
Veeam Backup for Microsoft Office 365 5d 5.0.3.1033 10.0.5.1033 2021-09-22

PDF

KB4203
Veeam Backup for Microsoft Office 365 5c Cumulative Patch KB4187 5.0.2.42 10.0.4.42
 2021-09-01
 KB4187
Veeam Backup for Microsoft Office 365 5c 5.0.2.22 10.0.4.22 2021-06-28 KB4181
Veeam Backup for Microsoft Office 365 5b Cumulative Patch KB4158 5.0.1.252 10.0.3.252 2021-05-31 KB4158
Veeam Backup for Microsoft Office 365 5b Cumulative Patch KB4135 5.0.1.225 10.0.3.225 2021-04-12 KB4135
Veeam Backup for Microsoft Office 365 5b Cumulative Patch KB4124 5.0.1.207 10.0.3.207 2021-03-12 KB4124
Veeam Backup for Microsoft Office 365 5b 5.0.1.179 10.0.3.179 2021-02-08

PDF

KB4092
Veeam Backup for Microsoft Office 365 5a 5.0.0.1070 10.0.2.1070 2020-12-14

PDF

KB4082
Veeam Backup for Microsoft Office 365 5 Day 0 Update 5.0.0.1063 10.0.2.1063 2020-12-04 PDF
Veeam Backup for Microsoft Office 365 5 GA 5.0.0.1061 10.0.2.1061 2020-12-03 PDF
Veeam Backup for Microsoft Office 365 4 Releases
Veeam Backup for Microsoft Office 365 4c Cumulative Patch KB4099 4.0.1.625 10.0.1.625 2021-02-16 KB4099
Veeam Backup for Microsoft Office 365 4c Cumulative Patch KB4083 4.0.1.612 10.0.1.612 2020-12-24 KB4083
Veeam Backup for Microsoft Office 365 4c Cumulative Patch KB3222 4.0.1.545 10.0.1.545 2020-07-09 KB3222
Veeam Backup for Microsoft Office 365 4c Day 0 Update 4.0.1.531 10.0.1.531 2020-06-16 KB3145
Veeam Backup for Microsoft Office 365 4b Cumulative Patch KB3119 4.0.0.2549 9.6.6.2549 2020-03-31 KB3119
Veeam Backup for Microsoft Office 365 4b 4.0.0.2516 9.6.6.2516 2020-01-31 KB3065
Veeam Backup for Microsoft Office 365 4a Cumulative Patch KB3089 4.0.0.1580 9.6.6.1580 2020-03-10 KB3089
Veeam Backup for Microsoft Office 365 4a 4.0.0.1553 9.6.6.1553 2020-01-21 KB3035
Veeam Backup for Microsoft Office 365 4 GA 4.0.0.1345 9.6.6.1345 2019-11-26 PDF
Veeam Backup for Microsoft Office 365 3 Releases
Veeam Backup for Microsoft Office 365 3 GA 3.0.0.422 9.6.5.422 2019-04-02 PDF
Veeam Backup for Microsoft Office 365 2 Releases
Veeam Backup for Microsoft Office 365 2 Cumulative Patch KB2809 2.0.0.814 9.6.3.814 2018-12-28 KB2809
Veeam Backup for Microsoft Office 365 2 Cumulative Patch KB2765 2.0.0.594 9.6.3.594 2018-09-26 KB2765
Veeam Backup for Microsoft Office 365 2 GA 2.0.0.567 9.6.3.567 2018-07-24 PDF
Veeam Backup for Microsoft Office 365 1 Releases
Veeam Backup for Microsoft Office 365 1.5 GA 1.5.0.1099 9.6.0.1099 2017-10-03 PDF
Veeam Backup for Microsoft Office 365 1 Update 1 1.0.0.912 9.5.0.912 2017-01-20 KB2224
PDF
Veeam Backup for Microsoft Office 365 1 GA 1.0.0.860 9.5.0.860 2016-11-29 PDF
Swipe to show more of the table

Related Articles

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.

]]> <![CDATA[Outbound Public IP Addresses Used by Veeam Data Cloud]]> https://www.veeam.com/kb4900 2026-09-10T00:00:00Z 2026-09-10T00:00:00Z

Outbound Public IP Addresses Used by Veeam Data Cloud

KB ID: 4900
Product: Veeam Data Cloud for Microsoft 365
Veeam Data Cloud for Microsoft Azure
Published: 2026-09-10
Last Modified: 2026-09-10

Purpose

This article lists the outbound public IP addresses that Veeam Data Cloud uses when connecting from the cloud to infrastructure that a customer hosts and controls, for example a Microsoft Azure Key Vault used for BYOK encryption. These addresses are not used for inbound connections made to Veeam Data Cloud.

The addresses belong to the control plane shared by all Veeam Data Cloud products, so they are not specific to any one product.

If a resource in the environment receives connections from Veeam Data Cloud and restricts access with an IP-based rule, whether in a firewall, a security group, a conditional access policy, or a similar control, that rule must account for the addresses listed below. If no IP-based restrictions are applied to connections from Veeam Data Cloud, no action is required.

Solution

Address Change Scheduled for October 2026
The addresses listed below are changing. Five new ranges come into use on 2026-10-12, and the three existing addresses will be retired on 2026-10-22. To ensure a smooth transition, any IP-based rule governing connections from Veeam Data Cloud must be updated to include the new ranges.

Outbound Public IP Addresses

IP address Status Notes
4.223.88.40/30
(4.223.88.40 – 4.223.88.43)		 Upcoming Will become active on 2026-10-12
13.78.8.220/30
(13.78.8.220 – 13.78.8.223)		 Upcoming Will become active on 2026-10-12
20.28.182.92/30
(20.28.182.92 – 20.28.182.95)		 Upcoming Will become active on 2026-10-12
20.46.44.192/30
(20.46.44.192 – 20.46.44.195)		 Upcoming Will become active on 2026-10-12
52.189.108.8/30
(52.189.108.8 – 52.189.108.11)		 Upcoming Will become active on 2026-10-12
20.18.9.116/32
 Active Will be retired after 2026-10-22
40.86.73.61/32
 Active Will be retired after 2026-10-22
135.225.48.195/32
 Active Will be retired after 2026-10-22
Swipe to show more of the table

Advised Action

  • Any IP-based rule that governs connections from Veeam Data Cloud should permit every address listed above as Upcoming or Active. Permitting an upcoming address early has no effect on traffic and avoids a gap in connectivity when it comes into use.
  • Leave an active address in place until after its retirement date, so that connections from Veeam Data Cloud continue to reach the environment while the change is applied.
  • An address listed as Retired is no longer used and can be removed from the rule.

Keeping Your Configuration Current

This list is not fixed. Addresses may be added, changed, or withdrawn as the service evolves, and any rule that references them must be updated to match. Changes are published on this page in advance whenever possible. Because a rule built against an out-of-date list may block legitimate traffic, this page should be reviewed periodically.

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.

]]> <![CDATA[Windows 11 24H2/25H2 | Server 2025 - Recovery Media Restore Fails with: The Local Security Authority cannot be contacted]]> https://www.veeam.com/kb4885 2026-09-10T00:00:00Z 2026-09-10T00:00:00Z

Windows 11 24H2/25H2 | Server 2025 - Recovery Media Restore Fails with: The Local Security Authority cannot be contacted

KB ID: 4885
Product: Veeam Agent for Microsoft Windows
Published: 2026-07-28
Last Modified: 2026-09-10
Issue Resolved in September 8 2026 Windows Updates
The underlying issue documented in this article was resolved by Microsoft in the September 8 2026 security updates for Windows 11 (KB5124008) and Windows Server 2025 (KB5122871). After applying the update, the Veeam Recovery Media must be recreated.

Challenge

When attempting to perform a restore using the Veeam Recovery Media, the restore fails while establishing the connection to the local VeeamAgent.exe process, and the following error occurs:

The Local Security Authority cannot be contacted

Because the failure occurs before a recovery operation can begin, it prevents restoring from any backup location, including local storage, a network shared folder or Veeam backup repository, and cloud repositories.

Cause

This issue occurs due to a regression introduced by the Microsoft June 2026 security update for Windows 11 and Windows Server 2025. The update changed the behavior of the Windows security subsystem (Local Security Authority and Schannel) within the Windows Recovery Environment (WinRE), on which the Veeam Recovery Media is based. As a result, the TLS handshake that secures the connection between the restore wizard and the local VeeamAgent.exe process cannot be completed.

This behavior has been confirmed with the following Microsoft Windows updates for Windows 11 (versions 24H2 and 25H2) and Windows Server 2025, and later updates released before September 2026:

  • KB5094126 (OS builds 26100.8655 and 26200.8655)
  • KB5099536 (OS build 26100.33158)

Recovery media created from a system running an earlier update (for example, KB5089549, OS build 26200.8457, or earlier) is not affected.

Solution

This issue was resolved by Microsoft in the September 8 2026 security updates. To resolve the issue, install the applicable update on the machine where the Veeam Recovery Media is created:

  • Windows 11 (versions 24H2 and 25H2): KB5124008 (OS builds 26200.9445 and 26100.9445)
  • Windows Server 2025: KB5122871 (OS build 26100.33438)

After the update has been installed, the Veeam Recovery Media must be recreated. Recovery media created before the update was installed remains affected.

Workaround

If the September 8 2026 update cannot be installed, the Veeam Recovery Media can be built using the Windows Assessment and Deployment Kit (Windows ADK) instead of the Windows Recovery Environment (WinRE). Recovery media built using the Windows ADK is not affected by this issue.

  1. Ensure that the Windows Assessment and Deployment Kit (Windows ADK) and the corresponding Windows PE add-on are installed on the machine where the Veeam Recovery Media will be recreated.
  2. Create the following registry value on the machine where Veeam Agent for Microsoft Windows is installed to configure it to build the Veeam Recovery Media using the Windows ADK:

    Location:     HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup
    Value Type: DWORD (32-Bit) Value
    Value Name: ForceUseAdkForRecoveryMedia
    Value Data: 1

    Alternatively, the registry value can be created using the following PowerShell command:
New-ItemProperty -Path "HKLM:\SOFTWARE\Veeam\Veeam Endpoint Backup" -Name "ForceUseAdkForRecoveryMedia" -PropertyType DWORD -Value 1 -Force
  1. Recreate the Veeam Recovery Media.

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.

]]> <![CDATA[What Microsoft's EWS Retirement Means for Your Veeam Backups]]> https://www.veeam.com/kb4820 2026-09-10T00:00:00Z 2026-09-10T00:00:00Z

What Microsoft's EWS Retirement Means for Your Veeam Backups

KB ID: 4820
Product: Veeam Data Cloud for Microsoft 365
Veeam Backup for Microsoft 365
Published: 2026-03-25
Last Modified: 2026-09-22
Updated September 2026

This article has been revised to reflect:

  • Microsoft's October 1, 2026 enforcement timeline.
  • The introduction of the EWSAllowedAppIDs allow list.
  • The current status of Veeam's transition to Microsoft Graph.

Customers who have previously read this article are advised to review Steps 1 and 2 closely.

Challenge

Microsoft is retiring Exchange Web Services (EWS) in Exchange Online. EWS is the protocol Veeam currently uses to back up Exchange Online mailboxes.

Key dates:

  • October 1, 2026 — Microsoft begins disabling EWS tenant by tenant. Tenants who have not explicitly enabled EWS will be automatically blocked as the rollout proceeds.
  • April 1, 2027 — EWS is fully and permanently shut down for all tenants.

Note: These EWS phase-out dates apply to all Exchange Online mailbox types (including Kiosk/F1/F3). Configuring EWSAllowedAppIDs as described in Step 2 will maintain backup access for all mailboxes through the end of the transition period. However, if you take no action before October 1, your Exchange Online mailbox backups will fail.

Veeam's transition to Microsoft Graph

Veeam is actively transitioning Exchange backup functionality from EWS to the Microsoft Graph API. This requires additional Microsoft Graph permissions. However, Microsoft has not yet completed all the Graph API capabilities required — specifically, delta sync support needed for incremental backups.

Veeam is working closely with Microsoft to close this gap. Until it is resolved, EWS must remain accessible for Exchange Online backups to continue. See Microsoft's parity gap roadmap for the latest status.

Solution

Step 1: Keep EWS enabled in your tenant

EWS access in Exchange Online is controlled by the EwsEnabled setting in your organization's configuration. Most tenants are currently at the default value of $null, and you will need to change this to $true before October 1, 2026.

What happens to each setting value starting October 1, 2026
If EwsEnabled Value Is: This will happen starting October 1, 2026:
$null
(default — most tenants)		 Microsoft automatically changes this to $false. EWS is blocked for all apps.  You can re-enable it afterward, but that change can take time to propagate, and you will then need a validated App ID allow list (see Step 2) before EWS access is restored.
$true Microsoft honors an explicitly configured $true value and does not change it to $false during the rollout. However, the setting alone no longer determines access. If the App ID allow list is empty, all EWS access will be blocked. If the list is populated, only the applications on it can use EWS, which is already true before this date (see Step 2).
$false EWS remains blocked.
Swipe to show more of the table
Action required: Explicitly set EwsEnabled to $true now

Run the following PowerShell command against the Exchange Online tenant to check the current value first:

Get-OrganizationConfig | Format-List EwsEnabled

If the current value is anything other than $true, run the following command to set the value to $true:

Set-OrganizationConfig -EwsEnabled $true

Setting this explicitly to $true before October 1 protects your tenant from the automatic $null → $false conversion and gives you control over the transition timeline.

Step 2: Manage your EWS App ID allow list

Microsoft has introduced EWSAllowedAppIDs, an allow list that controls which Entra ID app registrations are permitted to use EWS. The allow list takes effect as soon as it contains at least one entry. When EwsEnabled is set to $true and the list is populated, only the applications on that list can make EWS calls.

What changes starting October 1, 2026? An empty EWSAllowedAppIDs list will cause all EWS access to be blocked, even if EwsEnabled is set to $true.

Veeam's App IDs must therefore be included the first time the allow list is populated. Populating the list without them will block Veeam backups immediately, before October 1, 2026.

Will Microsoft populate this list for me?

Yes — Microsoft will automatically pre-populate the EWSAllowedAppIDs allow list based on each tenant's observed EWS usage, but only for tenants where the list has not already been configured. Note that this applies whether your current EwsEnabled value is $null or $true.

However, Microsoft recommends that admins create and validate their own list rather than relying on automatic population. The automatically populated list may include apps you are no longer aware of or wish to permit, and you, the admin, are responsible for ensuring the list is correct.

Microsoft's guidance: “Configure or validate the EWSAllowedAppIDs allow list (remember, we said we would populate this for tenants who have not done so, but the admin owns ensuring it's correct).”

What you need to do
  1. Review EWS usage in your tenant.
    • For Veeam Backup for Microsoft 365, open the Organizations view, right-click the Microsoft 365 organization, and select Edit Organization. The Application ID is listed in the application settings. For details, review Using Existing Microsoft Entra Application.
      • As an alternative, the following PowerShell command can be used to pull the current Application ID for a given organization: 
        $org = Get-VBOOrganization -Name "Org_Name"
$org.Office365ExchangeConnectionSettings.ApplicationId
    • For Veeam Data Cloud for Microsoft 365 use the EWS Usage Reports in Microsoft 365 Admin Center to identify App IDs currently making EWS calls.
    Note: For Veeam Data Cloud for Microsoft 365 customers, an automated way to enable EWS access is available. See Step 3.
  2. Ensure Veeam's App IDs are on the allow list. Veeam app registrations must be included so that backups can continue using EWS during the period before the Microsoft Graph transition is complete.
  3. Review and remove any app IDs you no longer need. This is a good opportunity to clean up stale registrations.

The allow list is configured in Exchange Online and is documented by Microsoft. Before making any changes, review Introducing EWSAllowedAppIDs: Preparing for the Final Phase of EWS Retirement, which provides the commands for viewing and setting the list, how to add an entry without discarding the entries already there, and how long a change takes to apply.

Step 3: Take action in your Veeam product

Veeam Data Cloud for Microsoft 365

Both actions below are performed in the Veeam Data Cloud portal. Completing either action requires authenticating against Microsoft 365 with an account that has the Global Administrator role.

  1. On the Microsoft 365 page, click the name of the tenant you want to manage.
  2. Select Settings.
  3. Go to the Microsoft 365 tab.
  4. In the EWS Access section, click Enable EWS access. For details, review Enabling EWS Access.
  5. In the Reauthorize Veeam Data Cloud section, click Reauthorize existing app registration. This grants the Microsoft Graph permissions needed for the transition. For details, review Reauthorizing Veeam Data Cloud for Microsoft 365.
  6. Repeat these steps for each Microsoft 365 tenant protected by Veeam Data Cloud.
Veeam Backup for Microsoft 365

Ensure the required Microsoft Graph permissions are assigned to your Veeam app registrations in Microsoft Entra ID:

Ensure EWS access is enabled, as described in Step 1: Keep EWS enabled in your tenant and Step 2: Manage your EWS App ID allow list.

An updated product release supporting the full EWS-to-Graph transition is in development. You will need to upgrade to that release when it becomes available.

Summary Checklist

Action Veeam Data Cloud for M365 Veeam Backup for M365
Manually configure access
Set EwsEnabled = $true in PowerShell Do now Do now
Review Veeam App IDs and validate App ID allow list Before Oct 1 Before Oct 1
Add Veeam App IDs to EWSAllowedAppIDs Before Oct 1 Before Oct 1
Add Microsoft Graph permissions in Entra ID Not applicable Do now
Upgrade to updated product release Not applicable When available
Automatically configure access
Reauthorize app in Veeam Data Cloud portal Do now Not applicable
Enable EWS access in VDC portal When available Not applicable
Swipe to show more of the table

More Information

Restoring access

If EWS is turned off for your tenant before you have completed the steps above, whether because your EWSEnabled was $null at the October 1 cutover, or for any other reason, you can restore access manually:

Set-OrganizationConfig -EwsEnabled $true

After re-enabling, ensure your Veeam App IDs are included in the EWSAllowedAppIDs allow list before backups will resume successfully. See also KB4796 for guidance on EWS access control at the organization and mailbox level.

Impact on backups

Once EWS access is blocked for your tenant, Exchange Online mailbox backups will fail. You can still restore access and add the required permissions, and backups will then resume, but:

  • The first backup job will perform a full sync, which is slower than a normal incremental run but uses the same amount of storage.
  • Any mailboxes not backed up during the gap will have a missing coverage window in their restore history.

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.

]]> <![CDATA[Build Numbers and Versions of Veeam Plug-In for KubeVirt]]> https://www.veeam.com/kb4914 2026-09-08T00:00:00Z 2026-09-08T00:00:00Z

Build Numbers and Versions of Veeam Plug-In for KubeVirt

KB ID: 4914
Product: Veeam Backup & Replication
Published: 2026-09-08
Last Modified: 2026-09-09
This KB article lists all versions of the Veeam Plug-In for KubeVirt and their respective worker build numbers.
Version Plug-In / Worker Build Release Date
Veeam Plug-In for KubeVirt 1 Releases
Veeam Plug-In for KubeVirt 1.0
Independent Plug-In Release		 13.1.0.428 2026-09-08
Swipe to show more of the table

Independent Plug-In releases are available in the My Account portal:

My Account > My Products > Additional downloads > Virtualization Plug-ins

The additional downloads section is at the very bottom of the My Products page.

Note: Veeam Plug-In for KubeVirt may also be listed as Veeam Plug-In for Red Hat OpenShift Virtualization.

Related Articles

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.

]]> <![CDATA[How to Disable the Automatic Installation of Security Updates When Adding a Veeam Infrastructure Appliance to Veeam Backup & Replication]]> https://www.veeam.com/kb4916 2026-09-08T00:00:00Z 2026-09-08T00:00:00Z

How to Disable the Automatic Installation of Security Updates When Adding a Veeam Infrastructure Appliance to Veeam Backup & Replication

KB ID: 4916
Product: Veeam Backup & Replication | 13.1
Published: 2026-09-08
Last Modified: 2026-09-08

Purpose

By default, when a new Veeam Infrastructure Appliance is added to the Veeam Backup & Replication infrastructure, all available security updates are installed on that appliance automatically by the Veeam Updater running on it. The installation of updates can take a significant amount of time, during which the wizard used to add the appliance is blocked, and the appliance is rebooted automatically at the end of the process if a reboot is required.

In environments where the appliance has no access to the Veeam software repositories, the update check cannot succeed, and the wizard is delayed until the check has exhausted its retries, which takes approximately three minutes by default.

This article describes how to disable the automatic update check and installation for Veeam Infrastructure Appliance hosts that are being added to the Veeam Backup & Replication infrastructure.

The setting described in this article is available in Veeam Backup & Replication 13.1.0.411 and later.

Solution

Security Impact of Disabling the Update Check

When the automatic update check is disabled, security updates are not installed on Veeam Infrastructure Appliance hosts while they are being added to the infrastructure. Updates must then be installed on each appliance separately, either through the Veeam Updater on that appliance or through a centralized update mirror. Review How Updates Work in the User Guide before this setting is applied.

Windows-based Veeam Backup & Replication

On the Veeam Backup Server, the following registry value must be created. A restart of the Veeam Backup & Replication services is not required after the value is created.

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
Value Name: SkipInfrastructureApplianceUpdateCheck
Value Type: DWORD (32-Bit) Value
Value Data: 1

PowerShell Registry Value Creation

New-ItemProperty -Path 'HKLM:\SOFTWARE\Veeam\Veeam Backup and Replication\' -Name 'SkipInfrastructureApplianceUpdateCheck' -Value "1" -PropertyType DWORD -Force

Veeam Software Appliance

On Veeam Backup & Replication deployed as a Veeam Software Appliance, the equivalent setting is stored in the /etc/veeam/veeam_backup_and_replication.conf configuration file. That file must be exported from the Veeam Host Management Console, modified, and then imported again, as described in KB4779: Applying Custom Settings to Veeam Software Appliance.

Add the following line to the [root] section of the configuration file. A restart of the Veeam Backup & Replication services is not required after the line is added.

SkipInfrastructureApplianceUpdateCheck=1

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.

]]> <![CDATA[Applications Restored by Veeam Kasten Disaster Recovery Fail to Export with: invalid repository password]]> https://www.veeam.com/kb4910 2026-09-04T00:00:00Z 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.

  1. Confirm that the Veeam Kasten for Kubernetes instance is running version 9.0.5 or later.
  2. 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: <cluster-id>
  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: <KastenDRReview Name>
      namespace: kasten-io
    id: <KDR Restore Point ID from KastenDRReview RestorePointList>
  forceReimportAppRestorePoints: true
  1. Run the KDR restore as described in Recovering Veeam Kasten from a Disaster via CLI.
  2. 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.

]]> <![CDATA[Release Information for Veeam Service Provider Console 9 and Updates]]> https://www.veeam.com/kb4788 2026-09-04T00:00:00Z 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

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:

  1. Back up the Veeam Service Provider Console configuration database.
  2. Log off from all active Veeam Service Provider Console Portal sessions.
  3. 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.isoSHA256: 931553A86DE4478A726AC0E59313D894BB21FA7B35817B1C1873EAB099F8887B Initial Release
2026-07-29 VeeamServiceProviderConsole_9.3.0.35057_20260726.isoSHA256: C2B0CE5B3B537912656A861044CAA46EAAE0A3DF50FAB585BF3A4BBAAE656F13 Initial Release
2026-05-27 VeeamServiceProviderConsole_9.2.1.33875_20260522.isoMD5: BA48514257C225215826F7D0DDEE83F1
SHA1: 77A8DAB3E4F00D9D058BA3EDFB3121DAC827604B		 Initial Release
2026-04-09 VeeamServiceProviderConsole_9.2.0.33215_20260408.isoMD5: A816199DD6BB4244DDFBE3D7C1E1D99A
SHA1: 9D3F44309101B0FA66CD66E6BFB70FB05747E98D		 Initial Release
2025-12-05 VeeamServiceProviderConsole_9.1.0.30713_20251203.isoMD5: B9467A75C0BA2C97EFB22721E2D16903
SHA1: A26FF0E9E67B9F7039801BE6464E9F910B9431F9		 Initial Release
2025-11-19 VeeamServiceProviderConsole_9.1.0.30636_20251117.isoMD5: 261685F88D51204A80DF7E8201485C60
SHA1: 89662902E2479984AD778FB9ADD88E2B7D6913E0		 Initial Release
2025-11-07 VeeamServiceProviderConsole_9.1.0.30345_20251105.isoMD5: 91CEEECE2621D0D4D06E1D7836876E72
SHA1: 07F7000843E652D89F3D9388047F0742858E02F6		 Initial Release
2025-10-21 VeeamServiceProviderConsole_9.0.0.29860_20251020.isoMD5: 0821F41C556E45902913BDB5EAF261AC
SHA1: E198ACBF385674346A4053CC4D6D2BB20D3E8AD4		 Initial Release
2025-09-03 VeeamServiceProviderConsole_9.0.0.29555.isoMD5: 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.

]]>