Veeam Support Knowledge Base https://www.veeam.com/services/open/kb/rss-feed 2026-04-09T17:01:25Z Veeam Software <![CDATA[Release History for Veeam Service Provider Console 9]]> https://www.veeam.com/kb4788 2026-04-09T00:00:00Z 2026-04-09T00:00:00Z

Release History for Veeam Service Provider Console 9

KB ID: 4788
Product: Veeam Service Provider Console | 9 | 9.1 | 9.2
Published: 2025-10-21
Last Modified: 2026-04-09

Veeam Service Provider Console 9 Builds

9.2.0.33215 (9.2 GA)

Release Information

9.1.0.30713

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)

Release Information

9.1.0.30345 (9.1 RTM)

Release Information

9.0.0.29860

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

Release Information

Download Information

Deployment Guidance

Deployment ISO

DOWNLOAD latest 9.2 ISO

See the 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[Build Numbers and Versions of Veeam Service Provider Console]]> https://www.veeam.com/kb4464 2026-04-09T00:00:00Z 2026-04-09T00:00:00Z

Build Numbers and Versions of Veeam Service Provider Console

KB ID: 4464
Product: Veeam Service Provider Console | 4.0 | 5.0 | 6.0 | 7.0 | 8.0 | 8.1 | 9 | 9.1 | 9.2
Veeam Availability Console | 2.0 | 2.0_U1 | 3.0
Published: 2023-06-16
Last Modified: 2026-04-09

This KB article lists all versions of Veeam Service Provider Console and their respective build numbers.

For more information on downloading the latest version of Veeam Service Provider Console, visit:

Note: Prior to version 4, the product was known as Veeam Availability Console.
Note: Prior to version 2, the product was known as Veeam Managed Backup Portal.
Version Build Number Release Date Release Notes Product Guides
Veeam Service Provider Console 9 Releases
Veeam Service Provider Console 9.2 9.2.0.33215 2026-04-09 HTML  
Veeam Service Provider Console 9.1 Patch 1 9.1.0.30713 2025-12-05 KB4788  
Veeam Service Provider Console 9.1 GA 9.1.0.30636 2025-11-19 HTML  
Veeam Service Provider Console 9.1 RTM 9.1.0.30345 2025-11-07 KB4788  
Veeam Service Provider Console 9 CP1 9.0.0.29860 2025-10-21 KB4788  
Veeam Service Provider Console 9 9.0.0.29555 2025-09-03 HTML HTML
Veeam Service Provider Console 8 Releases
Veeam Service Provider Console 8.1 CP1 8.1.0.21999 2024-12-03 KB4651 HTML
Veeam Service Provider Console 8.1 8.1.0.21377 2024-08-28 HTML
KB4651
Veeam Service Provider Console 8 CP2 8.0.0.19552 2024-05-28 KB4509 HTML
Veeam Service Provider Console 8 CP2 (Note)This build was retracted and rereleased as build 8.0.0.19552. For more information review KB4509. 8.0.0.19236 2024-05-06
Veeam Service Provider Console 8 CP1 8.0.0.18054 2024-03-04
Veeam Service Provider Console 8 8.0.0.16877 2023-12-05 PDF ZIP
Veeam Service Provider Console 7 Releases
Veeam Service Provider Console 7 P20240516 7.0.0.19551 2024-05-28 KB4441 -
Veeam Service Provider Console 7 P20240412 7.0.0.18899 2024-05-06
Veeam Service Provider Console 7 P20230531 7.0.0.14271 2023-06-05
Veeam Service Provider Console 7 P20230321 7.0.0.13157 2023-03-21
Veeam Service Provider Console 7 GA 7.0.0.12777 2023-01-30 PDF -
Veeam Service Provider Console 6 Releases
Veeam Service Provider Console 6 Patch 1 6.0.0.8787 2022-02-02 KB4277 -
Veeam Service Provider Console 6 GA 6.0.0.7739 2021-09-27 PDF

KB4212		 -
Veeam Service Provider Console 5 Releases
Veeam Service Provider Console 5 Patch 4 5.0.0.7151 2021-10-12 KB4223 -
Veeam Service Provider Console 5 Patch 3 5.0.0.6959 2021-05-22 KB4163 -
Veeam Service Provider Console 5 Patch 2 5.0.0.6883 2021-03-25 KB4127 -
Veeam Service Provider Console 5 Patch 1 5.0.0.6838 2021-03-03 KB4116 -
Veeam Service Provider Console 5 GA 5.0.0.6726 2021-02-24 PDF

KB4111		 -
Veeam Service Provider Console 4 Releases
Veeam Service Provider Console 4 Patch 2 4.0.0.4914 2020-07-23 KB3237 -
Veeam Service Provider Console 4 Patch 1 4.0.0.4911 2020-07-03 KB3211 -
Veeam Service Provider Console 4 GA 4.0.0.4877 2020-03-31 PDF

KB3040		 -
Veeam Availability Console 3 Releases
Veeam Availability Console 3 Patch 4 3.0.0.2795 2020-01-23 KB3036 -
Veeam Availability Console 3 Patch 3 3.0.0.2762 2019-09-20 KB3003 -
Veeam Availability Console 3 Patch 2 3.0.0.2725 2019-06-17 KB2960 -
Veeam Availability Console 3 Patch 1 3.0.0.2703 2019-04-11 KB2934 -
Veeam Availability Console 3 GA 3.0.0.2647 2019-03-28 PDF -
Veeam Availability Console 2 Update 1 Releases
Veeam Availability Console 2 U1 Patch 1913 2.0.2.1913 2018-12-21 KB2835 -
Veeam Availability Console 2 U1 Patch 1850 2.0.2.1850 2018-11-15 KB2795 -
Veeam Availability Console 2 U1 Patch 1824 2.0.2.1824 2018-10-05 KB2781 -
Veeam Availability Console 2 U1 Patch 1817 2.0.2.1817 2018-08-30 KB2715 -
Veeam Availability Console 2 U1 Patch 1807 2.0.2.1807 2018-07-30 KB2694 -
Veeam Availability Console 2 U1 GA 2.0.2.1750 2018-06-19 PDF -
Veeam Availability Console 2 Releases
Veeam Availability Console 2 Cumulative Patch 1376 2.0.1.1376 2017-12-21 KB2418 -
Veeam Availability Console 2 GA 2.0.1.1319 2017-11-14 PDF -
Veeam Managed Backup Portal 1 Releases
Veeam Managed Backup Portal 1 1.0.0.295 2016-03-24 - -
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[How to Configure krb5.conf for Cross-Domain Hyper-V Cluster Management]]> https://www.veeam.com/kb4841 2026-04-01T00:00:00Z 2026-04-01T00:00:00Z

How to Configure krb5.conf for Cross-Domain Hyper-V Cluster Management

KB ID: 4841
Product: Veeam Backup & Replication | 13
Published: 2026-04-01
Last Modified: 2026-04-01

Purpose

This article documents how to configure the /etc/krb5.conf file on the Veeam Software Appliance (VSA) to enable Kerberos authentication when managing a Microsoft Hyper-V cluster whose nodes belong to a different Active Directory domain than the backup server.

As noted in the VBR 13 User Guide — Before You Begin (Hyper-V):

  • [For Linux-based backup servers] Both the Hyper-V nodes and the backup server must be joined to the same Active Directory domain. If they are not joined to the same Active Directory domain, additional manual configuration of the krb5.conf file is required.

Cause

Linux uses /etc/krb5.conf to determine which Key Distribution Center (KDC) to contact when requesting Kerberos tickets. If the VSA and Hyper-V cluster nodes are in different AD domains and the [realms] section of krb5.conf does not contain entries for those domains, Kerberos authentication will fail when Veeam Backup & Replication attempts to connect to the cluster.

For more information, please reference the krb5.conf documentation.

