Veeam Support Knowledge Base

"Warning: Exchange account was not found"

2026-07-08T00:00:00Z

"Warning: Exchange account was not found"

KB ID:	4877
Product:	Veeam Backup for Microsoft 365 \| 8.5
Published:	2026-07-08
Last Modified:	2026-07-08

Challenge

When backing up Exchange Online mailboxes, Veeam Backup for Microsoft 365 intermittently fails to discover and process some mailboxes, reporting the following warning:

Warning: Exchange account was not found

The affected mailboxes vary between job runs, and in some cases, only a small subset of mailboxes back up successfully. The impacted mailboxes exist, are licensed, and function normally in Microsoft 365. This behavior is typically observed in hybrid organizations after mailboxes have been migrated from on-premises Exchange to Exchange Online.

Cause

This issue occurs because the Microsoft Autodiscover response for mailboxes located in a separate forest of a multi-forest hybrid organization does not consistently return all of the attributes that Veeam Backup for Microsoft 365 requires to identify each mailbox. Because the returned attributes vary between requests, the specific mailboxes that fail to be discovered differ from one job run to the next.

Solution

A patch is available for Veeam Backup for Microsoft 365 8.5.0.1014 that resolves this issue.

Before applying the patch, ensure that Veeam Backup for Microsoft 365 has been upgraded to build 8.5.0.1014.

Download Patch

After downloading the patch, complete the following steps:

Install the following .msp files in the order listed:
1. VeeamBackupMicrosoft365_8.5.0.1503_20260702.msp
2. VeeamExplorerForExchange_8.5.0.1503_20260702.msp
3. VeeamExplorerForSharePoint_8.5.0.1503_20260702.msp
4. VeeamExplorerForTeams_8.5.0.1503_20260702.msp
Upgrade any remote backup proxies and proxy pools, if applicable. For instructions, see Upgrading Backup Infrastructure Components.
Re-run the affected backup jobs and verify that the issue is resolved.

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.

Data Import for Veeam Data Cloud for Salesforce

2026-07-07T00:00:00Z

Data Import for Veeam Data Cloud for Salesforce

KB ID:	4878
Product:	Veeam Data Cloud for Salesforce
Published:	2026-07-07
Last Modified:	2026-07-07

Purpose

This article explains the Data Import feature in Veeam Data Cloud for Salesforce (VDCSF): what it does, which sources it currently supports, and how to prepare data for importation.

This article is a feature summary only. Full procedural documentation can be found in the VDCSF User Guide.

Solution

Overview

The Data Import feature brings backup data that a customer already holds into VDCSF, preserving their backup history when migrating from another solution. The data can come from a supported third-party Salesforce backup tool or from exports of on-premises Veeam Backup for Salesforce (VBSF).

The exported CSV files are uploaded to cloud storage, and a Data Import job is then run. The job merges the data into the customer's VDCSF backup, creating a restore point for each imported snapshot. Once the import finishes, standard VDCSF restore works on the imported points, and regularly scheduled backups continue incrementally from there, without re-downloading data or creating duplicate records.

Like an initial full backup, a Data Import job can take anywhere from a few hours to several days, depending on the volume of data being imported. Customers should plan their cutover from the legacy solution accordingly.

Eligibility Requirements

Available only to customers with a Salesforce subscription of 200+ users.
Data Import requires an empty Veeam Data Cloud for Salesforce tenant, one whose backup policy has not run and therefore contains no restore points. A tenant that already has Salesforce backups cannot be used as an import target.

What's Supported Today

Data Import supports object record data in CSV format from the following two sources:

Own
- Archived Own data is not supported.
- Currently, the only supported third-party Salesforce backup product.
  Support for an additional third-party product can be requested by opening a Support case.
Veeam Backup for Salesforce
- For customers migrating an existing on-premises deployment to Veeam Data Cloud for Salesforce.

Note: Files and Attachments, Salesforce configuration metadata, Big Objects, and Events are not supported.

Enablement

Data Import is not self-service and must be enabled for the tenant by opening a Support case before an import is planned.

Import Data Preparation

Supported Storage

The exported CSV files must be uploaded to Amazon S3 or Azure Blob Storage. Veeam Data Cloud for Salesforce connects to that location to read the files; it never writes to it.

File Format