Solution

  1. Export the existing /etc/krb5.conf file using the Host Configuration file manager.
  2. Edit the downloaded krb.conf file and update the [realms] section to include an entry for each AD domain containing Hyper-V cluster nodes:

    Example
[realms]
 EXAMPLE1.COM = {
     kdc = kerberos.example1.com
 }
 EXAMPLE2.COM = {
     kdc = kerberos.example2.com
 }

Replace the following placeholders:

  • EXAMPLE1.COM, EXAMPLE2.COM — the fully qualified domain names (in uppercase) of the AD domains containing the Hyper-V cluster nodes.
  • kerberos.example1.com, kerberos.example2.com — the DNS-resolvable hostnames or IP addresses of the KDC servers for the respective domains. By default, the KDC is the domain controller.
  1. Review krb5.conf documentation to determine if the [domain_realm] section or the default_realm option need configured for your environment.
  2. Once the krb5.conf file is updated, use the Import button in the Host Configuration file manager to import it into the VSA.

    Note:     If the Security Officer role is enabled, the import will require veeamso approval.

More Information

An additional factor that can contribute to KDC lookup failures is that Linux DNS resolution queries only the first three DNS servers listed in /etc/resolv.conf. Critically, Linux falls over to the next DNS server only if the previous one times out or returns a hard failure. DNS server failover will not occur if the DNS lookup returns an NXDOMAIN ("host does not exist") response. If the primary DNS server returns NXDOMAIN for a KDC hostname, the query fails even when other DNS servers could resolve it.

To test DNS resolution, enable SSH on the VSA via the Host Management Console, then SSH into the VSA and test the resolution of each realm's KDC server.

nslookup kerberos.example1.com
nslookup kerberos.example2.com

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[The HTTP request was forbidden with client authentication scheme]]> https://www.veeam.com/kb4796 2026-04-01T00:00:00Z 2026-04-01T00:00:00Z

The HTTP request was forbidden with client authentication scheme

KB ID: 4796
Product: Veeam Data Cloud for Microsoft 365
Veeam Backup for Microsoft 365
Published: 2025-11-25
Last Modified: 2026-04-08

Challenge

Microsoft 365 backups display the following error:

The HTTP request was forbidden with client authentication scheme 'Anonymous'.

This error typically occurs when specific mailboxes are accessed during backup jobs.

Cause

It was confirmed on March 27th, 2026, that Microsoft recently applied a patch to correct how Exchange Online enforces Exchange Web Services (EWS) access. Previously, some environments were able to access mailboxes via EWS even when it was not explicitly enabled (i.e., $Null status). After Microsoft corrected this behavior, EWS must now be explicitly enabled at both the organization and mailbox levels for backups to succeed.

For more information, please reference: The way to control EWS usage in Exchange Online is changing


For details about the occurrence of this issue from December 2025, please refer to the More Information section at the bottom of this article.

Solution

Microsoft provides training resources for utilizing PowerShell to manage Exchange Online:
Microsoft Learning Center: Manage Exchange Online by using Windows PowerShell

To address the root cause of the problem, confirm and configure EWS access to be explicitly enabled at both the organization and mailbox level:

  1. Review the EWS enablement status at both the Organization and Mailbox level using the following PowerShell commands:
#Get the organization's EwsEnabled state.
Get-OrganizationConfig | Fl EwsEnabled
#Get all mailboxes where EwsEnabled state is not set to $true.
Get-CASMailbox -ResultSize Unlimited | Where-Object { $_.EwsEnabled -ne $true } | Select-Object Identity, PrimarySmtpAddress, EwsEnabled
  1. If the output results for either org or mailbox are anything other than an explicit True, access via EWS must be enabled using the following commands:
#Set the organization's EwsEnabled state to $true.
Set-OrganizationConfig -EwsEnabled $true
#Bulk set EwsEnabled to $true for all mailboxes where it is not already set to $true.
Get-CASMailbox -ResultSize Unlimited | Where-Object { $_.EwsEnabled -ne $true } | Set-CASMailbox -EwsEnabled $true
If preferred, mailboxes may be individually modified using the following command: 
#Granularly set a single mailbox's EwsEnabled state to $true
Set-CASMailbox mailbox@address.com -EwsEnabled $true
  1. Wait. The new values may take up to 24 hours to replicate and take effect.
  2. Re-check the backup job again

More Information

Similar Issue from December 2025

Challenge

Microsoft 365 backups display the following error:

The HTTP request was forbidden with client authentication scheme 'Anonymous'.

This error typically occurs when specific mailboxes are accessed during backup jobs.

Cause

Following a coordinated investigation with Microsoft, we have confirmed that certain subscription plans, such as Exchange Online Kiosk and similar limited-service SKUs, may not support the API required by Veeam Backup for Microsoft 365.

As a result, calls to the API return an HTTP 403 Forbidden error, causing backup jobs to fail.

Solution

Status: This issue is resolved as of December 2025.
Issue Root Cause: Mailboxes licensed with Exchange Online Kiosk, Microsoft 365, and Office 365 F1, and Microsoft 365 and Office 365 F3, were temporarily blocked from accessing the API used by Veeam for backup operations. The access has been restored, and the issue has been resolved.

For more information, please refer to the following Microsoft article: Update to EWS Access for Kiosk / Frontline Worker Licensed Users.

Veeam R&D continues to work closely with Microsoft on the upcoming deprecation of the EWS API. A future update will address these changes. A Veeam Support Statement regarding EWS deprecation is available on KB4820.

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 Fsas ETERNUS Plug-In for Veeam Backup & Replication]]> https://www.veeam.com/kb4043 2026-04-01T00:00:00Z 2026-04-01T00:00:00Z

Release Information for Fsas ETERNUS Plug-In for Veeam Backup & Replication

KB ID: 4043
Product: Veeam Backup & Replication | 12.3 | 12.3.1 | 12.3.2 | 13
Published: 2020-11-06
Last Modified: 2026-04-02
This plug-in leverages the Veeam Universal Storage API, which enables storage OEMs to allow Veeam Backup & Replication integration to the arrays for backup and replication jobs.

Requirements

Before installing Fsas ETERNUS Plug-In v1.3, ensure that you are running Veeam Backup & Replication 12.3.0.310 or higher. You can check the installed build number in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.

ETERNUS Plug-In v1.3 supports integration with the following storage systems:

  • ETERNUS AF S2 and DX S4 series (except DX8900 S4): V10L88-1000 or later
  • ETERNUS AF S3 and DX S5 series, DX8900 S4: V11L30-5000 or later
  • ETERNUS DX S6 series: V12L10-0000 or later

Additional Requirements and Considerations

  • For Fsas ETERNUS storage systems, a Veeam Storage Integration license must be installed on the storage system. The Veeam Storage Integration license is available free of charge from the Fsas website.
  • The ETERNUS storage plug-in will not work when the FIPS policy is enabled on the Veeam Backup Server.

What's New

  • This update is a rebranded version of the Fujitsu Plug-In for Veeam Backup & Replication.

Download Information

DOWNLOAD ETERNUS Plug-In

Updated: 2026-04-01

MD5: C1E25DF14A4D207723A1BCBB43CEA84E
SHA1: 92A180AA590ABBD39D2C3DD31BE6508BDD49BAF7

Previous Versions

Fujitsu Plug-In for Veeam Backup & Replication [1.2.2] 2025-12-02
  • Updated setup package to enable installation on Veeam Backup & Replication v13.0.1.
    Please also install this version if you are unable to remove the earlier plug-in version after upgrading to v13.0.1.
     
Fujitsu Plug-In for Veeam Backup & Replication [1.1.3] 2024-01-29
  • This update resolves the most common Storage Cluster configuration support issues.
     
Fujitsu Plug-In for Veeam Backup & Replication [1.1.3] 2023-02-28
  • Added support for snapshots on replicated volumes.
  • Added support for multiple VLAN's.
  • This update also resolves the most common support issues.

 

Fujitsu Plug-In for Veeam Backup & Replication [1.0.10] 2019-05-14
  • Initial plug-in version

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[Guest processing fails for Nutanix AHV, Proxmox VE, Scale Computing HyperCore]]> https://www.veeam.com/kb4842 2026-03-31T00:00:00Z 2026-03-31T00:00:00Z

Guest processing fails for Nutanix AHV, Proxmox VE, Scale Computing HyperCore

KB ID: 4842
Product: Veeam Backup & Replication | 13
Veeam Backup for Nutanix AHV | 9
Veeam Plug-In for Proxmox VE | 3
Published: 2026-03-31
Last Modified: 2026-04-06

Challenge

When running backup or replication jobs for Windows virtual machines hosted on Nutanix AHV, Proxmox VE, or Scale Computing HyperCore with Veeam Backup & Replication 13.0.1 Patch 2, guest processing fails with one of the following errors:

Failed to install guest processing components for [VM name]. Error: Failed to connect to the guest OS.

or

Failed to prepare guest for hot backup. Error: Cannot start service. Machine: [IP address]. Service: [VeeamGuestHelper]. Cannot start service. Win32 error: The service did not respond to the start or control request in a timely fashion. Code: 1053
Backup job summary showing failed status for both "ubu" and "SQL" entities, with errors indicating failure to prepare the guest for hot backup and failure to install guest processing components due to being unable to start the VeeamGuestHelper service.

Cause

This issue occurs due to an in-guest processing component that may be assigned an invalid port value, preventing it from initializing.

Solution

Potential Conflict with Existing Private Hotfixes

If you have already installed another private hotfix, contact Veeam Support before installing this hotfix to confirm there are no conflicts.

Private hotfixes replace core product files (e.g., .dll and .exe). If multiple private hotfixes modify the same file, installing one can overwrite changes from another and cause unexpected behavior.

For Windows-based Veeam Backup & Replication Deployment

Install the private fix provided below.

Note: This fix applies only to Veeam Backup & Replication build 13.0.1.2067. Verify your build number under Help > About before proceeding.

  1. Ensure no backup, replication, or restore sessions are currently running.
  2. Close Veeam Backup & Replication Console on all machines where it is open.
  3. On the Veeam Backup & Replication server, execute the private fix file as an Administrator.
  4. Follow the on-screen prompts to complete the installation.
  5. Reopen the console and confirm that guest processing completes successfully for the affected VMs.
Download Private Fix

Filename: KB4842_20260331_VBR_13.0.1.2067_PF1309581.zip

MD5: 6CD1901BA27D3AEA60A2D7CA979912DA
SHA1: 1393D67F506D6ABADE2314263A4288109B04205F
SHA256: 6EE196110E96EF50E6F4B7C53A31AC87826272589DADE166F501C9C33A1DB241

For Veeam Software Appliance

Install the private fix provided below.

Note: This fix applies only to Veeam Backup & Replication build 13.0.1.2067. Verify your build number under Help > About before proceeding.

  1. Ensure no backup, replication, or restore sessions are currently running.
  2. Install the private hotfix.
    (See Install Private Hotfixes for more information.)
  3. Confirm that guest processing completes successfully for the affected VMs.
Download VSA Private Hotfix

Filename: vbr-pf-bundle-1309581-1616154.zip

MD5: D278805D915E1ACA7E4DAEB6B5FA96F8
SHA1: D2ECE4E443988AE9E586568F1CD559CDEAEE205A
SHA256: 98D649584D01F3215755CA7AA768700D58FDAA049BB245E0E1AB538AADFE1401

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[Malware and Ransomware Detection in M365]]> https://www.veeam.com/kb4838 2026-03-31T00:00:00Z 2026-03-31T00:00:00Z

Malware and Ransomware Detection in M365

KB ID: 4838
Product: Veeam Data Cloud for Microsoft 365
Published: 2026-03-31
Last Modified: 2026-03-31
Availability Requirement
Threat Detection is available to Veeam Data Cloud for Microsoft 365 customers with Premium or Advanced plans. Customers must opt in to AI settings to enable this feature. Contact your Veeam account team or see your plan details to confirm availability.
Supported Workloads
This feature currently supports Microsoft 365 workloads only.

Purpose

This article describes how to locate, review, and interpret Malware and Ransomware threat detections surfaced by Veeam Data Cloud (VDC) Advanced Threat Detection for Microsoft 365 workloads.

When Veeam Data Cloud backs up Microsoft 365 data, it automatically analyzes each backup for security threats. It then flags infected files (malware) and suspicious encryption patterns (ransomware). Detected threats are surfaced in the Threats section of the Microsoft 365 workload view in the VDC portal.

How Threat Detection Works

VDC Advanced Threat Detection runs automatically after each backup job completes. It does not scan file content directly, and detection is based entirely on file metadata, behavioral signals, and machine learning analysis of backup statistics.
Threat Type Detection Method Data Source What Is Detected

Malware

 Deterministic
(rule-based)		 Microsoft's built-in malware detection Known malware signatures in OneDrive, Teams, and SharePoint files flagged during a backup session.
Ransomware Machine Learning
(Random Cut Forest)		 Backup file statistics (entropy, extension changes, modification patterns) Anomalous encryption patterns, unusual file extension changes, and entropy spikes deviating from the established baseline per workload.
Swipe to show more of the table
Privacy-Preserving Architecture
VDC Threat Detection analyzes metadata only. File content is never accessed, transmitted, or stored outside your backup environment. All data remains within your deployment region.

Solution

Navigate to the Threats View

In the Veeam Data Cloud (VDC) portal, select Microsoft 365 from the left navigation panel, and in the Management section, click Threats.

The threats page contains two tabs:

  • Malware Threats — A list of users whose OneDrive, Teams, or SharePoint files were flagged as containing malware during a backup session.
  • Ransomware Threats — A list of resources where anomalous encryption activity was detected.
Microsoft 365 Threat Detection dashboard with tabs for Malware Threats and Ransomware Threats, showing a list of malware threats for several entities in OneDrive.
Ransomware Threats tab in the Microsoft 365 Threat Detection dashboard displaying a list of ransomware threats, with one entry for the M8 Project site and its status as resolved.
The lists are sorted by most recent occurrence by default. Use the All Time date filter to scope results to a specific time range.

Investigate a Malware Threat

Click on any row in the Malware Threats tab, click the ⋯ action menu, then select View Details to open the Malware Threat Details panel.

Malware Threats tab in the Microsoft 365 Threat Detection dashboard showing a list of OneDrive entities with resolved malware threats, and the Actions menu is highlighted for one entry.
Understanding the Malware Threat Fields
  • Entity Name: The Microsoft 365 object name of the infected files.​
  • Resource Type: The Microsoft 365 resource type where the threat was found (e.g., OneDrive, SharePoint).
  • Number of Impacted Objects: Total count of files flagged as malware within the backup session.
  • Status: The current lifecycle state of the threat, which could be Active or Resolved​.
  • Resolved By: The user who resolved the threat in the Veeam Data Cloud platform. Keep in mind, the resolution of a threat happens off-platform.​
  • Date of Occurrence: The timestamp of the backup session during which infected files were detected.
    Note: This represents the date of detection, not the date of actual infection.
  • Resolved Date: The timestamp when the user clicked "Resolved" in the Veeam Data Cloud platform.​
Malware Threat Details window showing information for a OneDrive entity, including resolved status, number of impacted objects, and a table listing infected file names, locations, created dates, and updated dates.
Understanding the Malware Threat Details Fields
  • Explanation: A plain-language summary of the detection event.​
  • File Name: Name of the infected file.​
  • File Location: Full URL to the file.​
  • File Created Date: Timestamp of when the file was created.​
  • File Updated At: Timestamp for when the file was last modified.​
  • Resolve Button: Updates the status of the threat in the Veeam Data Cloud platform to "Resolved".​​