CSV (comma-separated values) files, one file (or a set of split files) per Salesforce object.
Files may be uncompressed, gzip-compressed (.gz), or in a password-protected ZIP archive (.zip). The password is entered when the import job is started and is not stored afterward.
The data inside the files must not be encrypted (e.g., no field-level encryption). A password-protected archive is acceptable, but encrypted field values inside the CSV are not supported.
The CSV header row must contain the Salesforce field API names for that object (column order doesn't matter, and matching is not case-sensitive).

File Naming

Each file name must identify the object and follow this pattern:

ObjectName[__h][-NNN].csv[.gz|.zip]

Account.csv
Current-state records for the Account object.
Account__h.csv
History records for the Account object (VBSF exports only).
Account-001.csv.gz, Account-002.csv.gz
A split export. The separator (- or _) must appear before the digits so they are read as part of the split and not the object name.

Any file that doesn't match this pattern will cause the whole job to fail before anything is imported, so file names should be verified before uploading.

Folder Structure

Own exports
Each daily snapshot must be in its own folder named day_YYYYMMDD_HHMMSS (an optional suffix, e.g. -abc123, is allowed). Seconds precision is required, and every folder in the job must have a unique timestamp. Files placed outside a day_* folder (including the storage root) are not supported and will cause the import to fail.
Veeam Backup for Salesforce exports
Files can be placed in the root or in any subfolder, as the restore-point and date information is already embedded in the CSV.

Note: Own and VBSF exports cannot be imported in the same job. A single import job must use only one export format, even across different objects, so each export type requires its own job.

Data Requirements and Known Limitations

Each object's CSV must include its Salesforce record Id column, plus IsDeleted and the incremental-tracking field where those exist for the object. If a required column is missing from even one folder, the whole object fails to import (no partial import).
Extra columns not in the Salesforce schema are ignored; the job still completes but is marked Warning, with the ignored columns listed in the job log.
Missing optional columns and column sets that change between snapshots are both supported, as VDCSF adapts to schema differences over time.
An empty (header-only) CSV, or a storage location with no matching files, is handled without error (the job completes with nothing imported).
Objects that no longer exist in Salesforce cannot be imported in this release; fields removed from the org are still imported and kept in the backup as text.
While a Data Import job is in progress for a tenant, no other backup job can run for that tenant until it finishes.

Monitoring and Resiliency

The Data Import job reports one of four statuses when it finishes:

Status	Meaning
Success	All objects/folders were imported with no issues.
Warning	Import completed, but some data was skipped (see below) or part of a multi-object job failed while the rest succeeded.
Failed	The job did not import any data. The job log identifies the reason, and the source data must be corrected before retrying.
Skipped	No matching files were found in the storage location (or a file filter excluded everything).

Swipe to show more of the table

If a job fails or only partially completes, there is no need to start over. The whole job, a single file, or a filtered subset of files can be re-run, and VDCSF will pick up where it left off without creating duplicate records or gaps in restore-point history.

To limit a (re)run to a subset of files, the File Name Pattern option can be used. It accepts a regular expression matched against the file/folder path. For example:

day_2026031[9]|day_2026032
Imports only the daily-snapshot folders for March 19–21, 2026.
Account
Imports only files for the Account object.

The pattern is case-sensitive and is applied on every retry, which is important to consider when importing the remaining folders or objects later.

Next Steps

Eligibility should be confirmed: the tenant requires a Salesforce subscription of 200+ users and must be an empty VDCSF tenant with no existing backups.
The source data should be confirmed as supported: an Own or on-premises VBSF export containing Salesforce object records in CSV format.
A Support case should be opened to have Data Import enabled for the tenant, and to request an additional third-party source if one is needed.
The export files should be prepared to meet the file format, naming, and folder-structure requirements, then uploaded to Amazon S3 or Azure Blob Storage.
A trial import into a Sandbox or UAT tenant is recommended before importing into Production.
The Data Import job should be started from the VDCSF UI, and its completion status reviewed, with any affected files re-run as needed.

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.

Veeam My Account Portal - MFA Guide

2026-07-07T00:00:00Z

Veeam My Account Portal - MFA Guide

KB ID:	4716
Published:	2025-02-26
Last Modified:	2026-07-07

Veeam Data Cloud MFA Requirements

As of July 7, 2026, logging in to Veeam Data Cloud (cloud.veeam.com) using the Continue with Veeam authentication option now requires that your Veeam Account have Multi-Factor Authentication (MFA) enabled.

If you use the Continue with Microsoft authentication option, no action is required.
If MFA is already enabled on your Veeam Account, no action is required.

For information about enabling MFA, review the Solution section below.

Purpose

This article documents how to enable and manage the Multifactor Authentication (MFA) option available for the Veeam My Account portal login (my.veeam.com).

Solution

The MFA option allows users to enhance the security of their Veeam Account using Time-based One-Time Passwords (TOTP) from authenticator applications.

Below are the most Frequently Asked Questions, click on a question to see more information.

How do I enable MFA for my Veeam Account login?

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

2026-07-07T00: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-07-08

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.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	Max Supported Kernel	VAL Build	Shipped with VBR Build
Red Hat Enterprise Linux (RHEL) / Rocky / AlmaOnly Rocky/Alma 8.10 and 9.4 or higher are supported.
10.0-10.2	6.12.0-211.30.1.el10_2	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
9.0-9.8	5.14.0-687.22.1.el9_8	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
8.4-8.10	4.18.0-553.141.1.el8_10	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the veeamsnap* kernel module.*
Oracle Linux
10.0-10.2 (RHCK)	6.12.0-211.30.1.el10_2	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
10.0-10.1 (UEK8)	6.12.0-204.92.4.2.el10uek	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
9.0-9.8 (RHCK)	5.14.0-687.22.1.el9_8	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
9.5-9.7 (UEK8)	6.12.0-204.92.4.2.el9uek	13.0.2.2	Veeam Backup & Replication 13.0.2.29 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-322.203.3.2.el9uek	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
8.0-8.10 (RHCK)	4.18.0-553.141.1.el8_10	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the veeamsnap* kernel module.*
8.5-8.10 (UEK7)	5.15.0-322.203.3.2.el8uek	13.0.2.2	Veeam Backup & Replication 13.0.2.29 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.357.3.1.el8uek	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the veeamsnap* kernel module.*
7.7-7.9 (UEK6)	5.4.17-2136.338.4.2.el7uek	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the veeamsnap* kernel module.*
7.5-7.9 (UEK5)	4.14.35-2047.542.2.el7uek	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the veeamsnap* kernel module.*
7.1-7.9 (UEK4)	4.1.12-124.93.1.el7uek	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the veeamsnap* kernel module.*
SUSE Linux Enterprise (SLES)
16.0	6.12.0-160000.35	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
15 SP7	6.4.0-150700.53.63	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
15 SP6	6.4.0-150600.23.118	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
15 SP5	5.14.21-150500.55.169	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
15 SP4	5.14.21-150400.24.222	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
15 SP3	5.3.18-150300.59.229	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
12 SP5	4.12.14-122.317	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the veeamsnap* kernel module.*
Ubuntu
26.04	7.0.0-15	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
24.04	6.8.0-117	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
22.04	5.15.0-185	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
Debian
13.5	6.12.95-deb13	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*

Swipe to show more of the table

Veeam Agent for Linux 6.3.2

blksnap kernel module

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

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

Version	Maximum Supported Kernel	VAL Build	Shipped with VBR Build
*Red Hat Enterprise Linux (RHEL)* /** CentOS*Only CentOS 7.x is supported. / Rocky / AlmaOnly Rocky/Alma 8.10 and 9.3 or higher are supported.
10.0-10.2	6.12.0-211.30.1.el10_2	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
9.0-9.8	5.14.0-687.22.1.el9_8	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
8.0-8.10	4.18.0-553.141.1.el8_10	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
7.0-7.9	3.10.0-1160.155.1.el7	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
6.4-6.10	2.6.32-754.53.1	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.* _{Please note that RHEL6 reached "End of life," and the EPEL repository has archived the version 6 packages. If you are looking for the dkms package (a VAL prerequisite), check: https://archives.fedoraproject.org/pub/archive/epel/6/} _{See also: https://access.redhat.com/discussions/4768501.}
Oracle Linux
10.0-10.2 (RHCK)	6.12.0-211.30.1.el10_2	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
10.0-10.1 (UEK8)	6.12.0-204.92.4.2.el10uek	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
9.0-9.8 (RHCK)	5.14.0-687.22.1.el9_8	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
9.5-9.7 (UEK8)	6.12.0-204.92.4.2.el9uek	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.* ^{Note: Building the veeamsnap kernel module on Oracle Linux 9 with UEK R8 kernel requires additional steps. For more information, refer to KB4732}
9.0-9.7 (UEK7)	5.15.0-322.203.3.2.el9uek	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
8.0-8.10 (RHCK)	4.18.0-553.141.1.el8_10	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
8.5-8.10 (UEK7)	5.15.0-322.203.3.2.el8uek	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.* _{Note: Building the veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information, refer to KB4394}
8.1-8.10 (UEK6)	5.4.17-2136.357.3.1.el8uek	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
7.0-7.9 (RHCK)	3.10.0-1160.155.1.el7	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
7.7-7.9 (UEK6)	5.4.17-2136.338.4.2.el7uek	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
7.5-7.9 (UEK5)	4.14.35-2047.542.2.el7uek	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
7.1-7.9 (UEK4)	4.1.12-124.93.1.el7uek	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
6.4-6.10 (RHCK)	2.6.32-754.35.1.el6	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap kernel module.
6.8-6.10 (UEK4)	4.1.12-124.16.4	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
16	6.12.0-160000.35	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
15 SP7	6.4.0-150700.53.63	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
15 SP6	6.4.0-150600.23.118	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
15 SP5	5.14.21-150500.55.169	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
15 SP4	5.14.21-150400.24.222	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
15 SP3	5.3.18-150300.59.229	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
15 SP2	5.3.18-24.96.1	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
12 SP5	4.12.14-122.317	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
12 SP4	4.12.14-122.283	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
openSUSE
Leap 16.0	6.12.0-160000.35	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
Leap 15.6	6.4.0-150600.23.103	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
Leap 15.5	5.14.21-150500.55.83	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
Leap 15.4	5.14.21-150400.24.100	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
Leap 15.3	5.3.18-150300.59.106	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
Tumbleweed	6.14.6-2	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
Ubuntu
25.04	6.14.0-36	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
24.10	6.11.0-26	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
24.04	6.8.0-117	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
22.04	5.15.0-185	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
Debian
13.5	6.12.95-deb13	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*

Swipe to show more of the table

Veeam Agent for Linux 6.3.1

blksnap kernel module

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

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

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:

Rocky Linux 9.3 and 9.4
Alma Linux 9.3 and 9.4

blksnap kernel module

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

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

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

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.
9.0-9.3	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) */ CentOSOnly 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.

Release Information for IBM FlashSystem Plug-In for Veeam Backup & Replication

2026-07-06T00:00:00Z

Release Information for IBM FlashSystem Plug-In for Veeam Backup & Replication

KB ID:	4650
Product:	Veeam Backup & Replication \| 12.3 \| 12.3.1 \| 12.3.2 \| 13
Published:	2024-08-28
Last Modified:	2026-07-06

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 IBM FlashSystem Plug-In v2.4.2, ensure that you are running at least Veeam Backup & Replication version 12.3.0.310, for deployments on Windows, or the Veeam Software Appliance version 13.0.0.4967. You can check the build number in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.

IBM FlashSystem Plug-In v2.4.2 supports integration with the following storage systems:

IBM Spectrum Virtualize OS version 8.4.0 or later

Detailed configuration instructions are available from IBM: IBM Storage Virtualize Plugin for Veeam Backup and Replication

What's New

Support for the most recent IBM Spectrum Virtualize OS versions up to non-LTS 9.1.x
Support for local storage partitions
Support for PBHA (policy-based high availability) configurations (snapshot creation/orchestration on source, backup from source storage array, restores)
Bug fixes

Known Issues

The following are known issues for the IBM FlashSystem Plug-In for Veeam Backup & Replication, organized by the IBM Spectrum Virtualize versions they affect.

Version 8.4.0 and higher

Policy-based replication relationships are not detected. You will not be able to select this feature for backup and snapshot orchestration with secondary storage arrays.

Version 8.4.0 through 8.5.0

Before adding the storage system to the backup infrastructure, ensure that a license for the IBM Spectrum Virtualize storage system supports IBM FlashCopy.

Version 8.4.2 and higher (iSCSI connectivity)

During backup from storage snapshots and storage rescan, storage snapshot export to a proxy is required. If the default proxy is used, Veeam Backup & Replication creates a service host with the "VeeamAUX" prefix in the default portset of the storage system. If you want to send traffic using a custom portset, you can manually specify the required portset in the service host settings. If another proxy is used, check that the host that performs the proxy role has the required port set in the host settings.
When storage partitions are used, proxy hosts are not created automatically. The required proxy hosts must be created manually in the storage partition prior to registering the storage array in Veeam Backup & Replication, including the Veeam initiator host used for VMFS rescan. For details on discovering the Veeam initiator IQN, see Rescan (Storage Discovery) Process in the User Guide.

Version 8.5.1 and higher

Volume snapshot functionality can cause node warmstarts on IBM Spectrum Virtualize 8.5.1 and later. This issue occurs if the account used to connect to the storage system in Veeam Backup & Replication is a member of an ownership group on the storage system. The problem is due to a known IBM issue (SVAPAR-138214).
To avoid warmstarts, use an Administrator account that is not a member of the ownership group. Alternatively, you can switch to IBM FlashCopy by setting a registry value. For more information, contact Veeam Customer Support.
For FlashSystem models that support storage volume snapshot technology, Veeam Backup & Replication automatically uses that functionality, which does not require license support for IBM FlashCopy.

Once a storage volume snapshot is created (with or without Veeam Backup & Replication), FlashCopies—including policy-based Safeguarded backups created with third-party software—are blocked from being created. However, it remains possible to restore from previously created FlashCopies. If needed, you can continue working with FlashCopy by setting a registry value available from Veeam Customer Support. Note that setting this registry value would require removing all storage volume snapshots.
Storage partitions are not compatible with IBM FlashCopy. Volumes included in a storage partition can only be protected using storage volume snapshot technology.

Version 8.7.1 and higher

The vendor no longer supports Metro Mirror, Global Mirror, and HyperSwap features. As a result, the replication feature is unavailable in Veeam Backup & Replication. You can configure backup and snapshot creation only for the primary storage array.

For existing backup jobs that use the replication feature, ensure that the "Failover to primary storage snapshot" option is enabled. Alternatively, you can remove the replication feature at the Secondary Target step of the wizard or create new backup jobs.

If you need the replication feature, use IBM Spectrum Virtualize versions prior to 8.7.1.

Download Information

For Veeam Backup & Replication on Windows

Download IBM Plug-In

^{Release date: 2026-07-02}

MD5: CEF7D0B29A11BCEB6190293444B8395C
SHA1: 69570EB0CA142237895E2441DAC0B2C1E504F100
SHA256: 79361E56325BF232B9E91617A3C1712F77F3BAD57C15C2F879EF65AAF41264F7

For Veeam Backup & Replication on Veeam Software Appliance

Download IBM Plug-In

^{Release date: 2026-07-02}

MD5: 725430F578F61929BCCC69F6324AAE1F
SHA1: E76DDFC55D076ADDC6CE6DE3699F96621C08B4AE
SHA256: FCA2A8D182C2B7DEA7BB5AAEF1B89B8EAD4820A9ABB48DB620C8B76BAE54BBFD

Previous Versions

IBM FlashSystem Plug-In for Veeam Backup & Replication [2.3.80] - 2025-11-19

Added support for Veeam Backup & Replication v13.0.1.

IBM FlashSystem Plug-In for Veeam Backup & Replication [2.0.26] - 2024-08-28

This independent plug-in implements a full functionality set previously built into Veeam Backup & Replication.
For details, please review: Veeam Backup & Replication Storage System Snapshot Integration Guide: VMware Integration.

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.

The HTTP request was forbidden with client authentication scheme

2026-07-02T00: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-07-08

July 2, 2026 — Issue Recurrence [Resolved]

July 2, 2026 | Veeam Customer Technical Support began observing an increase in cases reporting that jobs were failing with the same error documented in this article.
July 3, 2026 | Microsoft engineering has implemented backend changes as part of the ongoing investigation into the issue. Customers are encouraged to retry failed operations. A detailed RCA is being discussed and is expected soon.
July 7, 2026 | Root Cause: Microsoft engineering identified the issue with EWS access evaluation and reverted it, restoring access for the affected subset of tenants. No customer action is required.

Veeam Data Cloud for Microsoft 365 Configuration Check Notice

On 2026-05-22, an update to the Veeam Data Cloud for Microsoft 365 services introduced a configuration check to proactively detect configuration issues that may cause the issue described in this article's Challenge section. The Cause and Solution section of this article remains relevant and should be used to resolve the configuration issue and pass the configuration check.

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 levels:

Part 1: Set the `EwsEnabled` Flag at the Tenant (Organization) Level

Review the EWS enablement status using the following PowerShell command:

#Get the organization's EwsEnabled state.
Get-OrganizationConfig | Fl EwsEnabled

If the output is anything other than an explicit $true, access via EWS must be enabled using the following command:

#Set the organization's EwsEnabled state to $true.
Set-OrganizationConfig -EwsEnabled $true

Part 2: Set the `EwsEnabled` Flag at the User (Mailbox) Level

Review the list of mailboxes where the EwsEnabled flag is not $true using the following PowerShell command:

#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

Any mailbox listed in the results from the previous step that needs to be backed up must have the EwsEnabled flag set to $true using the following command:

#Set a single mailbox's EwsEnabled state to $true
Set-CASMailbox mailbox@address.com -EwsEnabled $true

Optionally, customers may choose to set the EwsEnabled flag to $true for all mailboxes using the following PowerShell command:

#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

Part 3: Wait and Verify Results

Wait. The new values may take up to 24 hours to replicate and take effect.
Re-check the backup job.

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.

Release Information for Veeam Backup for Microsoft 365 8.5

2026-06-29T00:00:00Z

Release Information for Veeam Backup for Microsoft 365 8.5

KB ID:	4873
Product:	Veeam Backup for Microsoft 365 \| 8
Published:	2026-06-29
Last Modified:	2026-07-01

Requirements

This release can be used to:

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

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

Release Information

8.5.0.1014

2026-06-30

Release Notes for Veeam Backup for Microsoft 365 8.5

New Features and Enhancements

Added new PowerShell cmdlets to remediate data stored in object storage repositories that is affected by the issue described in KB4835. For more information, see KB4874.
Additional Microsoft Graph permissions are required for the backup app registrations in Microsoft Entra ID to support Exchange mailbox protection after EWS retirement. For more information, see KB4820.
Added support for Microsoft Exchange Server Subscription Edition.
SharePoint site permissions and members are now preserved when restoring a site to another location within the same Microsoft 365 organization using the REST API.
Microsoft Teams channel messages are now referred to as "posts" instead of "chats", to better reflect Microsoft's own terminology. REST API and PowerShell parameter names are not affected.
Improved SharePoint backup and object storage repository performance by extending asynchronous processing to list content retrieval and file cache operations.
Improved Exchange backup performance for mailboxes with large numbers of emails in a single month.
Reduced memory usage and improved backup job performance for repositories containing SharePoint data.
Improved backup performance for SharePoint sites containing large numbers of items by optimizing internal database queries for large datasets, improving query completion time from minutes to milliseconds.
Improved SharePoint backup job throughput.
Optimized how object storage consumption metrics are updated during backup jobs and retention tasks, reducing PostgreSQL load for large repositories.
Reduced Exchange backup job duration by up to 26% for large mailboxes by parallelizing sync and repository write operations.
Optimized processing of backup job and restore session events to prevent uncontrolled growth of the NATS controller stream.

Bug Fixes

General

The backup proxy service on a Linux machine may crash during an OS base system update.
The Veeam Backup for Microsoft 365 upgrade stalls if services, including Veeam.Archiver.Shell and Veeam.Archiver.Proxy, do not terminate properly before starting.
Backup or restore sessions get stuck in the Running state during Veeam Backup for Microsoft 365 upgrades when proxies are running different product versions simultaneously.
In large-scale environments, retention tasks run longer than expected or fail intermittently.
Re-adding an immutable object storage repository after deletion fails with an error stating the S3-compatible object storage already exists at the specified location.

Organization cache synchronization intermittently fails on group members with errors such as:

A web error occurred when invoking {path}. The response status code does not indicate success: 400 (Bad Request).

Editing an organization to enable Teams chat protection fails with the error:
```
New configuration must point to the same Exchange organization.
```
The retention task fails on immutable S3-compatible repositories when all blob versions have unexpired locks with the error:
```
Sequence contains no elements
```
Duplicate geolocation entries are not detected after the organization configuration is loaded, resulting in unexpected behavior in multi-geo environments.

Backup and Backup Copy

OneDrive backup copy jobs to an immutable repository fail with the error:
```
The file content stream must be read to obtain: ContentOffset.
```
A SharePoint backup job gets stuck in the Running state with no progress, reporting a large number of failed items with the error:
```
An invalid file cache context was detected.
```
Exchange backup jobs intermittently fail to download individual mailbox items, displaying the error:
```
Failed to download some of the items.
```

A SharePoint backup job stalls after this error occurs:

The value must be greater or equal to {value}. (Parameter 'to')

Backup jobs fail during the object resolve phase if processed objects have properties, such as display names or office locations, containing \0 characters.
Backup copy job transfers restore points exceeding the retention period set on the target repository.
Backup copy to an immutable repository fails with an error indicating the immutability period has not yet expired.
Teams and SharePoint backup jobs fail with the error:
```
Index was outside the bounds of the array.
```
When the organization contains Microsoft Loop content storage sites that use the new URL format, the SharePoint backup job fails with the error:
```
Attempted to perform an unauthorized operation.
```
After a repository resync on immutable S3-compatible storage, the Exchange backup job fails with the error:
```
Failed to apply immutability to object {path} because the object is already immutable
```
Backup copy job intermittently fails with the error:
```
Resolve failed: Cannot access a disposed object.
```
SharePoint list entities that are deleted and recreated in production are not correctly re-added to the backup during incremental job runs.
Exchange backup jobs run longer than expected when the Exchange Online REST API is temporarily unavailable.

Backup jobs processing SharePoint and OneDrive data fail with the error:

PostgreSQL database operation failed multiple times with transient error.

A backup job fails with the error:
```
Failed to resolve some objects.
```

Restore

SharePoint item restore fails if the item contains a _CopySource property.
Restoring a OneDrive to another OneDrive account with the same display name using the 'Copy To' option fails with the error:
```
There are multiple OneDrive accounts with the specified username. Please select the account explicitly.
```
Microsoft sensitivity labels applied to a SharePoint site or list are not preserved when the site or list is restored to a different location.
The Restore Portal fails to open after upgrading from Veeam Backup for Microsoft 365 v7.
The Advanced Find feature in Veeam Explorer for Microsoft Exchange may return incomplete or incorrect results.
Restore sessions on JET-based repositories fail due to excessive organization verification.
In organizations where the user has both a member account and a legacy guest/external account after a cross-tenant migration, restoring that user's OneDrive in Veeam Explorer for Microsoft OneDrive fails with the error:
```
There are multiple OneDrive accounts with the specified username
```
Performing an Exchange restore operation when the recipient list contains a skipped or unresolvable element fails with the error:
```
An internal server error occurred
```
After migrating backup data from a JET-based repository to object storage, mailbox restore points do not appear in the Restore Portal.
Restore of a SharePoint site to another geo region within the same Microsoft 365 organization fails with the error:
```
This parameter is incompatible with restoring to another location: RestorePermissions.
```
Changing the scope in the Restore Portal fails with repeated PostgreSQL transient errors.
Teams post timestamps in exported HTML files were displayed in the timezone of the machine running the REST API server instead of UTC, causing dates to appear incorrect when compared to Microsoft Teams.

REST APIs

The (GET) v8/backuprepositories/{id}/SiteData REST API endpoint responds slowly on larger repositories.
Teams restores initiated via legacy v7 REST API fail with the error:
```
Failed to get task result because the task does not exist.
```
OneDrive restore using the 'Copy To' option initiated via REST API automatically cancels after processing for a period without completing.
The REST API returns incorrectly formatted date/time values on servers configured with northern European system locales.
The REST API returns an invalid endTime value for backup job sessions in progress, missing the UTC designator in the timestamp.
For organizations configured to protect only the Exchange service, backup jobs configured via the REST API attempt to access SharePoint and fail with the error:
```
HostNotFound
```
The (GET) v8/RestoreSessions/{restoreSessionId}/Events endpoint returns an incorrect restore target for SharePoint and OneDrive restore sessions.
The changedItems and deletedItems parameters are ignored when restoring a OneDrive to the same or a different location using the copyTo REST API endpoints.

PowerShell and Data Management

Data move jobs fail with the error:

Object reference not set to an instance of an object.

Data move job fails with the error:

Failed to move team posts: No JSON content found.

When the organization has already been removed from the Veeam Backup for Microsoft 365 Console, deleting backups from a JET-based repository using the Remove-VBOEntityData cmdlet fails with one of the following errors:
```
An item with the same key has already been added
```
or
```
Organization does not exist
```
Data move jobs transferring Teams data fail with the error:
```
Object reference not set to an instance of an object.
```
Data move jobs fail with a duplicate key error:
```
(error code -1605)
```

The Get-VBOEntityData cmdlet fails with the error:

An item with the same key has already been added.

Download Information

Download VB365 8.5 ISO

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

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

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

2026-06-29T00:00:00Z

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

KB ID:	4874
Product:	Veeam Backup for Microsoft 365 \| 8
Published:	2026-06-29
Last Modified:	2026-06-29

Purpose

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

Note: These instructions apply only to non-immutable object storage repositories that contain backups. Verification and remediation for JET-based repositories and backup copies will be provided in a future update.

Solution

Before You Begin

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

Repair Procedure

The following steps are to be completed for each non-immutable object storage repository that contains SharePoint, OneDrive, and Teams files. The steps in this section use PowerShell commands that reference variables set in one step and called in later steps.

Step 1: Run an Integrity Check

Open PowerShell and import the Veeam Backup for Microsoft 365 PowerShell module:

Import-Module "C:\Program Files\Veeam\Backup365\Veeam.Archiver.PowerShell.dll"

Run the following cmdlet for the repository being investigated:

$repository = Get-VBORepository -Name "Repository Name"
Test-VBORepository -Repository $repository

Step 2: Review the Results

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

The following site has corrupted file data

The following list contains items referencing corrupted files

If neither message appears, no further action is required for that repository.

Step 3: Scan Repository and Flag Affected Items

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

$session = Start-VBORepositoryRepairSession -Repository $repository -Type CleanMissingFilesData -Mode Full -Scope Full
                     
                    

To limit the scope to a specific SharePoint site, use the -WebIds parameter:

$session = Start-VBORepositoryRepairSession -Repository $repository -Type CleanMissingFilesData -Mode Full -WebIds '{InternalWebId}','{InternalWebId}'
                     
                    

Wait for the session to complete before proceeding to Step 4. To verify that a session has completed, check its status using the session object returned in Step 3:

Get-VBORepositoryRepairSession -Id $session.Id
                     
                    

Step 4: Run Backup Jobs

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

Step 5: Review Outcome and Identify Unrecoverable Files

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

Test-VBORepository -Repository $repository -DetailedOutput
                     
                    

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

Files that could not be redownloaded will have log entries containing the following two messages:

Backed-up file is empty:

RepairHistory: FileWasReset

Error Line Example:

[Info] Integrity verifier generated message (repository ID: {repo-guid}, tenant ID: {tenantID}, type: FilesIntegrityVerifier, severity: Error, text: Backed-up file is empty: OrganizationId: {orgGuid}, SiteId: {siteID-guid}, WebId: {webID-guid}, InternalWebId: {intwebID-guid} (file: Id: {fileID-guid}, Version: 513, ContentLength: 0, BytesInStorage: 0, StorageType:None, RepairHistory: FileWasReset).)

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

^(?=.*Backed-up file is empty)(?=.*RepairHistory: FileWasReset).*$

More Information

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

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Email item data export from EWS failed

2026-06-29T00:00:00Z

Email item data export from EWS failed

KB ID:	4867
Product:	Veeam Data Cloud for Microsoft 365 Veeam Backup for Microsoft 365
Published:	2026-06-03
Last Modified:	2026-06-29

Challenge

Exchange Online backup jobs in Veeam Backup for Microsoft 365 and Veeam Data Cloud for Microsoft 365 may fail to process mailboxes, returning one of the following errors:

Processing mailbox  failed with error: Email item data export from EWS failed (item IDs: [...]). The operation has timed out.

Or:

The server cannot service this request right now. Try again later.

Cause

This issue occurs when an Exchange Web Services (EWS) export operation takes longer to complete than the default timeout allows. Exporting very large mailbox items or encountering EWS throttling can prolong the operation past the timeout, causing the backup job to fail.

Solution

For Veeam Data Cloud for Microsoft 365
A fix has been deployed to the environment. No action is needed from Veeam Data Cloud for Microsoft 365 customers.
For Veeam Backup for Microsoft 365
A fix has been included with Veeam Backup for Microsoft 365 8.5.

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.

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

2026-06-29T00: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-07-01

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.

Solution

Veeam Data Cloud for Microsoft 365

No action is required from Veeam Data Cloud for Microsoft 365 users. The platform has been automatically updated to the latest version to address the root cause, ensuring that newly created and changed items are backed up correctly.

Affected items in the backups, if any, that have not changed in production since the last backup remain impacted by the issue. Veeam Data Cloud for Microsoft 365 will remediate the impacted items automatically where possible.

Starting June 30, 2026, a granular remediation process began on a tenant-by-tenant basis. A special maintenance message will be displayed in the UI when the process starts for your organization. During the remediation process, subsequent backup job runs may take longer than usual as all impacted data is reprocessed.

Veeam Backup for Microsoft 365

The root cause of the issue described in this article was resolved starting in Veeam Backup for Microsoft 365 v8.4 (build 8.4.0.1457), ensuring that new and changed items are backed up correctly. All Veeam Backup for Microsoft 365 customers are advised to upgrade to the latest version as soon as possible.

Affected items in the backups, if any, that have not changed in production since the last backup remain impacted by the issue.

Veeam Backup for Microsoft 365 v8.5 (build 8.5.0.1014 introduced a method for customers to remediate those impacted items.
For more information, please review: KB4874: How to Identify and Repair Files That Cannot Be Opened After Restore

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.

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

2026-06-29T00: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-06-29

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

Additional Security Enhancements for Salesforce Connections

To further align with Salesforce security standards, the following security options are enabled on both the External Client App and the legacy Connected App (the latter for customers who have not yet transitioned to the ECA):

Proof Key for Code Exchange — Already Enabled
Refresh Token Rotation — Already Enabled
Refresh Token 30-Day Idle Timeout — Already Enabled
Allowlist Ranges for Refresh Tokens — Will be enabled on July 6th, 2026.

After these options take effect, an existing refresh token may no longer be valid under the new rules the next time a Salesforce access token expires. If this occurs, a prompt to re-authorize the Salesforce connection is displayed so that a new, compliant refresh token can be issued.

In addition, once Allowlist Ranges for Refresh Tokens is enabled, customers who have Login IP Ranges configured for the backup user must add the following IP addresses, which are used for token refresh, to the allowed list:

EMEA: 4.223.102.146 , 9.223.216.186
APJ: 52.253.96.103 , 130.33.216.155
AMER: 52.238.211.143 , 20.236.255.222

This change might also require re-authorization of connections to Salesforce organizations.

Recommended action: To avoid missing an expired-connection event, log in to the product as soon as possible and verify that the alert for an expired Salesforce connection token is configured with a valid email address for notifications. For instructions, see Managing Notifications in the Veeam Data Cloud for Salesforce User Guide.

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

ECA Configuration Considerations

After the managed package is installed, the External Client App can be modified in Salesforce to apply additional security restrictions, such as limiting access to specific user accounts or adjusting the token refresh policy.

However, the Immediately expire refresh token option in OAuth Policies > App Authorization must not be enabled. If this option is selected, Veeam Data Cloud cannot maintain an active connection to the Salesforce organization, and the backup policy will require manual re-authorization each day to run.

Troubleshooting Deployment of External Client App (ECA) for Veeam Data Cloud

If the following error occurs when installing the managed package:

Missing feature: Installing this package requires the following feature and its associated permissions: External Client Applications

Please ensure that:

The installing user has the Create, Edit, and Delete External Client Apps permission enabled under System Permissions.
The External Client Applications feature is enabled for the organization.
This can be verified by confirming that External Client App Manager appears in Setup. If it does not, navigate to Setup > External Client App > Settings, select the Opt in for external client apps checkbox, and click Save.

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.

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

2026-06-29T00:00:00Z

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

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

Purpose

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

Solution

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

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

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

This table lists only actively supported versions.

Swipe to show more of the table

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

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

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Build Numbers and Versions of Veeam Backup for Microsoft 365

2026-06-29T00:00:00Z

Build Numbers and Versions of Veeam Backup for Microsoft 365

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

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

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

_{Note: Prior to version 6.0, the product was known as Veeam Backup for Microsoft Office 365.}

Version	Console Build	Build in Logs	Release Date	Release Notes
*Veeam Backup for Microsoft 365* 8.5 Releases**
Veeam Backup for Microsoft 365 8.5	8.5.0.1014	13.5.0.1014	2026-06-29	KB4873 HTML
*Veeam Backup for Microsoft 365* 8.4 Releases**
Veeam Backup for Microsoft 365 8.4	8.4.0.1457	13.4.0.1457	2026-04-16	KB4843 HTML
*Veeam Backup for Microsoft 365* 8.3 Releases**
Veeam Backup for Microsoft 365 8.3	8.3.0.2201	13.3.0.2201	2025-12-18	KB4809 HTML
*Veeam Backup for Microsoft 365* 8.2 Releases**
Veeam Backup for Microsoft 365 8.2 P20251031	8.2.0.2202	13.2.0.2202	2025-11-06	KB4751
Veeam Backup for Microsoft 365 8.2	8.2.0.2008	13.2.0.2008	2025-10-23	KB4751 HTML
*Veeam Backup for Microsoft 365* 8.1 Releases**
Veeam Backup for Microsoft 365 8.1.2.3301	8.1.2.3301	13.1.2.3301	2025-10-24	KB4711 HTML
Veeam Backup for Microsoft 365 8.1.2.180	8.1.2.180	13.1.2.180	2025-07-01
Veeam Backup for Microsoft 365 8.1.1.159	8.1.1.159	13.1.1.159	2025-04-02
Veeam Backup for Microsoft 365 8.1.0.3503	8.1.0.3503	13.1.0.3503	2025-02-27
Veeam Backup for Microsoft 365 8.1.0.331	8.1.0.331	13.1.0.331	2025-02-11
Veeam Backup for Microsoft 365 8.1	8.1.0.305	13.1.0.305	2025-01-23
*Veeam Backup for Microsoft 365* 8 Releases**
Veeam Backup for Microsoft 365 8.0.5	8.0.5.20	13.0.5.20	2024-11-14	KB4656 HTML
Veeam Backup for Microsoft 365 8.0.4	8.0.4.29	13.0.4.29	2024-10-30
Veeam Backup for Microsoft 365 8.0.3.1073	8.0.3.1073	13.0.3.1073	2024-10-16
Veeam Backup for Microsoft 365 8 P20241004	8.0.3.1044	13.0.3.1044	2024-10-08
Veeam Backup for Microsoft 365 8 P20240910	8.0.2.200	13.0.2.200	2024-09-11
Veeam Backup for Microsoft 365 8	8.0.2.159	13.0.2.159	2024-09-03
*Veeam Backup for Microsoft 365* 7a Releases**
Veeam Backup for Microsoft 365 7a P20240418	7.1.0.2031	12.1.0.2031	2024-04-24	KB4533
Veeam Backup for Microsoft 365 7a P20240411	7.1.0.1502	12.1.0.1502	2024-04-15
Veeam Backup for Microsoft 365 7a P20240123	7.1.0.1501	12.1.0.1501	2024-01-25
Veeam Backup for Microsoft 365 7a P20231218	7.1.0.1401	12.1.0.1401	2023-12-26
Veeam Backup for Microsoft 365 7a	7.1.0.1301	12.1.0.1301	2023-12-05	PDF
*Veeam Backup for Microsoft 365* 7 Releases**
Veeam Backup for Microsoft 365 7 P20240123	7.0.0.4901	12.0.0.4901	2024-01-25	KB4425
Veeam Backup for Microsoft 365 7 P20231218	7.0.0.4551	12.0.0.4551	2023-12-25
Veeam Backup for Microsoft 365 7 P20231015	7.0.0.4388	12.0.0.4388	2023-10-15
Veeam Backup for Microsoft 365 7 P20231005	7.0.0.4385	12.0.0.4385	2023-10-12
Veeam Backup for Microsoft 365 7 P20230704	7.0.0.3968	12.0.0.3968	2023-07-13
Veeam Backup for Microsoft 365 7 P20230512	7.0.0.3604	12.0.0.3604	2023-05-24
Veeam Backup for Microsoft 365 7 P20230421	7.0.0.3007	12.0.0.3007	2023-04-25
Veeam Backup for Microsoft 365 7 P20230302	7.0.0.2914	12.0.0.2914	2023-03-09
Veeam Backup for Microsoft 365 7	7.0.0.2911	12.0.0.2911	2023-02-28	PDF
*Veeam Backup for Microsoft 365* 6 Releases**
Veeam Backup for Microsoft 365 6a P20230322	6.1.0.1015	11.2.0.1015	2023-03-28	KB4347
Veeam Backup for Microsoft 365 6a P20221215	6.1.0.438	11.2.0.438	2022-12-20
Veeam Backup for Microsoft 365 6a P20220926	6.1.0.423	11.2.0.423	2022-10-06
Veeam Backup for Microsoft 365 6a P20220825	6.1.0.254	11.2.0.254	2022-08-25
Veeam Backup for Microsoft 365 6a	6.1.0.222	11.2.0.222	2022-08-10	PDF KB4344
Veeam Backup for Microsoft 365 6 P20220718	6.0.0.400	11.1.0.400	2022-07-27	KB4285
Veeam Backup for Microsoft 365 6 P20220524	6.0.0.385	11.1.0.385	2022-05-31
Veeam Backup for Microsoft 365 6 P20220413	6.0.0.379	11.1.0.379	2022-05-05
Veeam Backup for Microsoft 365 6 GA	6.0.0.367	11.1.0.367	2022-03-09	PDF KB4286
*Veeam Backup for Microsoft Office 365* 5 Releases**
Veeam Backup for Microsoft Office 365 5d Cumulative Patch KB4278	5.0.3.1063	10.0.5.1063	2022-02-08	KB4278
Veeam Backup for Microsoft Office 365 5d Cumulative Patch KB4270	5.0.3.1060	10.0.5.1060	2022-01-10	KB4270
Veeam Backup for Microsoft Office 365 5d Cumulative Patch KB4235	5.0.3.1051	10.0.5.1051	2021-12-16	KB4235
Veeam Backup for Microsoft Office 365 5d Cumulative Patch KB4222	5.0.3.1035	10.0.5.1035	2021-10-22	KB4222
Veeam Backup for Microsoft Office 365 5d	5.0.3.1033	10.0.5.1033	2021-09-22	PDF KB4203
Veeam Backup for Microsoft Office 365 5c Cumulative Patch KB4187	5.0.2.42	10.0.4.42	2021-09-01	KB4187
Veeam Backup for Microsoft Office 365 5c	5.0.2.22	10.0.4.22	2021-06-28	KB4181
Veeam Backup for Microsoft Office 365 5b Cumulative Patch KB4158	5.0.1.252	10.0.3.252	2021-05-31	KB4158
Veeam Backup for Microsoft Office 365 5b Cumulative Patch KB4135	5.0.1.225	10.0.3.225	2021-04-12	KB4135
Veeam Backup for Microsoft Office 365 5b Cumulative Patch KB4124	5.0.1.207	10.0.3.207	2021-03-12	KB4124
Veeam Backup for Microsoft Office 365 5b	5.0.1.179	10.0.3.179	2021-02-08	PDF KB4092
Veeam Backup for Microsoft Office 365 5a	5.0.0.1070	10.0.2.1070	2020-12-14	PDF KB4082
Veeam Backup for Microsoft Office 365 5 Day 0 Update	5.0.0.1063	10.0.2.1063	2020-12-04	PDF
Veeam Backup for Microsoft Office 365 5 GA	5.0.0.1061	10.0.2.1061	2020-12-03	PDF
*Veeam Backup for Microsoft Office 365* 4 Releases**
Veeam Backup for Microsoft Office 365 4c Cumulative Patch KB4099	4.0.1.625	10.0.1.625	2021-02-16	KB4099
Veeam Backup for Microsoft Office 365 4c Cumulative Patch KB4083	4.0.1.612	10.0.1.612	2020-12-24	KB4083
Veeam Backup for Microsoft Office 365 4c Cumulative Patch KB3222	4.0.1.545	10.0.1.545	2020-07-09	KB3222
Veeam Backup for Microsoft Office 365 4c Day 0 Update	4.0.1.531	10.0.1.531	2020-06-16	KB3145
Veeam Backup for Microsoft Office 365 4b Cumulative Patch KB3119	4.0.0.2549	9.6.6.2549	2020-03-31	KB3119
Veeam Backup for Microsoft Office 365 4b	4.0.0.2516	9.6.6.2516	2020-01-31	KB3065
Veeam Backup for Microsoft Office 365 4a Cumulative Patch KB3089	4.0.0.1580	9.6.6.1580	2020-03-10	KB3089
Veeam Backup for Microsoft Office 365 4a	4.0.0.1553	9.6.6.1553	2020-01-21	KB3035
Veeam Backup for Microsoft Office 365 4 GA	4.0.0.1345	9.6.6.1345	2019-11-26	PDF
*Veeam Backup for Microsoft Office 365* 3 Releases**
Veeam Backup for Microsoft Office 365 3 GA	3.0.0.422	9.6.5.422	2019-04-02	PDF
*Veeam Backup for Microsoft Office 365* 2 Releases**
Veeam Backup for Microsoft Office 365 2 Cumulative Patch KB2809	2.0.0.814	9.6.3.814	2018-12-28	KB2809
Veeam Backup for Microsoft Office 365 2 Cumulative Patch KB2765	2.0.0.594	9.6.3.594	2018-09-26	KB2765
Veeam Backup for Microsoft Office 365 2 GA	2.0.0.567	9.6.3.567	2018-07-24	PDF
*Veeam Backup for Microsoft Office 365* 1 Releases**
Veeam Backup for Microsoft Office 365 1.5 GA	1.5.0.1099	9.6.0.1099	2017-10-03	PDF
Veeam Backup for Microsoft Office 365 1 Update 1	1.0.0.912	9.5.0.912	2017-01-20	KB2224 PDF
Veeam Backup for Microsoft Office 365 1 GA	1.0.0.860	9.5.0.860	2016-11-29	PDF

Swipe to show more of the table

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.

Veeam Backup for Microsoft 365 Upgrade Paths

2026-06-29T00:00:00Z

Veeam Backup for Microsoft 365 Upgrade Paths

KB ID:	4098
Product:	Veeam Backup for Microsoft 365 \| 8
Published:	2021-02-09
Last Modified:	2026-06-29

Shared Server with Veeam Backup & Replication

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

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

Purpose

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

Solution

Consider the following when planning for an upgrade:

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

End of Support Upgrade Path

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

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

For example:

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

7 to 8.5

Path: 7 (7.0.x) → 8.4 → 8.5

7a to 8.5

Path: 7a (7.1.x) → 8.4 → 8.5

8.0 to 8.5

Path: 8.0 (8.0.x) → 8.5

Upgrade to Veeam Backup for Microsoft 365 8.5

8.1 to 8.5

Path: 8.1 (8.1.x) → 8.5

Upgrade to Veeam Backup for Microsoft 365 8.5

8.2 to 8.5

Path: 8.2 (8.2.x) → 8.5

Upgrade to Veeam Backup for Microsoft 365 8.5

8.3 to 8.5

Path: 8.3 (8.3.x) → 8.5

Upgrade to Veeam Backup for Microsoft 365 8.5

8.4 to 8.5

Path: 8.4 (8.4.x) → 8.5

Upgrade to Veeam Backup for Microsoft 365 8.5

What You Do After Upgrade

After upgrading Veeam Backup for Microsoft 365, be sure to review the "What You Do After Upgrade" section of the user guide.

More Information

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Restore to AWS EC2 Fails with: "ClientError: Unknown OS / Missing OS files" or "FirstBootFailure"

2026-06-25T00:00:00Z

Restore to AWS EC2 Fails with: "ClientError: Unknown OS / Missing OS files" or "FirstBootFailure"

KB ID:	4814
Product:	Veeam Backup & Replication \| 12.3 \| 12.3.1 \| 12.3.2 \| 13
Published:	2026-01-21
Last Modified:	2026-06-25

Challenge

When restoring a VM to AWS EC2, one of the following errors occurs:

StatusMessage: "CLIENT_ERROR : ClientError: Unknown OS / Missing OS files."

Failed to import machine to Amazon EC2: CLIENT_ERROR : FirstBootFailure: This import request failed because the instance failed to boot and establish network connectivity.

Cause

This issue occurs because Amazon recently began encrypting disks upon creation, resulting in new disks containing random data rather than zeros. When restoring to EC2 using the helper appliance, Veeam Backup & Replication restores backup data onto those disks, which are then sent for AWS import. However, since the disks contain extraneous random data in addition to the restored data, the AWS import process may fail to correctly identify boot partitions for certain guest operating systems, resulting in the reported errors.

Solution

Direct recovery to AWS EC2 without using the helper appliance works successfully and does not encounter this issue.

Note: This issue does not affect the restore of AWS EC2-native VMs. For those EC2-native VMs, it is recommended to use the helper appliance.

For Veeam Backup & Replication 13.0.x

In Veeam Backup & Replication 13.0.x (e.g., 13.0 and 13.0.1), disable the option "Use the helper appliance" in the restore wizard.

Reference: Restoring to Amazon EC2 > Step 8. Configure Helper Appliance

Note: A solution to resolve the root issue will be included in a future Veeam Backup & Replication release.

For Veeam Backup & Replication 12.3.x

In Veeam Backup & Replication v12.3.x (e.g., 12.3, 12.3.1, and 12.3.2), the option for "Use the helper appliance" during the restore process is greyed out and cannot be disabled. To make the option selectable, create the following registry value on the Veeam Backup Server. After configuring the registry value, the “Use helper appliance” option should be disabled when restoring non-AWS EC2-native VMs to AWS EC2.

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: PublicCloudRestoreEnableApplianceSelection
Value Type: DWORD (32-Bit) Value
Value Data: 1

Note: The Veeam Backup & Replication Console must be closed and reopened for the setting to take effect.

PowerShell command to set registry value:

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

If the Helper Appliance Cannot Be Avoided

Restoring without the helper appliance, as described above, is the recommended approach. When restoring without the helper appliance is not possible, the AmazonZeroDisksOnRestore registry value can be created to enable a disk pre-zeroing mechanism that allows the restore to complete successfully while the helper appliance is used.

Note: The pre-zeroing mechanism significantly increases restore time. The restore can be two to three times slower than a regular data upload.

This registry value is available in Veeam Backup & Replication 12.3.2.4465 and later.

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: AmazonZeroDisksOnRestore
Value Type: DWORD (32-Bit) Value
Value Data: 1

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.

How to Enable the Firewall Rules Required by Veeam ONE for Event Collection

2026-06-18T00:00:00Z

How to Enable the Firewall Rules Required by Veeam ONE for Event Collection

KB ID:	2696
Product:	Veeam ONE \| 12
Published:	2018-07-30
Last Modified:	2026-06-18

Purpose

This article describes how to enable the Microsoft Windows Firewall rules that Veeam ONE requires to collect event data from monitored Windows servers, such as Hyper-V hosts and Veeam Backup & Replication servers.

Solution

Using Windows Defender Firewall with Advanced Security

On a server with the Desktop Experience, enable the rules using the firewall management console:

Open Windows Defender Firewall with Advanced Security ( wf.msc ).
Select Inbound Rules.
Locate each rule listed below, right-click it, and select Enable Rule.
- Remote Event Log Management (NP-In)
- Remote Event Log Management (RPC)
- Remote Event Log Management (RPC-EPMAP)
- COM+ Network Access (DCOM-In)

Using PowerShell

Alternatively, launch an Administrative PowerShell terminal and run the following commands:

Set-NetFirewallRule -Name 'RemoteEventLogSvc-NP-In-TCP' -Enabled True
Set-NetFirewallRule -Name 'RemoteEventLogSvc-In-TCP' -Enabled True
Set-NetFirewallRule -Name 'RemoteEventLogSvc-RPCSS-In-TCP' -Enabled True
Set-NetFirewallRule -Name 'ComPlusNetworkAccess-DCOM-In' -Enabled True
                     
                    

More Information

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Onboarding a Microsoft 365 Organization Fails with: service principal name is already present for the tenant

2026-06-16T00:00:00Z

Onboarding a Microsoft 365 Organization Fails with: service principal name is already present for the tenant

KB ID:	4871
Product:	Veeam Data Cloud for Microsoft 365
Published:	2026-06-16
Last Modified:	2026-06-16

Challenge

When signing in with a device code during onboarding of a Microsoft 365 organization in Veeam Data Cloud for Microsoft 365, the following error occurs:

AADSTS650051: Consent action for Application '' failed due to following error: The  service principal name is already present for the tenant  paramName: ServicePrincipalName, paramValue: , objectType: System.String

Cause

This error occurs when a service principal from a previous onboarding attempt is still present in the customer tenant.

Under normal conditions, onboarding proceeds as follows:

The user signs in with a device code, and a new service principal is created in the customer tenant.
When Connect is clicked, the onboarding process uses that service principal to obtain an authentication token, then deletes the service principal and begins onboarding the organization.

However, if an error occurs during organization onboarding (for example, the account does not have sufficient permissions, or an organization with the same domain already exists), onboarding fails after the service principal has been deleted. If a new device code is then generated and used to sign in again too soon, the onboarding process attempts to create a service principal with the same name as the one from the failed attempt. Because service principal deletion is a soft delete that takes approximately 5 to 15 minutes to complete in Azure, the name remains in the tenant even though the Azure portal no longer displays the service principal. As a result, the error occurs.

Solution

If this error occurs, wait approximately 15 minutes for the soft-deleted service principal to be fully removed, then regenerate the device code and sign in again.

Deleting the Enterprise application will not speed up removal of the soft-deleted service principal and should not be performed.

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.

List of Security Fixes and Improvements in Veeam Kasten for Kubernetes

2026-06-16T00: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 \| 3 \| 5 \| 5.5 \| 6 \| 6.5
Published:	2026-03-02
Last Modified:	2026-06-16

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:

Veeam Kasten for Kubernetes — Release Notes

Security Fixes and Improvements

**Veeam Kasten for Kubernetes 8.5.12**

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

**Veeam Kasten for Kubernetes 8.5.10**

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

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

**Veeam Kasten for Kubernetes 8.5.5**

Upgrade to Go 1.26.1 to address CVE-2026-25679 and CVE-2026-27142
Updated the UBI base image to address CVE-2026-4111

**Veeam Kasten for Kubernetes 8.5.3**

Upgrade to Go 1.25.7 to address CVE-2025-61732.

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

Upgrade to Go 1.25.6 to address CVEs:
Updated base image used to build Veeam Kasten container images to pull in latest security updates.

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

Upgrade to Go 1.17.7 to mitigate CVE-2022-23772 and CVE-2022-23806.

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

Update Grafana version to pull in fix for CVE-2021-43798.

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.

How to use SQL Management Studio to Apply SQL-Based Hotfixes to the Veeam ONE Database

2026-06-15T00:00:00Z

How to use SQL Management Studio to Apply SQL-Based Hotfixes to the Veeam ONE Database

KB ID:	4414
Product:	Veeam ONE \| 10 \| 11 \| 12 \| 12.1 \| 12.2 \| 12.3 \| 13
Published:	2023-03-07
Last Modified:	2026-06-15

Purpose

This article documents applying a SQL query script-based hotfix for the Veeam One database.

Solution

Identify the Location of the Veeam ONE Database

If Veeam ONE is installed, open the Veeam ONE Settings Utility to view the current SQL Server settings.
C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe

Alternatively, check the following registry values in the following key:
HKLM\SOFTWARE\Veeam\Veeam ONE Monitor\db_config
- host
- db_name

Hotfix Deployment Guide

Disable and Stop all Veeam ONE Services
1. Veeam ONE v13:
  - Veeam Analytics Service
  - Veeam ONE Monitoring Service
  - Veeam ONE Error Reporting Service
  - Veeam ONE Reporting Service
  - Veeam ONE Caching Service
2. Veeam ONE v12:
  - Veeam ONE Monitoring Service
  - Veeam ONE Reporting Service
  - Veeam ONE Error Reporting Service
  - Veeam ONE Agent Service

To automate this, run the following commands in an Administrative Command Prompt.
^{Command prompt is used instead of PowerShell because older versions of PowerShell were unable to set service startup to delayed start.}

For Veeam ONE v13:

net stop VeeamOAS
net stop VeeamDCS
net stop VeeamERS
net stop VeeamRSS
net stop VeeamCHS
sc config VeeamOAS start= disabled
sc config VeeamDCS start= disabled
sc config VeeamERS start= disabled
sc config VeeamRSS start= disabled
sc config VeeamCHS start= disabled
echo Services stopped and startup types set to disabled.
                     
                    

For Veeam ONE v12:

net stop VeeamDCS
net stop VeeamOneAgentSvc
net stop VeeamRSS
net stop VeeamCRS
sc config VeeamDCS start= disabled
sc config VeeamCRS start= disabled
sc config VeeamOneAgentSvc start= disabled
sc config VeeamRSS start= disabled
echo Services stopped and startup types set to disabled.
                     
                    

Download the hotfix provided by the Veeam Technical Support engineer.
Unpack the hotfix archive.
Back up the Veeam ONE database. See KB2356.
Open Microsoft SQL Management Studio and connect to the SQL Instance hosting the Veeam One database.

Note:
- You may need to launch SQL Management Studio using Run as Administrator.
- If the account you signed in to the SQL server does not have permission to access the SQL instance, you may have to use Run as different user to launch SQL Management Studio as a user who has access to the SQL instance.
In Microsoft SQL Management Studio, use the Ctrl+O hotkey to open the hotfix script.

Ensure that the correct database is selected from the drop-down list.

Execute the hotfix query.

Review the results and ensure that the script completes without errors.

Enable the Veeam One services and Start them.
1. Veeam ONE v13:
  - Veeam Analytics Service – set to Automatic (Delayed Start)
  - Veeam ONE Caching Service – set to Automatic
  - Veeam ONE Error Reporting Service – set to Automatic
  - Veeam ONE Monitoring Service – set to Automatic
  - Veeam ONE Reporting Service – set to Automatic (Delayed Start)
2. Veeam ONE v12:
  - Veeam ONE Monitoring Service – set to Automatic
  - Veeam ONE Reporting Service – set to Automatic (Delayed Start)
  - Veeam ONE Error Reporting Service – set to Automatic
  - Veeam ONE Agent Service – set to Automatic (Delayed Start)

To automate this, run the following commands in an Administrative Command Prompt.
^{Command prompt is used instead of PowerShell because older versions of PowerShell could not set service startup to delayed start.}

For Veeam ONE v13:

sc config VeeamOAS start= delayed-auto
sc config VeeamCHS start= auto
sc config VeeamERS start= auto
sc config VeeamDCS start= auto
sc config VeeamRSS start= delayed-auto
net start VeeamERS
net start VeeamDCS
net start VeeamOAS
net start VeeamRSS
net start VeeamCHS
echo Service startup set to default and started.

                     
                    

For Veeam ONE v12:

sc config VeeamDCS start= auto
sc config VeeamCRS start= auto
sc config VeeamOneAgentSvc start= delayed-auto
sc config VeeamRSS start= delayed-auto
net start VeeamCRS
net start VeeamDCS
net start VeeamOneAgentSvc
net start VeeamRSS
echo Service startup set to default and started.
                     
                    

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.

Support Statement — Exchange Web Services (EWS) Deprecation

2026-06-12T00: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-07-06

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.

Note: This article previously stated, "Starting July 1, 2026, Microsoft will begin blocking EWS access for Frontline Worker mailbox types (Kiosk, F1, and F3) as the first enforcement step of the EWS deprecation." However, on June 11, Microsoft updated the blog post titled "Update to EWS Access for Kiosk / Frontline Worker Licensed Users" to change that deadline to October 1, 2026.

Solution

Veeam software that currently uses EWS will be transitioned to the Microsoft Graph API to ensure continued compatibility and data protection capabilities.

As part of this transition, permission changes are required for all Veeam customers protecting Microsoft 365 data.

For Veeam Data Cloud for Microsoft 365 customers, the application logic will be updated in the service. Performing app reauthorization will assign the permissions necessary.
For Veeam Backup for Microsoft 365, an upcoming release will provide support for the transition from EWS to Microsoft Graph.

Preparing for the October 1, 2026 EWS Retirement

Although EWS remains available today, administrators can prepare now so that backups continue without interruption once EWS access is retired. Complete the applicable steps below for your Veeam product.

**Veeam Data Cloud for Microsoft 365 — Required Action**

To prepare for the retirement of EWS access, a Microsoft 365 Global Admin must reauthorize the Veeam Data Cloud application:

Log in to the Veeam Data Cloud portal.
Go to Settings → Microsoft 365 → Reauthorize Veeam Data Cloud.
Click Reauthorize existing app registration.

**Veeam Backup for Microsoft 365 — Required Action**

To prepare for the retirement of EWS access, ensure that the necessary Microsoft Graph permissions are assigned to the backup app registrations in Microsoft Entra ID.

More Information

What happens if permissions are not added before the EWS deprecation?

Once Microsoft retires EWS access, backups will fail until the required permissions are added. You can add the permissions at any time and backups will resume; however, the first backup afterward will be a full sync backup, and a coverage gap will exist during the period the permissions were missing.

Veeam Backup for Microsoft 365 customers will also need to upgrade to the upcoming release once it becomes available.

Unexpected Early EWS Access Termination

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, as discussed in the solution on KB4796.

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.

Veeam Support Knowledge Base

"Warning: Exchange account was not found"

"Warning: Exchange account was not found"

Challenge

Cause

Solution

Data Import for Veeam Data Cloud for Salesforce

Data Import for Veeam Data Cloud for Salesforce

Purpose

Solution

Overview

Eligibility Requirements

What's Supported Today

Import Data Preparation

Supported Storage

File Format

File Naming

Folder Structure

Data Requirements and Known Limitations

Monitoring and Resiliency

Next Steps

Veeam My Account Portal - MFA Guide

Veeam My Account Portal - MFA Guide

Purpose

Solution

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

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

Veeam Agent for Linux 13.0.2

Veeam Agent for Linux 6.3.2

Veeam Agent for Linux 6.3.1

Veeam Agent for Linux 6.3

Veeam Agent for Linux 6.2

Veeam Agent for Linux 6.1.2

Veeam Agent for Linux 6.1

Veeam Agent for Linux 6.0.3

Veeam Agent for Linux 6.0.2

Veeam Agent for Linux 6.0

End of Life Versions

Veeam Agent for Linux 5.0.2

Veeam Agent for Linux 5.0.1

Veeam Agent for Linux 5.0

Release Information for IBM FlashSystem Plug-In for Veeam Backup & Replication

Release Information for IBM FlashSystem Plug-In for Veeam Backup & Replication

Requirements

What's New

Known Issues

Version 8.4.0 and higher

Version 8.4.0 through 8.5.0

Version 8.4.2 and higher (iSCSI connectivity)

Version 8.5.1 and higher

Version 8.7.1 and higher

Download Information

For Veeam Backup & Replication on Windows

For Veeam Backup & Replication on Veeam Software Appliance

Previous Versions

IBM FlashSystem Plug-In for Veeam Backup & Replication [2.3.80] - 2025-11-19

IBM FlashSystem Plug-In for Veeam Backup & Replication [2.0.26] - 2024-08-28

The HTTP request was forbidden with client authentication scheme

The HTTP request was forbidden with client authentication scheme

Challenge

Cause

Solution

Part 1: Set the EwsEnabled Flag at the Tenant (Organization) Level

Part 2: Set the EwsEnabled Flag at the User (Mailbox) Level

Part 3: Wait and Verify Results

More Information

Similar Issue from December 2025

Challenge

Cause

Solution

Release Information for Veeam Backup for Microsoft 365 8.5

Release Information for Veeam Backup for Microsoft 365 8.5

Requirements

Release Information

8.5.0.1014

2026-06-30

New Features and Enhancements

Bug Fixes

General

Backup and Backup Copy

Part 1: Set the `EwsEnabled` Flag at the Tenant (Organization) Level

Part 2: Set the `EwsEnabled` Flag at the User (Mailbox) Level