Detection Source
Malware detection for Microsoft 365 is powered by deterministic signals from Microsoft's built-in malware detection. This means detection accuracy is consistent with Microsoft's own malware protection layer.

Investigate a Ransomware Threat

Click the Ransomware Threats tab to see detections based on anomalous backup behavior. Ransomware detections are scoped at the site or resource level rather than the individual user level.

Ransomware Threats tab in the Microsoft 365 Threat Detection dashboard displaying a list of ransomware threats, with one entry for the M8 Project site and its status as resolved.
Understanding the Ransomware Threat Fields
  • Entity Name: The Microsoft 365 object name of the infected files.​
  • Resource Type: The Microsoft 365 resource type where the threat was found (e.g., SITE).
  • Number of Impacted Objects: Total count of files flagged as malware within the backup session.
  • Status: The current lifecycle state of the threat, which could be Active or Resolved.
  • Resolved By: The user who resolved the threat in the Veeam Data Cloud platform. Keep in mind, the resolution of a threat happens off-platform.​
  • Date of Occurrence: The timestamp of the backup session during which infected files were detected.
    Note: This represents the date of detection, not the date of actual infection.
  • Resolved Date: The timestamp when the user clicked "Resolved" in the Veeam Data Cloud platform.​
Ransomware Threat Details window for the M8 Project site, showing resolved status, explanation of potential ransomware activity detected, and a table with the impacted file’s name, location, and dates.
Understanding the Ransomware Threat Details Fields
  • Explanation: A plain-language summary of the detection event.​
  • File Name: Name of the infected file.​
  • File Location: Full URL to the file.​
  • File Created Date: Timestamp of when the file was created.​
  • File Updated At: Timestamp for when the file was last modified.​
  • Resolve Button: Updates the status of the threat in the Veeam Data Cloud platform to "Resolved".​​
Ransomware Requires a Baseline Period
The machine learning model (Random Cut Forest) requires approximately 45 days of backup history per workload to establish a reliable behavioral baseline before anomaly detection becomes fully effective. During this period, detection may be limited. New workloads or newly protected tenants will automatically build their baselines during this window.

More Information

Considerations and Limitations

  • Opt-in required: Threat Detection must be explicitly enabled per tenant. It is not active by default due to customer consent requirements for AI-powered features.

  • Microsoft 365 workloads only (current release): Threat Detection currently supports Microsoft 365 (i.e., OneDrive, Teams, and SharePoint).

  • Malware detection relies on Microsoft's built-in malware detection signals: If Microsoft does not flag a file as malware, the Veeam Data Cloud platform will not independently detect it.

  • Ransomware detection requires a 45-day baseline: New workloads or tenants will not have full anomaly detection until the machine learning (ML) model has established a behavioral baseline. During the ramp-up period, low-confidence anomalies may not be surfaced.

  • Ransomware detection is probabilistic: The Random Cut Forest ML model flags statistically anomalous patterns. All detections are labelled as "Potential ransomware activity" and are reviewed by Veeam operators before being marked Active.

  • File content is never accessed: Both malware and ransomware detection operate exclusively on metadata and behavioral statistics. Backup file content is never read, transmitted, or analyzed by the threat detection service.

  • False positives may occur: Legitimate bulk file operations (e.g., large migrations, mass rename events, encryption of files by authorized software) may occasionally trigger a ransomware detection. Veeam operators review these events before escalating to Active status.

  • Data residency: All threat detection data, including file metadata and detection results, is stored in the same Azure region as your Veeam Data Cloud deployment. No data crosses regional boundaries unless explicitly requested by the customer.

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[Potential Issue With Backing up Sharepoint, Onedrive, Teams Files, and List Attachments]]> https://www.veeam.com/kb4835 2026-03-31T00:00:00Z 2026-03-31T00:00:00Z

Potential Issue With Backing up Sharepoint, Onedrive, Teams Files, and List Attachments

KB ID: 4835
Product: Veeam Data Cloud for Microsoft 365
Veeam Backup for Microsoft 365 | 7.0 | 7a | 8 | 8.1 | 8.2 | 8.3
Published: 2026-03-31
Last Modified: 2026-03-31

Challenge

Backup of SharePoint, OneDrive, and Teams data completes successfully, and subsequent restores of this protected data are successful. However, when opening some of the restored files or list attachments, users may find that these items do not open correctly in their associated applications (e.g., Microsoft Word, Excel, PowerPoint, and Adobe Acrobat).

Common errors reported by customers are:

  • “The file is either not a supported file type or has been damaged.”
  • “Word found unreadable content…”
  • “Excel cannot open the file ... because the file format or file extension is not valid.”
  • “Sorry, this document can't be opened for editing.”

The affected files retain their original names and extensions (e.g., .docx, .pdf) but cannot be viewed or edited.

Cause

During backup operations, files, list attachments, or images from SharePoint, OneDrive, or Teams were saved with the contents of the HTML error pages returned by the API, rather than their actual file content.

Veeam first observed this issue in early March 2026.

This issue impacts Veeam Data Cloud for Microsoft 365 and all supported versions of Veeam Backup for Microsoft 365. It is independent of repository type, affecting both JET-based and object storage repositories.

No errors are shown in backup jobs or restore tasks; the issue surfaces only when the user attempts to open the restored file.

Mitigation

Veeam is working expeditiously to resolve this issue with an upcoming release; until that time, all customers are advised to review the following with their technical and governance teams:

  • Avoid deleting and overwriting critical files, and list attachments in the production environment.
  • Temporarily adjust the Microsoft 365 retention and lifecycle policies (e.g., retention labels/policies, auto-expiration, scheduled cleanup) to prevent the removal or permanent deletion of such content, so that it remains in production.

Solution

Veeam Data Cloud for Microsoft 365

No action is required from Veeam Data Cloud for Microsoft 365 users. The platform will be automatically updated to the latest version, fixing the issue.
 

Veeam Backup for Microsoft 365

Veeam is working on a new product version that fixes the root cause of this issue. We will notify you when it becomes available. 

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[External Client App (ECA) for Veeam Data Cloud — Adapting to New Salesforce Security Requirements]]> https://www.veeam.com/kb4812 2026-03-30T00:00:00Z 2026-03-30T00:00:00Z

External Client App (ECA) for Veeam Data Cloud — Adapting to New Salesforce Security Requirements

KB ID: 4812
Product: Veeam Data Cloud for Salesforce
Published: 2026-03-30
Last Modified: 2026-03-31

Support Statement

Summary of Changes to Salesforce Security Protocols

Salesforce has introduced new security protocols for third-party applications accessing Salesforce organizations. This change affects all third-party products that integrate with Salesforce, requiring those vendors to transition from legacy Connected Apps to External Client Apps (ECAs). As part of this shift, organizations using external products for data backup must update their integrations to comply with these new requirements and prepare for the eventual deprecation of Connected Apps.

Introducing the External Client App (ECA) for Veeam Data Cloud

To meet Salesforce’s new security requirements, Veeam has released the External Client App (ECA) for Veeam Data Cloud managed package in February 2026. This package enables customers to securely connect Veeam Data Cloud for Salesforce to their Salesforce organizations, in compliance with Salesforce standards. Upon installation, the package creates an External Client App with the necessary permissions for Veeam Data Cloud to perform backups. It also automates client key and secret rotation, simplifying ongoing security management. Installation of this package is required for each Salesforce organization that will be protected with Veeam Data Cloud before it can be added and backed up.

Existing Veeam Data Cloud for Salesforce Customers

For Salesforce organizations added to Veeam Data Cloud for Salesforce before the Salesforce Winter ’26 release, Salesforce will provide a transition period during which the Connected App can continue to be used. However, all customers are encouraged to transition to the External Client App (ECA) for Veeam Data Cloud managed package and re-authorize their Salesforce organizations in Veeam Data Cloud. This approach ensures integration with Salesforce’s latest security protocols and helps prevent any last-minute changes when the Connected App is eventually deprecated.

Supported Salesforce Editions

The External Client App (ECA) for Veeam Data Cloud managed package is supported for:

  • Salesforce Enterprise
  • Unlimited
  • Developer
  • Professional editions
    Note: API access must be enabled for Professional editions.

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[Support Statement — Exchange Web Services (EWS) Deprecation]]> https://www.veeam.com/kb4820 2026-03-25T00:00:00Z 2026-03-25T00:00:00Z

Support Statement — Exchange Web Services Deprecation

KB ID: 4820
Product: Veeam Data Cloud for Microsoft 365
Veeam Backup for Microsoft 365
Published: 2026-03-25
Last Modified: 2026-03-26

Challenge

Microsoft has announced the deprecation of Exchange Web Services (EWS) in Exchange Online, with the initial phase-out target of October 1, 2026. Veeam Backup for Microsoft 365 and Veeam Data Cloud for Microsoft 365 currently leverage EWS for Exchange Online backup functionality. Veeam software will be updated to ensure continued compatibility and data protection capabilities.

Solution

Veeam product features that currently use EWS will be transitioned to the Microsoft Graph API, ensuring as smooth a migration as possible before the phase-out date.

Users do not need to take any action at this time.

More Information

Should you find that EWS has been turned off for your Microsoft 365 organization before the expected Microsoft EWS phase-out date, you can manually configure EWS access with PowerShell (see Control access to EWS in Exchange). 

Note: The default value for Get-OrganizationConfig -EwsEnabled is $null. We recommend you set this to Set-OrganizationConfig -EwsEnabled $true until the phase-out period to avoid possible service interruptions.

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[Most Common Issues with Salesforce Connected App in Veeam Data Cloud for Salesforce]]> https://www.veeam.com/kb4810 2026-03-25T00:00:00Z 2026-03-25T00:00:00Z

Most Common Issues with Salesforce Connected App in Veeam Data Cloud for Salesforce

KB ID: 4810
Product: Veeam Data Cloud for Salesforce
Published: 2026-01-23
Last Modified: 2026-03-25

Purpose

This article documents the changes to Connected App usage in Veeam Data Cloud for Salesforce resulting from Salesforce’s restriction of uninstalled connected apps, effective Autumn 2025. It provides guidance on authorization requirements, common connection errors, and necessary permissions for successful integration.

Solution

As of Autumn 2025, Salesforce has restricted the use of uninstalled connected apps (see Salesforce article). Due to these changes, customers may encounter errors when connecting a Salesforce organization to Veeam Data Cloud for Salesforce.

When authorizing Veeam Data Cloud in a Salesforce organization, Salesforce automatically creates the Connected App “VDC Salesforce Backup.” The user authorizing the connection must have the “Approve Uninstalled Connected Apps” permission. Without this permission, Salesforce will deny the connection.

Below are common errors that may occur during authorization or re-authorization, with steps to resolve them.

Connected App is not installed

Salesforce error code:

OAUTH_APPROVAL_ERROR_GENERIC
Resolution
  • Ensure the user authorizing the connection has the “Approve Uninstalled Connected AppsFrom Salesforce Documentation: This new user permission is automatically assigned to the System Administrator standard profile. Custom profiles aren’t automatically updated, including those previously cloned from the System Administrator standard profile. After the connected app usage restriction is enforced in September 2025, this user permission grants access to use uninstalled connected apps, bypassing the new usage restriction. It should only be assigned to highly trusted users, such as administrators and those involved in managing or testing connected app integrations. Salesforce recommend using care when assigning this user permission. For example, only grant to admin users and to users who manage connected app integrations and need to test the apps before installing on the org for access by other end users.” permission, then retry the authorization.
  • After the initial authorization attempt, Salesforce will create a connected app named VDC Salesforce Backup. Proceed to the Connected Apps OAuth Usage" page and click Install for the connected app in Salesforce. Then, try to authorize the Salesforce connection once again
  • If this error occurs when connecting a sandbox organization, run “Match Production Licenses to Sandbox without Refresh.”

Connected App is not installed or is blocked

Salesforce error code:

OAUTH_APP_ACCESS_BLOCKED
Resolution
  1. In Salesforce, go to Setup, search for "Connected Apps," and select "Connected Apps OAuth Usage."
  2. Unblock or Install the “VDC Salesforce Backup” Connected App as needed.
The Salesforce Setup page displays the "Connected Apps OAuth Usage" section. The sidebar shows "Connected Apps OAuth Usage" highlighted under Connected Apps. The main panel lists connected apps, including "VDC Salesforce Backup," along with columns for user count, denied attempts due to usage restriction, last denied attempt, and app actions such as "Unblock" and "Install." The search bar at the top left contains the text "Connected Apps."

User authorizing the connection is not approved to use the Connected App

Salesforce error code:

OAUTH_APP_ACCESS_DENIED

This error occurs if the Connected App is configured to allow only admin-approved users.

Resolution
  • Create a custom permission set that grants access to the “VDC Salesforce Backup” Connected App.
  • Assign this permission set to the user who will authorize the connection.
The Salesforce Setup page displays the "Manage Connected Apps" section. The left sidebar shows the search term "Connected Apps" and highlights "Manage Connected Apps" under Apps. The main panel displays details for the connected app "Veeam Backup for Salesforce," including system info, basic information, and OAuth policies. The "Permitted Users" setting is shown as "Admin approved users are pre-authorized." "Edit Policies" and "Uninstall" buttons are on the right.

"VDC Salesforce Backup" is not allowed to connect to your organization

Salesforce error code:

BAD_REQUEST

This error occurs if "API Access Control" is enabled for the organization.

Resolution
  • Ensure that the VDC Salesforce Connected app is installed.
  • Ensure that the connected app is added to the list of allowed applications under:  Setup > API Access Control

More Information

Additional Information About Authorization Errors

For more information about OAuth 2.0 Authorization errors, please review the Salesforce Help documentation:

 

Regarding the Future of Connected Apps

Starting with the Salesforce Winter '26 release, Salesforce will begin transitioning from Connected Apps to External Client Apps. For more information, please review this Salesforce article: 

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[Search Best Practices in Veeam Data Cloud for Microsoft 365]]> https://www.veeam.com/kb4730 2026-03-25T00:00:00Z 2026-03-25T00:00:00Z

Search Best Practices in Veeam Data Cloud for Microsoft 365

KB ID: 4730
Product: Veeam Data Cloud for Microsoft 365
Published: 2025-06-26
Last Modified: 2026-04-01
New Search Experience for Veeam Data Cloud for Microsoft 365

We are excited to announce the initial rollout of our new search feature, designed to significantly improve the speed and efficiency of your search experience. The new search supports deleted item recovery and restore point search without the overhead of mounting restore points. For details on what's new, see KB4839: New Search Experience for Veeam Data Cloud for Microsoft 365.

Note: The best practices in this article continue to apply to OneDrive and SharePoint search while the new experience is being rolled out to those workloads.

Purpose

This article offers guidance on choosing the best search method in Veeam Data Cloud for Microsoft 365 based on various scenarios.

Solution

Best Practice Summary

  • Start with Basic Search for fast, focused results when you know the relevant keyword and property.
  • Browse Backups when you know where to look or want to manually locate items within a specific backup or restore point.
  • Use Advanced Search as a last resort, for very broad or complex queries, or when you lack enough details for a targeted search.

How to Access Search

  1. Log in to the Veeam Data Cloud for Microsoft 365 portal.
  2. Navigate to the Search section on the dashboard.
    Learn more about search.

Search Options

Basic Search (Recommended)

Basic Search is optimised for speed and simplicity, and best used when you know what you’re looking for.

Basic Search is the fastest and most user-friendly way to find information in your Microsoft 365 backups. Use this option for most scenarios:

  • Outlook: Searches keywords in email subjects.
  • SharePoint: Searches keywords in site names or documents within a site.
  • Teams: Searches keywords in channel chat messages (posts).
  • OneDrive: Searches keywords in file names.

Browsing Backups (Manual Search)

Browsing is effective for targeted restores or when you want to verify backup contents without performing a search.

A technical alternative is to browse through your backups manually. This method lets you directly explore backup content (mailboxes, sites, files, etc.) without using the search interface.

  • How it works: You can open a specific backup or restore point and navigate through its structure (folders, mailboxes, documents, etc.) to find the needed data.
  • When to use: If you know the likely location of the item (e.g., a specific folder or user mailbox), browsing can often be faster and more precise than running a broad advanced search.
  • Benefits: This method avoids the overhead of mounting large restore points or running resource-intensive queries.

Advanced Search (For Complex or Broad Queries)

Advanced Search allows for complex, organisation-wide, or less-specific queries using advanced filters.

  • Use cases: When Basic Search and browsing do not return the needed results, or when you need to search on specific metadata or content across large datasets.
  • Resource note: Advanced Search requires mounting restore points and can take significant time, especially with broad criteria or large backups.

Important: To minimise wait times and system load, use Basic Search or browse backups whenever possible. Reserve Advanced Search for scenarios where other methods are not sufficient.

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[New Search Experience for Veeam Data Cloud for Microsoft 365]]> https://www.veeam.com/kb4839 2026-03-24T00:00:00Z 2026-03-24T00:00:00Z

New Search Experience for Veeam Data Cloud for Microsoft 365

KB ID: 4839
Product: Veeam Data Cloud for Microsoft 365
Published: 2026-03-24
Last Modified: 2026-04-10

Purpose

We are excited to announce the initial rollout of our new search feature, designed to significantly improve the speed and efficiency of your search experience. Below are the details and important limitations to be aware of during this phased rollout.

What's New

  • Faster Search Experience:
    Our upgraded search engine delivers results much more quickly, ensuring you can find what you need with minimal wait time.
  • Expanded Search for Deleted Items:
    You can now search for deleted items—a capability previously available only in the browse experience.
    Important limitation:
    • You’ll be able to search for deleted items only from one month prior to the feature’s release date. Any items deleted before that will not appear in search results.
    • Going forward, all deleted items will be searchable from the time of deletion.
  • Restore Point Search:
    The new search feature allows searching by restore points. 
    Important limitation:
    • Only restore points from up to one month before the initial release will be available in search.
    • All future restore points, created after the rollout, will be fully searchable.
  • Scope of Search (Initial Phase):
    • The first rollout includes email (Exchange) search only.
    • OneDrive and SharePoint search capabilities will be added in the next phase.
  • Email Body Content Search (Initial Limitation):
    • At launch, searching within email body content will not be available. This capability may be added in future updates.

More Information

Frequently Asked Questions

Will I be able to see deleted items in Search?
Yes, but you will only be able to see items deleted after March 31st, 2025, in the new search experience. All deleted items going forward will also be visible in the new search.
When will OneDrive and SharePoint search be available?
These will be included in the next phase of the rollout. Stay tuned for further announcements!
Will I be able to search for the actual content of emails?
Not at this time. Searching within the body of emails is not part of the initial release.

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 Safely Perform Snapshot Rollback of Veeam Backup for Microsoft 365]]> https://www.veeam.com/kb4837 2026-03-24T00:00:00Z 2026-03-24T00:00:00Z

How to Safely Perform Snapshot Rollback of Veeam Backup for Microsoft 365

KB ID: 4837
Product: Veeam Backup for Microsoft 365 | 8 | 8.1 | 8.2 | 8.3
Published: 2026-03-24
Last Modified: 2026-03-25

Purpose

This article provides step-by-step guidance for performing a snapshot rollback of a Veeam Backup for Microsoft 365 deployment in the event of a disaster. 
Critical Warning
Rolling back to a snapshot is a complex and highly risky process that should only be performed in rare disaster situations. This action is reserved for exceptional cases and must not be used as a standard recovery or troubleshooting step in production environments. Incorrect use can lead to serious data, configuration, or repository corruption, or make the system unrecoverable. Always consult Veeam Support before taking this action.

Solution

Supported Versions and Limitations

  • Snapshot Rollback is only supported when used to roll back Veeam Backup for Microsoft 365 between patches within the same major and minor release (e.g., 8.0.2.x to 8.0.2.y).
  • Snapshot Rollback is not supported to rollback between major (e.g., 8.x back to 7.x) or minor versions (e.g., 8.3.0.x back to 8.2.0.x).
     

Prerequisites and Restrictions

  • Before reverting the snapshot:
    • All jobs and restore tasks must be fully stopped and disabled.
    • All NATS streams must be removed/cleaned to avoid metadata conflicts.
    • All Veeam Backup for Microsoft 365 components (controller, proxies, PostgreSQL, and NATS) must be fully shut down.
  • Never connect a PostgreSQL database used with a higher Veeam Backup for Microsoft 365 version to a lower Veeam Backup for Microsoft 365 version — this can cause repository corruption and schema mismatches.

Step-by-Step Rollback Procedure

Part 1: Preparation and Shutdown
  1. Stop all Veeam Backup for Microsoft 365 components:
    • Controller service (Veeam.Archiver.Service)
    • All proxy servers (Veeam.Archiver.Proxy)
    • REST service (Veeam.Archiver.REST.Service)
    • Update service (Veeam.Archiver.Update.Service)
    • PostgreSQL server
    • NATS server
       
Part 2: Environment Drain and NATS Stream Cleanup
  1. Stop and disable all jobs, and ensure all restore tasks have stopped.
  2. Remove or clean all NATS streams.

    For example, delete the contents of the folder:
    C:\ProgramData\Veeam\Backup365\nats\jetstream\$G
     
Part 3: Snapshot Reversion
  1. Revert the environment to the snapshot created prior to the update.

    Tip: If you are reading this article before creating the original snapshot, Veeam recommends stopping all Veeam Backup for Microsoft 365 services before creating that original snapshot.
     
Part 4: Post-Rollback Startup Sequence (Strict Order)
  1. Start the PostgreSQL server.
  2. Start the NATS server (ensure all streams are cleaned up).
  3. Start the Veeam Backup for Microsoft 365 controller service (it will recreate all required NATS streams).
  4. Start the Veeam Backup for Microsoft 365 proxy servers.

    The proxies will perform repository synchronization checks. If any repository contains backups or blobs newer than the reverted metadata, the proxies will detect that repository as out-of-sync.

More Information

Veeam encourages all customers to consult Veeam Support before performing any snapshot rollback of a Veeam Backup for Microsoft 365 server.

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-03-23T00:00:00Z 2026-03-23T00: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
Kasten K10 by Veeam | 4 | 5 | 5.5 | 6 | 6.5
Published: 2026-03-02
Last Modified: 2026-03-23

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 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.

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-03-18T00:00:00Z 2026-03-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
Published: 2018-11-29
Last Modified: 2026-04-09

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.0.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.1 6.12.0-124.49.1.el10_1 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

Uses the blksnap kernel module.
9.0-9.7 5.14.0-611.47.1.el9_7 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

Uses the blksnap kernel module.
8.4-8.10 4.18.0-553.117.1.el8_10 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

Uses the veeamsnap kernel module.
Oracle Linux
10.0-10.1
(RHCK)		 6.12.0-124.49.1.el10_1 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

Uses the blksnap kernel module.
10.0-10.1
(UEK8)		 6.12.0-200.74.27.1.el10uek 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

Uses the blksnap kernel module.
9.0-9.7
(RHCK)		 5.14.0-611.47.1.el9_7 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

Uses the blksnap kernel module.
9.5-9.7
(UEK8)		 6.12.0-200.74.27.1.el9uek 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

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-318.199.3.2.1.el9uek 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

Uses the blksnap kernel module.
8.0-8.10
(RHCK)		 4.18.0-553.117.1.el8_10 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

Uses the veeamsnap kernel module.
8.5-8.10
(UEK7)		 5.15.0-318.199.3.2.1.el8uek 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

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.353.3.el8uek 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

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

Veeam Backup & Replication 13.0.1.2067

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

Veeam Backup & Replication 13.0.1.2067

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

Veeam Backup & Replication 13.0.1.2067

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
16.0 6.12.0-160000.27 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

Uses the blksnap kernel module.
15 SP7 6.4.0-150700.53.34 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

Uses the blksnap kernel module.
15 SP6 6.4.0-150600.23.92 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

Uses the blksnap kernel module.
15 SP5 5.14.21-150500.55.136 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

Uses the blksnap kernel module.
15 SP4 5.14.21-150400.24.194 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

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

Veeam Backup & Replication 13.0.1.2067

Uses the blksnap kernel module.
12 SP5 4.12.14-122.296 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

Uses the veeamsnap kernel module.
Ubuntu
24.04 6.8.0-106 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

Uses the blksnap kernel module.
22.04 5.15.0-173 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

Uses the blksnap kernel module.
Debian
13.4 6.12.74-deb13-1-amd64 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

Uses the blksnap kernel module.
13.2 6.12.74-deb13-1-amd64 13.0.1.404

Veeam Backup & Replication 13.0.1.2067

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.1 6.12.0-124.49.1.el10_1 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the blksnap kernel module.
9.0-9.7 5.14.0-611.47.1.el9_7 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the blksnap kernel module.
8.0-8.10 4.18.0-553.117.1.el8_10 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the veeamsnap kernel module.
7.0-7.9 3.10.0-1160.147.1.el7 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

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

Veeam Backup & Replication 12.3.2.4465

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.1
(RHCK)		 6.12.0-124.49.1.el10_1 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the blksnap kernel module.

10.0-10.1
(UEK8)		 6.12.0-200.74.27.1.el10uek 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the blksnap kernel module.
9.0-9.7
(RHCK)		 5.14.0-611.47.1.el9_7 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the blksnap kernel module.
9.5-9.7
(UEK8)		 6.12.0-200.74.27.1.el9uek 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

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-318.199.3.2.1.el9uek 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the blksnap kernel module.
8.0-8.10
(RHCK)		 4.18.0-553.117.1.el8_10 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the veeamsnap kernel module.
8.5-8.10
(UEK7)		 5.15.0-318.199.3.2.1.el8uek 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

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.353.3.el8uek 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the veeamsnap kernel module.
7.0-7.9
(RHCK)		 3.10.0-1160.147.1.el7 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

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

Veeam Backup & Replication 12.3.2.4465

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

Veeam Backup & Replication 12.3.2.4465

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

Veeam Backup & Replication 12.3.2.4465

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

Veeam Backup & Replication 12.3.2.4465

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

Veeam Backup & Replication 12.3.2.4465

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
15 SP7 6.4.0-150700.53.34 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the blksnap kernel module.
15 SP6 6.4.0-150600.23.92 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the blksnap kernel module.
15 SP5 5.14.21-150500.55.136 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the blksnap kernel module.
15 SP4 5.14.21-150400.24.194 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

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

Veeam Backup & Replication 12.3.2.4465

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

Veeam Backup & Replication 12.3.2.4465

Uses the veeamsnap kernel module.
12 SP5 4.12.14-122.293 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the veeamsnap kernel module.
12 SP4 4.12.14-122.283 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the veeamsnap kernel module.
openSUSE
Leap 15.6 6.4.0-150600.23.87 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

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

Veeam Backup & Replication 12.3.2.4465

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

Veeam Backup & Replication 12.3.2.4465

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

Veeam Backup & Replication 12.3.2.4465

Uses the blksnap kernel module.
Tumbleweed 6.13.6-1 6.3.2.1207

Veeam Backup & Replication 12.3.2.3617

Uses the blksnap kernel module.
Ubuntu
25.04 6.14.0-36 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the blksnap kernel module.
24.10 6.11.0-26 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the blksnap kernel module.
24.04 6.8.0-106 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the blksnap kernel module.
22.04 5.15.0-173 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

Uses the blksnap kernel module.
Debian
13.4 6.12.74-deb13-1-amd64 6.3.2.1307

Veeam Backup & Replication 12.3.2.4465

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[Veeam Agent for Linux: Update Blocked by Repository Signing Key Change]]> https://www.veeam.com/kb4836 2026-03-17T00:00:00Z 2026-03-17T00:00:00Z

Veeam Agent for Linux: Update Blocked by Repository Signing Key Change

KB ID: 4836
Product: Veeam Agent for Linux | 6.3 | 6.3.1 | 6.3.2
Published: 2026-03-17
Last Modified: 2026-03-17
Article Applicability

This article is intended for customers managing Veeam Agent for Linux 6.3 deployments.

Deployments that have already been updated to Veeam Agent for Linux 13, or are being updated to it, are not affected by the repository GPG key change.

Challenge

When attempting to update Veeam Agent for Linux to the latest patch 6.3.2.1307 the update fails during with GPG verification errors, preventing access to the Veeam repository and blocking the agent upgrade.

Debian-base Error Example:

NO_PUBKEY C5A1CF329BB5AC67
The repository 'https://repository.veeam.com/backup/linux/agent/dpkg/debian/public stable InRelease' is not signed.
Updating from such a repository can't be done securely, and is therefore disabled by default.

Cause

This occurs because the repository signing key used for the Linux agent repository was rotated.

  • The previous signing key was nearing expiration (2026‑03‑15).
  • Veeam replaced the key and moved fully to SHA‑256–based signing.
  • Systems that already had the old key installed did not automatically receive the new public key.
  • As a result, package managers can no longer verify the repository metadata and blocks updates for security reasons.

Solution

To resolve this update the veeam-release package, which installs the new repository public key.

For Debian-based Deployments

Download and install the updated release package manually:

wget https://repository.veeam.com/backup/linux/agent/dpkg/debian/public/pool/veeam/v/veeam-release-deb/veeam-release-deb_1.0.11_amd64.deb
sudo dpkg -i veeam-release-deb_1.0.11_amd64.deb
sudo apt update
After this, the repository signature will validate correctly, and the agent can be updated to 6.3.2.1307 without errors. 
sudo apt-get upgrade veeam

For Deployments on RHEL 7

sudo yum install https://repository.veeam.com/backup/linux/agent/rpm/el/7/x86_64/veeam-release-el7-1.0.11-1.x86_64.rpm
sudo yum update veeam

For Deployments on RHEL 8

sudo yum install https://repository.veeam.com/backup/linux/agent/rpm/el/8/x86_64/veeam-release-el8-1.0.11-1.noarch.rpm
sudo yum update veeam

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 Manually Update GPG key on Veeam Hardened Repository Appliance]]> https://www.veeam.com/kb4833 2026-03-16T00:00:00Z 2026-03-16T00:00:00Z

How to Manually Update GPG key on Veeam Hardened Repository Appliance

KB ID: 4833
Product: Veeam Backup & Replication | 12.3 | 12.3.1 | 12.3.2
Published: 2026-03-16
Last Modified: 2026-04-09
Article Applicability

This article is specifically regarding the Veeam Hardened Repository ISO v2 appliance, which was distributed alongside Veeam Backup & Replication 12.

For information about manually updating the GPG key on the appliances associated with Veeam Backup & Replication 13, review KB4834.

Challenge

This article documents how to manually update the GPG key for Veeam Hardened Repository ISO v2 appliances.

Generally, the new key should automatically be distributed to all appliances that have access to the Veeam repository. However, if the appliance does not have access to the repository (either directly, via a mirror, or via http_proxy), the GPG key will not be updated. After the installed GPG expires, that appliance will be unable to connect to the update repository.

On March 15, 2026, the GPG key used to sign the Veeam RPM packages expired.

Solution

  1. Download the new GPG key and copy it to the Veeam Hardened Repository using either the Files node or SSH with the veeamsvc account.
    The new key is available here:
    https://repository.veeam.com/keys/RPM-E6FBD664
  2. Use Live Boot ISO to gain shell access to the Veeam Hardened Repository appliance.
    Live Boot is available from the same ISO used for installation.
  3. Once in live boot, mount the original system disks and enter chroot. 
    1. sudo ./mount_systemvol.sh

    2. sudo chroot /mnt
  4. Delete the old GPG key using the following command:
rpm -qa gpg-pubkey | grep e6fbd664 | xargs -r rpm -e
  1. Import the new GPG key using the following command:
rpm --import /path/to/new/gpg_key
After importing the new GPG key, updates from the repository should be available again.

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 Manually Update GPG key on Veeam Appliances]]> https://www.veeam.com/kb4834 2026-03-16T00:00:00Z 2026-03-16T00:00:00Z

How to Manually Update GPG key on Veeam Appliances

KB ID: 4834
Product: Veeam Backup & Replication | 13
Published: 2026-03-16
Last Modified: 2026-03-16
Article Applicability

This article is specifically regarding the Veeam Appliances used in conjunction with Veeam Backup & Replication 13. Including the Veeam Software Appliance, Veeam Infrastructure Appliance, and Veeam Hardened Repository deployed from the Veeam Infrastructure Appliance.

For information about manually updating the GPG key on the legacy Veeam Hardened Repository Appliance v2, which is used with Veeam Backup & Replication 12, review KB4833.

Challenge

This article documents how to manually update the GPG key for Veeam Appliances (i.e., Veeam Software Appliance, Veeam Infrastructure Appliance, and Veeam Hardened Repository deployed from the Veeam Infrastructure Appliance).

Generally, the new key should automatically be distributed to all appliances that have access to the Veeam repository. However, if an appliance does not have access to the repository (either directly, via a mirror, or via http_proxy), the GPG key will not be updated. After the installed GPG expires, that appliance will be unable to connect to the update repository.

On March 15, 2026, the GPG key used to sign the Veeam RPM packages expired.

Solution

  1. Download the GPG key private fix zip using the bottom below.
  2. Within the privatefix zip file are two bndl files:
    • bundle-1266150-1558103.bndl — For Veeam Software Appliance and Veeam Infrastructure Appliance.
    • bundle-1266150-1558102.bndl — For Veeam Backup Enterprise Manager Appliance.
  3. Install the private fix bndl file using the Veeam Host Management Console.
Download GPG PrivateFix

Filename: KB4834_GPG_key_pf_20260313.zip

MD5: 5A0F205BE0A4EB9B5317A8481A4BF33B
SHA-1: 56A0A4B05195A2246337BFC89BFFD6BBA4A80C9B
SHA-256: DF0AA5C38892B8F6BAB58720135C051A25404615498AC99B38CE10E80D2EE8C3

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[Migration to Unified Veeam Data Cloud FAQ]]> https://www.veeam.com/kb4780 2026-03-16T00:00:00Z 2026-03-16T00:00:00Z

Migration to Unified Veeam Data Cloud FAQ

KB ID: 4780
Product: Veeam Data Cloud for Microsoft 365
Published: 2025-10-01
Last Modified: 2026-03-16

Below are the most commonly asked questions.

What is changing with my Veeam Data Cloud for Microsoft 365 experience?
Veeam is transitioning customers to the Veeam Data Cloud Platform, a unified multi-workload interface. This new experience allows you to manage Microsoft 365, Entra ID, Salesforce, and other workloads from a single platform at cloud.veeam.com.
When will the migration occur?
Migrations began on October 1st, 2025, and are still ongoing. Customers are being migrated in batches and closely monitored to ensure a smooth transition. When it is time for your migration, you will receive an in-app alert confirming your specific migration window.
How long will the migration take?
Migrations should take only a few minutes, but you should allow up to an hour. During migration, the portal will be inaccessible, and you will see a notification if you log in during this period.
What happens during migration?
During migration, you will be able to log in and see your Dashboard only. A message will be displayed on the dashboard showing that migration is in progress. The migration only affects the management interface; backups will continue to run normally. Once migration has been completed, your login to the classic Veeam Data Cloud interface will be disabled, and you’ll be redirected to cloud.veeam.com. Roles, subscriptions, and backup policies will be transferred.
Will my login credentials change?
No, your credentials remain the same. However, after migration, you’ll be redirected to the new Veeam Data Cloud Platform. Please update your bookmarks to cloud.veeam.com.
What if I can’t log in to the new interface after migration?
If login fails, it may be due to domain mismatches. We have enhanced security requirements on the Veeam Data Cloud Platform and require that your domain is registered to the same Microsoft ID tenant as your primary domain. Contact support if you need assistance with logging in.
Will my roles and permissions be preserved?
Roles will be translated as closely as possible. The Veeam Data Cloud Platform scopes permissions at user assignment, not role creation, which may result in minor differences. Admins may need to review and adjust roles post-migration.
Will my backups be affected during migration?
No. Backups will continue to run normally. The migration only affects the management interface. Your data will be retained in the classic Veeam Data Cloud service for rollback if needed.
Can I restore from old backups after migration?
Yes! All your historic backups will be accessible for restore using the new Veeam Data Cloud interface.
What differences will I find in the new Veeam Data Cloud Platform?

The Veeam Data Cloud platform is a multi-workload experience. You will be able to protect, monitor, and manage multiple workloads from a single UI, including Microsoft 365, Entra ID, and Salesforce.

Role and User management differences:

  • Users and roles are managed in the unified platform rather than the Microsoft 365 interface.
  • Permissions are scoped at user assignment, not role creation.
  • The new platform does not currently support scoping roles to Entra ID groups; this support is coming soon.
  • Self-service restore is enabled directly in your Microsoft 365 workload tenant settings. Role assignment is not required and will not activate this feature. For more information, see Enabling Self-Service Restore.
  • Enhanced security requirements on the Veeam Data Cloud Platform require that user domains be registered to the same Microsoft ID tenant as your primary domain registered with Veeam.

Once you select your Microsoft 365 tenant, the interface will be similar, with some minor differences:

  • After migration, one month of operational logs will be available. These logs include recent user activity and notifications logs, licensed users, and storage use graphs. The complete history will be available within two weeks.
  • Any active Download in background operations will be interrupted during migration. You'll need to restart the restore after migration or contact support for help.
  • The new interface does not support customized tenant display names. If you rename your tenant in the old interface, this change will not be preserved after migration.
  • The new interface does not support logo and colour customizations. If you changed these settings in the old interface, the migration will not preserve them.

For details of the new interface see the Veeam Data Cloud User Guide

Will I be notified?

Yes. The Veeam Data Cloud Platform interface provides:

  • A pre-migration email.
  • An in-progress in-app alert.
  • A post-migration in-app message with instructions and links.
I’m managed by a VCSP. Will I be migrated?
VCSP (Veeam Cloud Service Provider) customers will be migrated once VCSP support has been enabled in the new Veeam Data Cloud Platform. We will communicate migration dates and information about the migration process with your VCSP.
What if a user from outside my organisation has a login to my VDC tenant?
We will migrate those users, but you will not be able to add users from that domain in the future. We have enhanced security requirements on the Veeam Data Cloud platform and require that user domains are registered to the same Microsoft ID tenant as your primary domain registered with Veeam.
My organization has multiple Microsoft tenants or domains. Can we still migrate?
Yes, all tenants linked to your organisation will be consolidated under the primary organisation, but will remain separate for policy creation and restore. Only users with an email domain registered to the same Microsoft ID tenant as your primary domain registered with Veeam can be used for login.
Who do I contact for help?
Reach out to Veeam support or your account manager.

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.

]]>