Veeam Support Knowledge Base

Veeam Backup & Replication Platform Migration Guide (Windows to Linux)

2026-07-21T00:00:00Z

Veeam Backup & Replication Platform Migration Guide
(Windows to Linux)

KB ID:	4800
Product:	Veeam Backup & Replication \| 13
Published:	2026-02-19
Last Modified:	2026-07-21

Article Applicability

This article is related to a new capability to migrate the configuration of a Windows-based Veeam Backup & Replication deployment to a Veeam Software Appliance. Due to the variability in how Veeam Backup & Replication can be used, configured, and deployed, and the complexity of migrating software configuration between platforms, this guide may not cover every possible limitation or consideration.

This article will be updated as more migrations occur and as customer feedback is received.

Purpose

This article documents potential limitations and considerations when performing a Veeam Backup & Replication configuration migration from a Windows-based deployment to a Linux-based (Veeam Software Appliance) deployment.

Note: Platform migration is supported only from Windows-based Veeam Backup & Replication to the Veeam Software Appliance (Linux-based). Reverse migration from Linux to Windows is not available, and no such functionality is currently planned.

Before You Begin

Before reviewing limitations or proceeding with the migration guidance, please complete the following mandatory preparation steps.

Pilot migration projects are currently being performed in close cooperation with Technical Support, Sales Engineers, and Product Management. If you are considering migrating from a Windows-based installation to the Veeam Software Appliance (VSA) to take advantage of all supported features, complete the steps below before continuing with this article.

Preparation Steps

Ensure that you have instance-based licenses.
The Veeam Software Appliance supports only instance-based Veeam Universal License (VUL). To verify your license type, open the Veeam Backup & Replication Console and review the License Information. If the license specifies "Sockets," it is a legacy socket-based license and must be migrated to VUL before proceeding. For details on migration and pricing, contact your preferred reseller or the Veeam Renewals Team.
Update your Windows deployment to the latest available Veeam Backup & Replication 13.0.x patch.
This ensures your current installation is ready for migration and includes the most recent fixes that may affect the migration process.

VSA Migration Version Limitation

The Windows-to-Linux conversion path has been tested and is supported on Veeam Backup & Replication 13.0.x only. It has not been validated against future releases, including 13.1, and will not be supported on that release. If you plan to convert, do not upgrade to 13.1 until your conversion to the Veeam Software Appliance is complete, or you will remain on Windows.

Enable the “Receive proactive support” option in the product.
This allows Veeam to evaluate whether your backup server configuration can be migrated to VSA without issues.
Review the "Before you begin, complete the following mandatory steps" list on the VSA Conversion Portal.

Solution

Limitations due to Veeam Software Appliance Capabilities

Veeam Cloud Connect deployments cannot be migrated to Veeam Software Appliance.
Storage system snapshot integration support may differ between Windows-based Veeam Backup & Replication deployments and Veeam Software Appliance (Linux-based) deployments. Customers considering migration are encouraged to review the User Guide and be aware that integration with their storage system may be affected.

Note: For HPE Alletra 5000, 6000, Nimble, some versions of Nimble OS may not be supported when the Veeam Software Appliance operates in FIPS-compliant mode.
Any configuration associated with the Veeam Plug-in for Google Cloud will not be migrated because the Veeam Plug-in for Google Cloud is only available for Microsoft Windows-based backup servers.
The Veeam Software Appliance is only compatible with version 13 of Veeam Agents (Veeam Agent for Microsoft Windows, Veeam Agent for Linux, or Veeam Agent for Mac). All remote machines operating Veeam Agents that will communicate with the Veeam Software Appliance after migration must be upgraded to version 13 to ensure communication is maintained.

Pre-Migration Considerations

If the Windows-based Veeam Backup & Replication deployment, whose database is hosted on Microsoft SQL, was at any time in the past upgraded from a version older than v12, and there are still job history sessions in the database from prior to that upgrade, the migration to Veeam Software Appliance will fail. If this occurs, the solution is to reduce the session history retention to a number of weeks that is less than the last pre-v12 historical job session entry (the day the machine was upgraded to v12).
Make sure all machines managed by the current Veeam Backup & Replication deployment on Windows are accessible by the Veeam Software Appliance (consider: networks, firewalls, and DNS). This is important because the existing deployment and the new Veeam Software Appliance might be on separate networks or domains, so after migration, you need to confirm that the Veeam Software Appliance can connect to the current infrastructure.
If the original Veeam Backup & Replication server was used as the source for a file-to-tape job, the original backup server's short hostname must be used when selecting the Source server during migration. That short hostname must be resolvable from the Veeam Software Appliance.
During the migration to Veeam Software Appliance, Entra ID Tenant Backup jobs are migrated, but the primary backup data associated with those jobs is not migrated and remains on the original PostgreSQL instance. There are three options for ensuring backup continuity, listed below from least to most complicated:
- [Easy] Prior to migration, configure the original Entra ID Tenant Backup jobs to use a secondary destination (a standard backup repository). A remote repository that remains available immediately after migration is recommended, rather than a repository hosted on the backup server being migrated.
  
  After migration, the secondary backup data is used to repopulate the Veeam Software Appliance.
  
  This procedure does not restore any data to your production Microsoft Entra ID tenant. Although the operation is named Restore Entra ID tenant backup copy, it only retrieves the existing backup from the secondary copy and imports it into the local PostgreSQL database that the Veeam Software Appliance uses to store Entra ID Tenant backups. The data is loaded into this appliance-managed repository so that the backup job can be reconnected to it. Your production Entra ID environment is never contacted or modified during this process.
  1. In the Veeam Backup & Replication console, open Home > Backups > Disk (Copy), select the tenant, run Restore Entra ID tenant backup copy, and choose a restore point.
  2. When the import completes, the backup appears under Home > Backups > Disk (Imported).
  3. In the Entra ID Tenant Backup job settings, use the map function to connect the job to the imported backup.
- [Advanced] If the migration has already been completed and the jobs did not have a secondary destination configured, it is possible to configure the Veeam Software Appliance's Entra ID Tenant Backup Repository to use the original PostgreSQL Instance. Then, use the map function within the Entra ID Tenant Backup jobs to reconnect the job to the backup data. This solution requires keeping the machine that hosts the original PostgreSQL instance available to capture Entra ID Tenant backups.
- [Expert] If the migration has already been completed, the jobs did not have a secondary destination configured to restore, and you do not wish to keep the machine hosting the original (pre-migration) PostgreSQL instance storing the Entra ID Tenant backups in service, the database storing the Entra ID Tenant backups must be migrated manually. Use 'pg_dump' to export the existing database from the original PostgreSQL instance, move that database dump to the Veeam Software Appliance, access the root shell of the Veeam Software Appliance via the Terminal UI, and use 'pg_restore' to restore the database to the local PostgreSQL instance. Then, use the map function within the Entra ID Tenant Backup jobs to reconnect the job to the backup data.
Configuration information for CDP jobs will not be migrated and must be reconfigured manually after the migration is complete.

Agent Management Related

Before migration, all Veeam Agent Backup Policies that are disabled must have their configurations applied successfully. Additionally, machines included in these backup policies and part of a Protection Group for Computers with Pre-installed Backup Agents need to be synced with Veeam Backup & Replication after the policy is disabled. This ensures that the agents recognize the policy as disabled. If these steps are not completed, the migration will fail.
All Veeam Agents (Veeam Agent for Microsoft Windows, Veeam Agent for Linux, or Veeam Agent for Mac) installed on remote machines communicating with Veeam Backup & Replication must be upgraded to version 13 prior to migration. The Veeam Software Appliance only supports version 13 and higher of Veeam Agents.
Before migrating, remove all local (non-Domain) account entries from the access permissions of any repositories where granular permissions have been configured. If the entries for local (non-domain) accounts remain after migration, the Veeam Software Appliance will be unable to resolve Windows local account SIDs, resulting in a "SID not found" error that prevents editing repository access permissions until all local accounts are removed.

Storage Management Related

If either of the following Storage Systems were added to Veeam Backup & Replication, you must ensure that the timezone set within the Veeam Software Appliance settings matches the timezone used by the Windows machine where Veeam Backup & Replication was installed. This will ensure important data created by the old Veeam Backup & Replication deployed associated with the Storage Snapshots is not lost. Due to plugin limitations, the timezone of the machine hosting the Veeam Backup & Replication deployment, whether Windows-based or Veeam Software Appliance, must match the storage system's time zone.
- Hitachi
- HPE XP

Migration Procedure

To minimize downtime, this procedure recommends deploying the Veeam Software Appliance (VSA) first so that it is ready to receive the migration. Please closely review all system requirements for the VSA and take your time to ensure it is deployed with system resources appropriate for the environment.

Part 1: Deploy Veeam Software Appliance

Set up a Veeam Software Appliance server running Veeam Backup & Replication 13.0.2.
Install your license on the Veeam Software Appliance and provide the Support ID from this license to the Support team.

Note: The Veeam Backup & Replication Web UI has limited functionality; therefore, we strongly recommend that you install the Windows-based Veeam Backup & Replication Console to access all Veeam Backup & Replication features of the Veeam Software Appliance.

Part 2: Prepare Windows-based Veeam Backup & Replication Server and Export Configuration Backup

Upgrade your Windows-based Veeam Backup & Replication to 13.0.2.
Ensure all managed servers are up to date and that there are no issues with existing installed components.
Stop and disable all scheduled jobs (if any).
Create an encrypted Backup Configuration file.
Stop and Disable the following specific services:
Nested entries represent services that are stopped by association but must still be disabled manually.
Warning: Do not stop all Veeam services, only the ones listed.
PowerShell script available below the list.
- Veeam AHV Service
- Veeam AWS Service
- Veeam Azure Service
- Veeam Backup Server RESTful API Service
  ^{Stopping this service will also stop:}
  - Veeam Web Service.
- Veeam Backup Service
  ^{Stopping this service will also stop:}
  - Veeam Broker Service
  - Veeam CDP Coordinator Service
  - Veeam Cloud Connect Service
  - Veeam Data Analyzer Service
- Veeam GCP Service
- Veeam Kubernetes Service
- Veeam KVM Service
- Veeam PVE Service
- Veeam SC HyperCore Service
- Veeam Orchestrator Agent Service

PowerShell script to stop and disable services:

$services = @("Veeam AHV Service","Veeam AWS Service","Veeam Azure Service","Veeam Web Service","Veeam Backup Server RESTful API Service","Veeam Broker Service","Veeam CDP Coordinator Service","Veeam Cloud Connect Service","Veeam Data Analyzer Service","Veeam Backup Service","Veeam GCP Service","Veeam Kubernetes Service","Veeam KVM Service","Veeam PVE Service","Veeam SC HyperCore Service","Veeam Orchestrator Agent Service")

foreach ($service in $services) {
    $svc = Get-Service -DisplayName $service -ErrorAction SilentlyContinue
    if (-not $svc) { Write-Host "[$service] Not found." -ForegroundColor Yellow; continue }
    if ($svc.Status -ne 'Stopped') {
        Write-Host "[$service] Stopping..." -ForegroundColor Cyan
        Stop-Service -Name $svc.ServiceName -Force -ErrorAction SilentlyContinue
        $svc.WaitForStatus('Stopped', '00:02:00')
    }
    Set-Service -Name $svc.ServiceName -StartupType Disabled
    Write-Host "[$service] Stopped and disabled." -ForegroundColor Green
}
                        
                       

Part 3: Import Configuration Backup

Open the Veeam Host Management Console for the Veeam Software Appliance.
Within the Veeam Host Management Console, click Start configuration restore.
(Review the procedure: Launch Configuration Database Restore Wizard)
1. On the Restore Mode step, select Migrate.
2. On the Configuration Backup step, provide the Encrypted Configuration Backup file created on the Windows-based Veeam Backup & Replication server and enter the Encryption password.
3. On the Source Server step:
  - Source backup server — Specify the hostname of the Windows-based Veeam Backup & Replication server.
  - Service account — Specify a user account added to the local administrators group (on the server being added).
    Note: After migration, the old Veeam Backup & Replication server will be listed in the Backup Infrastructure > Managed Servers list, and the service account password must be set to allow communication with the old server.
4. On the Authorization Key step, enter the authorization key provided by Veeam Support.

Note: During the Configuration Restore, some infrastructure components may fail to update. After the configuration restore is complete you must recheck all managed components and ensure they are updated.

Part 4: Migration Verification

After migration, check the remote hosts (especially the migrated host) and upgrade the components if needed.
Log in to Veeam Software Appliance using the Veeam Backup & Replication Console or the WebUI and check everything configured in Veeam Backup & Replication (e.g., Jobs, Repositories, Proxies, Managed Servers, etc).

Note: After configuration migration, everything that was default on the Windows-based Veeam Backup & Replication server (i.e., Default Backup Repository and Default Backup Proxy) will have the prefix "Migrated" added to their name. This is done to avoid name conflict with the VSA's default repository and proxies. (More details available in the next section.)
Review all of the Post-Migration Considerations in the next section.

Post-Migration Considerations

If Four-Eyes Authorization is enabled before the migration, it will be disabled during the migration and may be re-enabled by the user after the migration is complete.
After the migration, the old Windows-based Veeam Backup Server will be added to the Veeam Software Appliance as a managed server.

Veeam recommends that, as soon as you can, migrate all roles from the old machine that hosted Veeam Backup & Replication to other machines managed by the Veeam Software Appliance, and then remove that machine from the Veeam Software Appliance configuration.
- If the source Windows-based Veeam Backup & Replication server was added as a proxy to itself, those entries will be migrated and appear as disabled proxy entries in the Veeam Software Appliance configuration.
- Any repositories that were associated with paths local to the old backup server will be migrated and continue to be accessible.
  - Those repositories that were local to the old backup server that also served as extents for a Scale-Out Backup repository will automatically be placed in Maintenance mode and must be manually removed from Maintenance mode by the user.
- If the "Default Backup Repository" still existed on the old backup server, after migration, it will be renamed to "Migrated Backup Repository" to avoid a name conflict with the Veeam Software Appliance's own Default Backup Repository.
  - Any pre-migration jobs that targeted the "Default Backup Repository" must have their configurations manually reviewed to confirm they now target the "Migrated Backup Repository."
    
    For example, if a plugin job (Proxmox and others) was using the "Default Backup Repository" prior to the migration, after the migration, you need to edit the job and change the target repository to "Migrated Backup Repository."
The Veeam Software Appliance exclusively uses Kerberos for handling domain credentials. As such, all domain usernames must be formatted in UPN format (user@fqdn). This applies to user accounts specified in Users and Roles and the Credentials Manager.

Note: The Veeam Software Appliance does not support trusted domain authentication.
Files that were used by Veeam Backup & Replication and stored on the old server must be manually copied to the Veeam Software Appliance by the user, and the settings must be updated after migration to use those files from their new location.

Tip: Use the Files view in the Veeam Backup & Replication Console to create a folder on the VSA under [Linux > This server], then use the copy-and-paste functions in the Files view to place the files in that folder.

Impacted items:
- CSV files used by CSV-based Protection Groups.
  Use the following command on the original Veeam Backup & Replication server to identify CSV-based Protection Groups:
```
Get-VBRProtectionGroup -ContainerType CSV
```
- Scripts used by Jobs:
  - Pre-Job and Post-Job Scripts
  - Pre-Freeze and Post-Thaw Scripts
After migrating to Veeam Software Appliance, any SureBackup Jobs or Application Groups that were configured to use the SQL Server Checker Script will fail during the "Running test scripts" step. These fail because the Microsoft SQL Server Checker Script requires a Windows-based Veeam Backup & Replication deployment. To resolve this, modify those SureBackup Jobs and Application Groups to remove the SQL Server test.
If the Veeam Backup & Replication server was added to Veeam Backup Enterprise Manager, and that same Veeam Backup Enterprise Manager server will manage the Veeam Software Appliance after the migration, then the entry for the old Veeam Backup & Replication server should be updated with the new hostname/FQDN/IP using the 'Edit' option (not deleting and adding the VSA as a new server).
If the original Windows-based Veeam Backup & Replication server was:
- Added to Veeam ONE:
  After the migration, the Veeam Software Appliance must be added as a new backup server, and the entry for the old one must be deleted. Historical data in Veeam ONE for the old backup server will be lost.
- Added to Veeam Recovery Orchestrator:
  After migration, the Veeam Software Appliance must be added to Veeam Recovery Orchestrator as a new backup server, and the entry for the old backup server must be removed (some configurations may be lost).
- Added to Veeam Service Provider Console as a hosted deployment:
  After migration, the old backup server must be removed from the Veeam Service Provider Console, and then the new Veeam Software Appliance must be added. Reassign resources (e.g., tags, repositories, and VCD organizations), and then reassign jobs.
If a remote Linux mount server was used before the migration, after the migration, the entry for that Linux server must be edited, and then click Finish to force the credentials to be updated.
If a repository did not have a Linux mount server specified in its settings before the migration, that setting will be updated during the migration to select the machine that is assigned as the default Linux Mount server.
If backups are being sent to a Veeam Cloud Connect Repository, a default Windows mount server must be assigned to restore from them using certain Veeam Explorers (Veeam Explorer for Microsoft SQL Server, Veeam Explorer for Oracle, Veeam Explorer for Microsoft SharePoint, and Veeam Explorer for Microsoft Active Directory).
If inline malware scanning is enabled, the first run of backup jobs after the migration may take longer than expected, as a full disk read operation is performed to create a RIDX file. The job session will run longer than usual, but the size of the incremental backup file will not be affected. This is necessary because the malware indexes from the Windows-based backup server are not migrated.
During migration, jobs that were created by a user with a custom role will have their ownership reassigned to the primary backup admin. The user who created the jobs can still start and modify them, but will no longer be able to delete the jobs or restore points created by those jobs. New jobs created after the migration by those users with custom roles will not be impacted.
After the migration, it may take up to 24 hours for the internal list of unsupported Azure Archive regions to be updated. During this time, avoid creating or modifying Azure Archive repositories, as this may result in errors.
Continuous Data Protection (CDP) for VMware vSphere: Jobs and settings related to this feature will be migrated. However, after migration, you must open the I/O Filter Manager and Take Ownership of the existing filters. This process cannot be completed automatically by the migration, as taking ownership checks for updates of the I/O Filter components, and if an update is needed, the ESXi host must be placed in Maintenance mode to complete the update.

Agent Management Related Post Migration Limitations and Considerations

General (Applies to all Veeam Agents)

After migrating to the Veeam Software Appliance, all Protection Groups must be rescanned to update the Backup Server certificate expected by the Agents.
After migration, all agents managed Protection Groups for Computers with Pre-installed Backup Agents must be reconfigured with a new configuration file from the Veeam Software Appliance.
Managed agents and standalone agents that have backup jobs targeting a VBR repository, and whose operating systems are not compatible with v13 agents, will be unable to connect to the Veeam Software Appliance. This applies even if those agents are not using v13.
Provided below are links to the System Requirements for Veeam Agent for Microsoft Windows and Veeam Agent for Linux 13, as there were changes.
- Veeam Agent for Microsoft Windows 13 System Requirements
- Veeam Agent for Linux 13 System Requirements
  See also: KB4784: Veeam Backup & Replication 13: Changes to Supported Linux Platforms
After the migration is complete, all Veeam Agent Backup Policies whose destination was the Veeam Backup & Replication server must be updated to specify the DNS name or IP address of the new backup server in the policy settings.
On the remote Distribution Server specified in the Protection Group's settings, the Veeam Distribution Service must be restarted to ensure it properly communicates with the Veeam Software Appliance.
Depending on the backup destination repository type (object or block), certain considerations should be taken after migration:
- If a Veeam Agent job was configured to connect to Veeam Backup & Replication using a local account on the Windows-based backup server, and the backup destination is an object storage repository, the backup chain cannot be continued after migration to the Veeam Software Appliance. Backup data on object storage is stored under a path tied to the account used to connect to Veeam Backup & Replication. After migration, this path changes even if a local account with the same name is created on the Veeam Software Appliance, resulting in a new active full backup being created under a new prefix.
  To restore from the previous backup chain, generate a recovery token for the affected backup in the Veeam Backup & Replication Console, then use the token to connect to the backup server during restore (VAW | VAL | VAM).
- If a Veeam Agent job was configured to use a local account on the Windows-based Veeam Backup & Replication server (for example, Administrator) and backs up to a block storage repository, the backup chain can be continued after migration by performing the following steps, as the backup files are stored in a directory named after the account used and will need to be moved to match the new account on the Veeam Software Appliance.
  - For Veeam Agent for Microsoft Windows
    Move the backup files from the old account's directory to the new account's directory (as described above), then edit the job as described in Moving Backups to Veeam Backup & Replication, and run the backup job.
  - For Veeam Agent for Linux and Veeam Agent for Mac
    1. On the repository, move the backup files from the old account's directory (for example, Administrator) to the new account's directory (for example, veeamadmin). This can be done manually or through the Files tab in the Veeam Backup & Replication console.
    2. Rescan the repository on the Veeam Software Appliance.
    3. On the agent machine, edit the job to specify the new backup server and new account credentials.
    4. On the agent machine, run the following CLI command to rescan the repository:
```
veeamconfig repository rescan --all
```
      For more information, see Rescanning Backup Repositories.
    5. Verify that the backup is recognized by running
```
veeamconfig backup list
```
    6. Run the backup job. Automapping will execute, and incremental backup will resume.

Veeam Agent for Microsoft Windows Specific

For Protection Groups for Microsoft Active Directory Objects that use port 636 (encrypted LDAP), open the Protection Group settings and, on the Active Directory tab, click "Change," then press "Ok" to have the software pull the domain Root CA certificate and add it to the trusted certificates.

Note: The default for Protection Group for Microsoft Active Directory Objects is to use port 389, but the option to use port 636 is available if manually entered. As documented in the user guide, "If you want to use port 636, make sure that the domain Root CA certificate is properly published in the domain."

Veeam Agent for Mac Specific

If Veeam Agent for Mac jobs were configured to connect to the Windows-based Veeam Backup & Replication server using domain accounts, those jobs must be reconfigured after migration to use a local user account on the Veeam Software Appliance (e.g., veeamadmin). Domain accounts cannot be used because Veeam Agent for Mac does not support Kerberos authentication, and the Veeam Software Appliance does not support NTLM authentication.
After migration, Veeam Agent for Mac jobs must be edited to specify the new backup server. After saving the updated job settings, close the editing wizard before running the job. Due to a known issue, running a job directly from within the wizard will return a connection error referencing the old backup server, even though the new server details are correctly saved.
- Workaround: Close the job editing wizard and start the job manually.
- Note: As an alternative, update the backup server connection via CLI on the agent machine by running veeamconfig vbrserver edit. This updates the connection for all jobs simultaneously without encountering the wizard issue. For more information, see Editing Veeam Backup Server Settings.

Storage System Related

After migration, if an IBM Flash System has been added as a Storage System, version 2.3.80 or higher of the IBM FlashSystem Plug-In for Veeam Backup & Replication must be installed manually to ensure the Veeam Software Appliance can communicate with it.
Any Storage Snapshot-Only job that was configured to use the "Default Backup Repository" to store database log backup files will still appear to be targeting that repository, even though it was renamed. Such jobs must be updated to target a new repository, or the renamed "Migrated Local Backup Repository."
Since the NAS filer role for NetApp ONTAP storage is the only role supported by Veeam Software Appliance, only storage configured with this role can be migrated.
After migration, if either of the following storage systems has been added as a Storage System, you must ensure that the listed version of that storage's plug-in is installed to ensure that the Veeam Software Appliance can communicate with it.
- Hitachi Plug-In for Veeam Backup & Replication version 2.2.271 or higher.
- HPE XP Plug-In for Veeam Backup & Replication version 2.2.271 or higher.

Standalone Enterprise Database Plug-ins Related

This section applies only to Standalone, non-managed, deployments of Enterprise Database Plug-ins (RMAN, HANA, SQL, DB2, SAP Oracle). After migration, those standalone Enterprise Plug-in deployments must be reconfigured in the following ways:

Endpoint (hostname or IP address): The address of the Veeam Backup & Replication server will change after migration to the Veeam Software Appliance (VSA). You must re-run the configuration wizard for the plug-in and specify the new Veeam Software Appliance address.
Credentials: If a local (non-Active Directory) Windows account was previously used to connect the plug-in to the Windows-based VBR deployment, you must reconfigure the plug-in after migration to specify new credentials (such as "veeamadmin" or another valid account) to connect to the Veeam Software Appliance, as it runs on Linux.
Repository: If the "Default Backup Repository" was used, it will be renamed to "Migrated Backup Repository." Reconfiguration is required to point the plug-in to the new repository name.
- To continue using the backups stored in that repository, reconfigure the affected plug‑in jobs to target the Migrated Backup Repository:
  - Reconfigure the plug-in to use the renamed repository, Migrated Backup Repository, as the new target.
  - Remove from configuration all plug-in backups that are associated with the renamed repository, Migrated Backup Repository.
  - Delete all plug-in jobs that previously targeted the Default Backup Repository.
  - Rescan the Migrated Backup Repository to ensure all migrated backups are recognized.
  - Map all plug-ins to the Migrated Repository.
  - Verify that all jobs can continue using old backups, but note that new jobs will be created (with new job names).
- If you opt to reconfigure the plug-ins to target the new Default Backup Repository of the Veeam Software Appliance, or a different repository, a new set of restore points will be created. However, it is still possible to restore data from the "Migrated Backup Repository," simply by using the “restore to another server” procedure. Details are available in the Restore section of the user guide for the relevant plug-in:

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 Configure Bypass Rules for Veeam Backup for Microsoft 365 Internet Proxy Setting

2026-07-21T00:00:00Z

How to Configure Bypass Rules for Veeam Backup for Microsoft 365 Internet Proxy Setting

KB ID:	4174
Product:	Veeam Backup for Microsoft 365 \| 8 \| 8.1 \| 8.2 \| 8.3 \| 8.4 \| 8.5
Published:	2021-05-26
Last Modified:	2026-07-21

Purpose

This article describes how to configure a bypass list for the Internet Proxy configured within Veeam Backup for Microsoft 365.

Solution

This procedure restarts services on the controller and backup proxies. Ensure that no backup or restore tasks are active before beginning.

How it Works

The Internet Proxy Bypass configuration uses a regular expression (regex) to define which domains Veeam Backup for Microsoft 365 accesses directly, bypassing the Internet Proxy settings.

For example, to exclude all addresses within the .local and veeam.com domains, the value .+\.local;veeam\.com is used.

Known Limitation

The Internet Proxy Bypass feature documented in this article only functions for Windows-based Backup Proxies.

How to Configure

Starting with Veeam Backup for Microsoft 365 v8, the bypass value is configured using the Set-VBOConfigurationParameter cmdlet. Manual editing of the Config.xml and Proxy.xml files is no longer required. The following steps are performed from the Veeam Backup for Microsoft 365 server using the Veeam Backup for Microsoft 365 PowerShell toolkit.

Note: Each backup proxy has its own internet proxy configuration and can either inherit the settings from the management server or use its own dedicated internet proxy, as described in Configuring Internet Proxy Server. These steps assume that a Global Internet Proxy has been configured, and that the backup proxies are set to Use internet proxy settings from the management server or Use the following internet proxy settings. If a backup proxy is configured with Do not use internet proxy, its configuration does not need to be modified.

Configure the Controller

Perform the following on the Veeam Backup for Microsoft 365 server (controller):

Open the Veeam Backup for Microsoft 365 console.
In the main menu ( ☰ ), expand Console and select PowerShell.
^{Note: Launching PowerShell from outside Veeam Backup for Microsoft 365 may require manual loading of PowerShell modules.}
Update the script's variable to set the bypass value, then run it to configure the controller:

# Set the following variable
$bypassHosts = ".+\.local;veeam\.com"

# No changes needed below
Set-VBOConfigurationParameter -XPath "/Veeam/InternetProxy" -Key "BypassHosts" -Value $bypassHosts -Controller

Note: Restart the Veeam Backup for Microsoft 365 Service on the Veeam Backup for Microsoft 365 server for the change to take effect.

Configure the Windows Backup Proxies

Note: Remember that the Veeam Backup for Microsoft 365 server (controller) itself is also a proxy.

Open the Veeam Backup for Microsoft 365 console.
In the main menu ( ☰ ), expand Console and select PowerShell.
^{Note: Launching PowerShell from outside Veeam Backup for Microsoft 365 may require manual loading of PowerShell modules.}
Run the following command to list the proxies and proxypools associated with the deployment. Use the hostnames and poolnames listed to ensure the script in step 4 completes without issue:

Get-VBOProxy | ft hostname,type,poolid
Get-VBOProxyPool | ft name,proxies,id

Update the script's variables to set the bypass value and proxy hostname, then run the script to configure that proxy.

When prompted, enter the Windows credentials for that proxy.

# Set the following variables
$bypassHosts = ".+\.local;veeam\.com"
$proxyHostname = ""

# No changes needed below
$vboproxy = Get-VBOProxy -Hostname $proxyHostname
$winserverCredentials = Get-Credential
Set-VBOConfigurationParameter -XPath "/Veeam/InternetProxy" -Key "BypassHosts" -Value $bypassHosts -Proxy $vboproxy -WindowsCredential $winserverCredentials -Restart
                     
                    

Note: Running the proxy or proxy pool configuration commands may return a deprecation warning for the -WindowsCredential parameter. This warning can be safely ignored; the configuration change still applies.

To configure all proxies in a pool, update and use the following script:

# Set the following variables
$bypassHosts = ".+\.local;veeam\.com"
$poolName = ""

# No changes needed below
$proxyPool = Get-VBOProxyPool -Name $poolName
$winserverCredentials = Get-Credential
Set-VBOConfigurationParameter -XPath "/Veeam/InternetProxy" -Key "BypassHosts" -Value $bypassHosts -ProxyPool $proxyPool -WindowsCredential $winserverCredentials -Restart
                     
                    

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 Export Veeam Backup for Salesforce Data to Cloud Storage

2026-07-16T00:00:00Z

How to Export Veeam Backup for Salesforce Data to Cloud Storage

KB ID:	4882
Product:	Veeam Backup for Salesforce
Published:	2026-07-16
Last Modified:	2026-07-16

Purpose

This article covers vbsf-export, a standalone utility that exports Salesforce backup data from a Veeam Backup for Salesforce deployment to cloud storage. The exported files can then be used, for example, with the Data Import feature of Veeam Data Cloud for Salesforce to migrate the backup history to the cloud.

Overview

With vbsf-export, backup data is exported from the PostgreSQL database managed by Veeam Backup for Salesforce to Azure Blob Storage or Amazon S3. The utility is distributed and installed separately from Veeam Backup for Salesforce, and is compatible with version 3.2.0 or later.

Preparation

The target cloud storage, either an Azure Blob container or an S3 bucket, must be provisioned, and the access credentials must be available.
The Veeam Backup for Salesforce deployment must be version 3.2.0 or later; vbsf-export is not compatible with earlier versions.
Java 17 or later must be available on the host on which the utility will be run.
Network connectivity from the host to both the backup PostgreSQL database and the target cloud storage endpoint must be confirmed (network, DNS, firewall, and proxy configuration as applicable).
Data archival policies must be paused, and a fresh backup must be run to capture the latest state before exporting.
The backup database connection details (JDBC URL, username, and password) and the 18-character Salesforce org ID must be available.

For Veeam Data Cloud for Salesforce Tenants

If Data Import is enabled for the Veeam Data Cloud for Salesforce tenant, a ready-to-run export command can be generated from the Migrate from On-Prem option in the Veeam Data Cloud for Salesforce UI, pre-filled with the org and storage details.

Deployment Information

The vbsf-export utility should be deployed on the host on which the export will be run (typically the Veeam Backup for Salesforce host itself, or another host with database and storage access).

Red Hat, AlmaLinux, Rocky, and Oracle | Version 8

#Download Repo Installation package
sudo curl https://repository.veeam.com/yum/el/8/x86_64/vbsf/vbsf-export-1.0.0-24.el8.x86_64.rpm --output vbsf-export.rpm
#Install Veeam Software Repository
sudo yum install -y ./vbsf-export.rpm
#Install vbsf-export utility from the Veeam software repository
sudo yum install -y vbsf-export
                     
                    

Red Hat, AlmaLinux, Rocky, and Oracle | Version 9

#Download Repo Installation package
sudo curl https://repository.veeam.com/yum/el/9/x86_64/vbsf/vbsf-export-1.0.0-24.el9.x86_64.rpm --output vbsf-export.rpm
#Install Veeam Software Repository
sudo yum install -y ./vbsf-export.rpm
#Install vbsf-export utility from the Veeam software repository
sudo yum install -y vbsf-export
                     
                    

Ubuntu

#Download Repo Installation package
sudo curl https://repository.veeam.com/apt/stable/amd64/vbsf-export_1.0.0-24_amd64.deb --output ./vbsf-export.deb
#Install Veeam Software Repository
sudo apt install -y ./vbsf-export.deb
#Install vbsf-export utility from the Veeam software repository
sudo apt-get -y update
sudo apt install -y vbsf-export
                     
                    

Verify Connectivity Before Exporting

Before an export is run, access from the host to both the backup database and the target cloud storage must be confirmed.

Export Execution

All parameters can be passed as CLI flags (--property=value) or as uppercase environment variables.
When the utility is run with no arguments, -h, or --help, the full parameter reference is printed.
For validation, --test_run=true can be added to check connectivity and show which tables match the configured filters, without exporting any data.
By default, only start and finish status is shown in the console; details are written to the log files specified in the log_output parameter (vbsf-export.log and debug/vbsf-export.log). To stream full progress to the console instead, --follow (-f) can be added.
Salesforce object names are mapped to lowercase table names in the backup database. To also include Account's history, --export_table_filter='^account(__h)?$' can be used.

Example

In the following example, only the Account object's data, changed on or after June 1, 2025, is exported to Azure Blob Storage:

java -jar vbsf-export.jar \
  --jdbc_url=jdbc:postgresql://localhost:5432/vbsf_application \
  --jdbc_username=vbsf --jdbc_password=*** \
  --sf_org_id=00D2C000700gi2SUAQ \
  --azure_account_name=mystorageaccount --azure_access_key=*** \
  --azure_container_name=vbsf-export \
  --log_output=/var/log/vbsf/vbsf-export \
  --export_table_filter='^account$' \
  --filter="vsf_last_modified_date >= '2025-06-01 00:00:00+00'"

Supported Features

Salesforce object record data (current state and history restore points) is exported from the backup PostgreSQL database to Azure Blob Storage or Amazon S3.
Everything can be exported, or the run can be limited to specific Salesforce objects by matching table names with a regular expression (by default, every table is exported).
Only a date range can be exported instead of the full history: a SQL condition (for example, "modified on or after a given date") can be applied to all exported tables, or overridden for a specific table.
Output can be produced as plain CSV, GZIP, ZIP, or password-protected ZIP, with optional file splitting by row count or size.
A test-run mode is available to validate the configuration before real data is exported.

Limitations and Considerations

Only Salesforce object record data is exported; Files, Attachments, and metadata are not supported.
Data is not decrypted, so encrypted fields are excluded by default. If the decrypted data is required (for example, to perform Data Import into Veeam Data Cloud for Salesforce), the fields must be decrypted beforehand.
Data is streamed directly to cloud storage, so a stable connection from the export host to the storage endpoint is required for the entire run.
If a column referenced by a row filter does not exist for a table (or causes a type mismatch), that table is skipped with a warning in the log, and the remainder of the export continues.

Next steps

Instructions for preparing and loading the exported files once they are in cloud storage are provided in KB4878.

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 Fsas ETERNUS EP300 Plug-In for Veeam Backup & Replication

2026-07-16T00:00:00Z

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

KB ID:	4881
Product:	Veeam Backup & Replication \| 13
Published:	2026-07-16
Last Modified:	2026-07-16

This plug-in leverages the Veeam Universal Storage API, which enables storage OEMs to allow Veeam Backup & Replication integration to the arrays for backup and replication jobs.

Requirements

Before installing Fsas ETERNUS EP300 Plug-In v2.2.309, make sure that you are running Veeam Backup & Replication build 13.0.1.180 or higher. You can check the build number in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.

Fsas ETERNUS EP300 Plug-In v2.2.309 supports integration with the following storage systems:

Fsas ETERNUS EP300 (A3-03-01-x0/01 or later)

ETERNUS EP300 is an OEM product of Hitachi VSP One Block B20 series, and its features and operation are identical to those of VSP One Block B20 series. Please refer to Hitachi documentation for user guides and other materials.

Known Issues

The following is a list of known major issues for Fsas ETERNUS EP300 Plug-In for Veeam Backup & Replication. If you experience any issue listed below, please contact Fsas support directly.

Thin Image Advanced feature is only supported for volumes with the DRS attribute. The attribute must be inherited by snapshots.
When backing up a Global Active Device (GAD) volume, note that the copy group name to which the volume belongs must be prefixed with "VBR_" otherwise, backup jobs will fail. This requirement applies even if only one volume from a GAD replication relationship is added to a Veeam Backup & Replication instance.
When adding ETERNUS EP300 storage to the Veeam Backup & Replication infrastructure, use the Service IP address.
DNS names (hostnames/FQDNs) cannot be used to add the storage; only IP addresses are allowed. Additionally, IPv6 can only be used if the IPv4 management address is not configured on the storage.
Fsas ETERNUS EP300 Plug-In does not return information about volumes that are not mounted to a host. To restore from snapshots residing on such volumes, mount a volume to a host and perform a rescan in the Veeam Backup & Replication console. For details, see Rescanning Storage Systems.
This plug-in version does not support Freeze-only snapshots (application-aware processing performed without creating a VMware snapshot, see Configuring Snapshot-Only Jobs). In some cases, this processing mode can exceed the Windows VSS timeout, which may result in inconsistent backups. To switch to VM processing using VMware snapshots instead of Freeze-only processing, contact Veeam support to change the value of a dedicated registry key.
After deleting a snapshot, logical device (LDEV) records with the _DEL suffix may remain on storage until the subsequent automatic maintenance. However, such snapshots can occasionally be exported and displayed in the storage infrastructure UI as regular volumes if the storage rescan fails to purge them - in this case, they can be unexported or deleted manually.
The same applies to clones that are purged during rescan only if synchronization between the source snapshot and its clone is not underway.
Retention-based snapshot removal may fail if synchronization between the snapshot and its clone has not been completed or is still running.
If jobs and rescan operations are running in parallel or at the moment when the storage system is processing other tasks, the operations may fail.
Ensure at least two FC ports are available on the storage; configurations with a single FC port are not supported.
Fsas ETERNUS EP300 Plug-In does not support backing up failover clusters using Veeam Agent for Microsoft Windows.
Information about the snapshot immutability period is not collected during storage rescan. As a result, snapshots created outside of Veeam Backup & Replication, or those collected after removing and re-adding the storage in Veeam Backup & Replication, do not display the 'Immutable Until' date in the UI. Additionally, such snapshots cannot be deleted manually because they are actually immutable.
The Immutability feature is only available for volumes that have the DRS attribute. If jobs reference volumes without the DRS attribute but have immutability enabled, they will display the snapshot immutability expiration time, which matches the snapshot creation time.

Download Information

For Veeam Backup & Replication on Windows

Download Plug-In

^{Release date: 2026-07-14}

SHA256: 076EC924E17623194295A357EED4B7C075ED52C7AB9C1698ECE0B23A4238CD26

For Veeam Backup & Replication on Veeam Software Appliance

Installing and Updating Plug-Ins on Linux-Based Backup Server

Download Plug-In for VSA

^{Release date: 2026-07-14}

SHA256: 3503E928E7CB841BBB01144B5C3059A9DB1221F4F78B7D66D8DE059C9E0C2167

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 Install and Configure PgBouncer for Veeam Backup for Microsoft 365

2026-07-16T00:00:00Z

How to Install and Configure PgBouncer for Veeam Backup for Microsoft 365

KB ID:	4728
Product:	Veeam Backup for Microsoft 365 \| 8.1 \| 8.2 \| 8.3 \| 8.4 \| 8.5
Published:	2025-07-18
Last Modified:	2026-07-16

PgBouncer must not be deployed on the machine where Veeam Backup for Microsoft 365 is installed.

This article is intended only for deployments where the PostgreSQL Instance used by Veeam Backup for Microsoft 365 is hosted on its own dedicated server.

For deployments of Veeam Backup for Microsoft 365 where the PostgreSQL instance is installed on the same machine as Veeam Backup for Microsoft 365, PgBouncer must not be deployed.

Review KB4758: PostgreSQL and PgBouncer Sizing and Configuration Guide for advice on whether the PostgreSQL instance should be deployed on its own dedicated server based on the Veeam Backup for Microsoft 365 deployment size. If the guidance in that article indicates that PostgreSQL should be hosted on a dedicated server, consider migration (review: KB4676: How to Migrate the Configuration and Repository Cache Databases).

Purpose

This article provides step-by-step instructions for installing and configuring PgBouncer for use with Veeam Backup for Microsoft 365. PgBouncer is a lightweight connection pooler for PostgreSQL, and this guide is intended to help users integrate it with Veeam Backup for Microsoft 365 environments to improve database connection efficiency and performance.

Cause

Why should you deploy PgBouncer?

Each proxy and repository must connect to the PostgreSQL database when using Veeam Backup for Microsoft 365. This can quickly create thousands of separate database connections in larger environments, overloading the PostgreSQL server’s resources and network, causing performance issues.

PgBouncer helps by pooling those connections. Instead of every proxy making its own connection, PgBouncer groups them and reuses connections efficiently. This dramatically reduces the total number of database connections and lowers the strain on the PostgreSQL server, making the system more stable and reliable.

Solution

Follow the steps below to install PgBouncer, configure it for use with PostgreSQL, and integrate it with Veeam Backup for Microsoft 365.

Depending on the number of proxies or repositories, you may require more precise configuration tunings for PostgreSQL and PgBouncer parameters.

KB4758: PostgreSQL and PgBouncer Sizing and Configuration Guide

Part 1: Prepare PostgreSQL Configuration

Using pgAdmin, or the PostgreSQL DB management tool of your choosing, create a dedicated user within the PostgreSQL instance for PgBouncer to use.

CREATE USER pgbouncer WITH LOGIN;
-- Update pgbouncerpass with the actual password you want to assign to the pgbouncer account.
ALTER USER pgbouncer WITH PASSWORD 'pgbouncerpass';
                     
                    

Using the Query Tool, and making sure the 'postgres' db is targeted, create a user lookup function to allow PgBouncer to authenticate users via PostgreSQL:

CREATE OR REPLACE FUNCTION user_search(uname TEXT) 
RETURNS TABLE (usename name, passwd text) AS 
$$ 
  SELECT usename, passwd FROM pg_shadow WHERE usename = $1; 
$$ 
LANGUAGE sql SECURITY DEFINER; 
                     
                    

Open the pg_hba.confFound in: C:\Program Files\PostgreSQL\16\data\ file and verify that it contains rules to accept local connections.

# TYPE   DATABASE        USER           ADDRESS                METHOD
local    all             all                                   scram-sha-256
host     all             all            127.0.0.1/32           scram-sha-256
host     all             all            ::1/128                scram-sha-256

If any changes were made to the pg_hba.conf file, then restart the PostgreSQL service.

Part 2: Install and Configure PgBouncer

Since PgBouncer must be installed on the same machine as the existing PostgreSQL instance, the instructions depend on the OS of the machine where PostgreSQL is installed.

Expand the appropriate section.

PgBouncer on Windows Instructions

List of Security Fixes and Improvements in Veeam Kasten for Kubernetes

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

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

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

**Veeam Kasten for Kubernetes 8.5.13**

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

**Veeam Kasten for Kubernetes 8.5.12**

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

**Veeam Kasten for Kubernetes 8.5.10**

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

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

**Veeam Kasten for Kubernetes 8.5.5**

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 Configure HTTP Proxy for Windows-based Veeam Components

2026-07-14T00:00:00Z

How to Configure HTTP Proxy for Windows-based Veeam Components

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

Purpose

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

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

Connecting to a Veeam Cloud Connect Provider

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

Solution

Summary

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

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

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

HTTP Proxy Authentication Is Not Supported

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

Configure WinHTTP Proxy

Veeam Software Appliance/Veeam Infrastructure Appliance — Updater Component Vulnerability

2026-07-14T00:00:00Z

Veeam Software Appliance/Veeam Infrastructure Appliance — Updater Component Vulnerability

KB ID:	4879
Product:	Veeam Backup & Replication \| 13
Published:	2026-07-14
Last Modified:	2026-07-14

Veeam Software Security Commitment

Veeam® is committed to ensuring its products protect customers from potential risks. As part of that commitment, we operate a Vulnerability Disclosure Program (VDP) for all Veeam products and perform extensive internal code audits. When a vulnerability is identified, our team promptly develops a patch to address and mitigate the risk. In line with our dedication to transparency, we publicly disclose the vulnerability and provide detailed mitigation information. This approach ensures that all potentially affected customers can quickly implement the necessary measures to safeguard their systems. It’s important to note that once a vulnerability and its associated patch are disclosed, attackers will likely attempt to reverse-engineer the patch to exploit unpatched deployments of Veeam software. This reality underscores the critical importance of ensuring that all customers use the latest versions of our software and install all updates and patches without delay.

Vulnerability Details

A vulnerability in the Veeam Updater component allows a local user to elevate their privileges and gain root-level access to the underlying operating system.

Severity: High
CVSS Score: 8.4CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Source: Reported through HackerOne by skydesperados.

Impacted Components:

Veeam Software Appliance (Linux-based Veeam Backup & Replication Server)
Veeam Infrastructure Appliance

This vulnerability does not affect Windows-based Veeam Backup & Replication backup servers, but may affect remote components that utilize the Veeam Infrastructure Appliance.

Solution

This vulnerability is resolved starting in the Veeam Updater component version 12.3.0.65.

Automatic Update Deployment — For most users, no action is needed, as the Veeam Updater component installs the fix automatically during its automatic update check.
Manual Update Deployment — If the Veeam Software Appliance or any Veeam Infrastructure Appliance is unable to reach either repository.veeam.com or a local mirror repository, the fix must be applied manually with assistance from Veeam Support, or temporary internet access to the update server must be configured.

For more information about Veeam Appliance Update configuration, review the product user guide:
Veeam Backup & Replication User Guide: Updating Veeam Appliances

Deployment Verification

To verify that the Veeam Updater component has been updated, review the component versions on the Veeam Software Appliance or Veeam Infrastructure Appliance using its Host Management Console:

Open the appliance's Host Management Console Web UI.
In the left-side navigation list, select the Logs and Services section under the Support heading.
Within the Logs and Services view, select the Components tab.
Review the list of installed components and their respective versions (optionally use the filter).
Verify that the Veeam Updater component version listed is 12.3.0.65 or higher.

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 Management Pack for Microsoft System Center / Veeam Backup & Replication 13 Compatibility

2026-07-14T00:00:00Z

Veeam Management Pack for Microsoft System Center / Veeam Backup & Replication 13 Compatibility

KB ID:	4876
Product:	Veeam Backup & Replication \| 13 Veeam Management Pack \| 9a
Published:	2026-07-14
Last Modified:	2026-07-14

Challenge

After Veeam Backup & Replication is upgraded to version 13, it is no longer monitored by Veeam Management Pack for Microsoft System Center 9.1. Backup infrastructure data is no longer collected from the upgraded Veeam Backup Server, backup jobs that were previously visible are no longer detected, and the associated Veeam reports stop working.

Solution

The patch available from this article adds support for monitoring Veeam Backup & Replication 13. The patch installs an updated Backup Data Collector on the Veeam Backup Server, along with updated Backup management packs.

Requirements

Software Requirements

Operating System
- Microsoft Windows Server 2025
- Microsoft Windows Server 2022
- Microsoft Windows Server 2019
Veeam Backup & Replication version 13

Permissions Requirements

The account used for the Veeam MP Backup Data Collector service must meet the following requirements:

The account must be a local administrator on the Veeam Backup Server where Veeam Backup & Replication is installed.
The account must be assigned the Backup Administrator role in Veeam Backup & Replication.

Deployment Information

Download the patch archive.
Unpack the archive.
On the Veeam Backup Server, run VeeamMP.BackupDataCollector.x64.msi from an elevated Command Prompt (Run as administrator). At the Service Credentials step, specify a service account that meets the requirements above.
From the Backup MP folder within the patch archive, import the five included management pack files via the SCOM Management Server.

Download Information

Download Patch

^{Filename: KB4876-VMP9.1-VBR13-Patch.zip}

SHA256: 21400950C86B5B0E0A920515C5D8C170A834872877C0B23FDCCD7ECDA3F67222

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 Operations Fail When the Backup Server Has Limited Internet Access

2026-07-14T00:00:00Z

Veeam Operations Fail When the Backup Server Has Limited Internet Access

KB ID:	4819
Product:	Veeam Backup & Replication \| 13
Published:	2026-02-24
Last Modified:	2026-07-14

Article Applicability

This article addresses an issue that may occur when using a Windows-based deployment of Veeam Backup & Replication v13, where the Veeam Backup Server or other Windows-based component servers are isolated from the internet or subject to significant firewall restrictions.

Challenge

When attempting to perform actions in Veeam Backup & Replication that initiate secure connections, those tasks may fail in environments where the Veeam Backup Server or other Windows-based component servers are either isolated from the internet or subject to significant firewall restrictions to outside servers.

Operations that may be affected include, but are not limited to:

Windows Guest File Level Restore (FLR)
Example: Task fails with "The request has been canceled"
Malware Scan Backup Session (which relies on Windows FLR)
Veeam Data Cloud Vault connections
Example: Interaction fails with "Rename folder failed"
Adding Hyper-V hosts
Connecting the Veeam Backup & Replication Console

Log Example - FLR Restore Failure

Release Information for Hitachi Plug-In for Veeam Backup & Replication

2026-07-14T00:00:00Z

Release Information for Hitachi Plug-In for Veeam Backup & Replication

KB ID:	4191
Product:	Veeam Backup & Replication \| 12 \| 12.1 \| 12.2 \| 12.3 \| 12.3.1 \| 12.3.2 \| 13
Published:	2021-07-21
Last Modified:	2026-07-15

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 Hitachi Plug-In v2.2.309, make sure that you are running Veeam Backup & Replication build 13.0.1.180 or higher. You can check the build number in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.

Hitachi Plug-In v2.2.309 supports integration with the following storage systems:

VSP E series (93-03-01-60/00 or later)
VSP F series (88-07-01-x0/00 or later)
VSP G series (88-07-01-x0/00 or later)
VSP 5100 and VSP 5500 (90-05-01-00/00 or later)
VSP 5200 and VSP 5600 (90-08-01-00/00 or later)
VSP One Block series (A3-03-01-x0/01 or later | A0-05-21-00/xx or later for the VSP One Block 85 model)

Follow detailed instructions on configuring the Hitachi Plug-in and the storage system in the Hitachi Documentation.

What's New

Added support for:

Added support for the VSP One Block 21 and VSP One Block 24 models

Known Issues

The following is a list of known major issues for Hitachi Plug-In for Veeam Backup & Replication. If you experience any issue listed below, please contact Hitachi support directly.

Thin Image Advanced feature is only supported for volumes with the DRS attribute. The attribute must be inherited by snapshots.
When backing up a Global Active Device (GAD) volume, note that the copy group name to which the volume belongs must be prefixed with "VBR_" otherwise, backup jobs will fail. This requirement applies even if only one volume from a GAD replication relationship is added to a Veeam Backup & Replication instance.
When adding Hitachi storage to the Veeam Backup & Replication infrastructure, the following addresses should be used:
- For the VSP One Block series, use the Service IP address.
- For the VSP 5000 series, use the Service Processor (SVP) IP.
- For all other storage models, use one of the CTL1/CTL2 IP addresses.
DNS names (hostnames/FQDNs) cannot be used to add the storage; only IP addresses are allowed. Additionally, IPv6 can only be used if the IPv4 management address is not configured on the storage.
Hitachi Plug-In does not return information about volumes that are not mounted to a host. To restore from snapshots residing on such volumes, mount a volume to a host and perform a rescan in the Veeam Backup & Replication console. For details, see Rescanning Storage Systems.
This plug-in version does not support Freeze-only snapshots (application-aware processing performed without creating a VMware snapshot — see Configuring Snapshot-Only Jobs). In some cases, this processing mode can exceed the Windows VSS timeout, which may result in inconsistent backups. To switch to VM processing using VMware snapshots instead of Freeze-only processing, contact Veeam support to change the value of a dedicated registry key.
After deleting a snapshot, logical device (LDEV) records with the _DEL suffix may remain on storage until the subsequent automatic maintenance. However, such snapshots can occasionally be exported and displayed in the storage infrastructure UI as regular volumes if the storage rescan fails to purge them - in this case, they can be unexported or deleted manually.
The same applies to clones that are purged during rescan only if synchronization between the source snapshot and its clone is not underway.
Retention-based snapshot removal may fail if synchronization between the snapshot and its clone has not been completed or is still running.
If jobs and rescan operations are running in parallel or at the moment when the storage system is processing other tasks, the operations may fail.
Ensure at least two FC ports are available on the storage; configurations with a single FC port are not supported.
Hitachi Plug-In does not support backing up failover clusters using Veeam Agent for Microsoft Windows.
Information about the snapshot immutability period is not collected during storage rescan. As a result, snapshots created outside of Veeam Backup & Replication, or those collected after removing and re-adding the storage in Veeam Backup & Replication, do not display the 'Immutable Until' date in the UI. Additionally, such snapshots cannot be deleted manually because they are actually immutable.
The Immutability feature is only available for volumes that have the DRS attribute. If jobs reference volumes without the DRS attribute but have immutability enabled, they will display the snapshot immutability expiration time, which matches the snapshot creation time.

Download Information

For Veeam Backup & Replication on Windows

Download Hitachi Plug-In

^{Release date: 2026-07-14}

SHA256: 076EC924E17623194295A357EED4B7C075ED52C7AB9C1698ECE0B23A4238CD26

For Veeam Backup & Replication on Veeam Software Appliance

Installing and Updating Plug-Ins on Linux-Based Backup Server

Download Plug-In for VSA

^{Release date: 2026-07-14}

SHA256: 3503E928E7CB841BBB01144B5C3059A9DB1221F4F78B7D66D8DE059C9E0C2167

Previous Versions

**Hitachi Plug-In for Veeam Backup & Replication [2.2.271] - 2025-12-23**

Added support for:

Veeam Backup & Replication v13.0.1
Immutable snapshots
New VSP One Block High End storage platform
Registering multiple WWNs of a single proxy server in one host group

**Hitachi Plug-In for Veeam Backup & Replication [2.1.225] - 2025-03-17**

Requirements

Hitachi Plug-In v2.1.225 supports all version 12.x builds Veeam Backup & Replication build 12.0.0.1420 P20230718 or higher (version 13+ not supported by this plug-in version). You can check the build number in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.

Hitachi Plug-In v2.1.225 supports integration with the following storage systems:

VSP E series (93-03-01-60/00 or later)
VSP F series (88-07-01-x0/00 or later)
VSP G series (88-07-01-x0/00 or later)
VSP 5100 and VSP 5500 (90-05-01-00/00 or later)
VSP 5200 and VSP 5600 (90-08-01-00/00 or later)
VSP One Block series (A3-03-01-x0/01 or later)

Follow the detailed instructions on configuring the Hitachi Plug-in and the storage system in the Hitachi Documentation.

What's New

This update resolves the most commonly reported support issues.
Support for TIA (Thin Image Advanced) snapshots.
Support for VSP One Block storage model line.

Preparation

If you are upgrading the Hitachi Plug-In or if a previous version of the Hitachi Plug-In was used with the Veeam Backup & Replication (VBR) deployment at any time in the past, a private fix may be required depending on the version of VBR that is currently installed.

12.0.0.1420 P20230718 — Install Private Fix TF630101.
12.1.0.2131 — Upgrade to 12.1.1.56, then install Private Fix TF630102.
12.1.1.56 — Install Private Fix TF630102.
12.1.2.172+ — No private fix required.

Note: These private fixes have been included with Veeam Backup & Replication build 12.1.2.172. You may upgrade to that version rather than install the listed private fix.

Failure to install the private fix associated with the installed version of Veeam Backup & Replication (VBR) before operating the newer version of the Hitachi Plug-In may result in the loss of multi-home and retention information created by the older version of the Hitachi Plug-In. Additionally, disks located on datastores other than the one housing the VMX file may fail to restore.

If you are unsure whether a previous version of the plug-in was ever used with your VBR deployment, please install the appropriate private fix to prevent any potential complications.

Deployment

Ensure Veeam Backup & Replication has a valid license.
Download and run the plug-in setup program on the Veeam Backup Server.

Download Hitachi Plug-In 2.1.225

^{Release date: 2025-03-17}

MD5: 9D98091EDE24E0BA56DA8DE6229CFE8E
SHA1: B6D4E775FA9E578BE7D288A80E8E12520ECF69D6

**Hitachi Plug-In for Veeam Backup & Replication [2.0.114] - 2024-05-14**

This update resolves the most commonly reported support issues.
Support for the new version of Universal Storage API v2 that enables Synchronous replication support, allowing backup jobs to create coordinated storage snapshots and track them as additional available restore points and perform backup from volumes on both sides on dual Hitachi TrueCopy and Global Active Device configurations that serve the same production volume from multiple storage management backends.

**Hitachi Plug-In for Veeam Backup & Replication [1.2.99] - 2023-06-08**

Support for HDT (Hitachi Dynamic Tiering) volumes.

**Hitachi Plug-In for Veeam Backup & Replication [1.2.94] - 2023-04-03**

Support for Dedupe and Compression volumes.
Support for Sync/Async replication (P-vol volumes).
Support for IPv6.
This update also resolves the most common support issues.

**Hitachi Plug-In for Veeam Backup & Replication [1.1.82] - 2022-06-23**

Support for GAD volume replication.
Support for new storage models.

**Hitachi Plug-In for Veeam Backup & Replication [1.0.66] - 2021-07-16**

Initial plug-in version

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

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

License Update Fails In Networks Where HTTP Proxy Must Be Used

2026-07-14T00:00:00Z

License Update Fails In Networks Where HTTP Proxy Must Be Used

KB ID:	1975
Product:	Veeam Backup & Replication Veeam ONE Veeam Service Provider Console Veeam Agent for Microsoft Windows Veeam Cloud Connect
Published:	2014-12-10
Last Modified:	2026-07-14

Challenge

License updating may fail if the machine where the Veeam software is installed does not have a direct connection to the Internet and must instead connect to the Internet via an HTTP proxy.

For example, when this occurs with Veeam Backup & Replication, the Svc.VeeamBackup.log shows either of the following errors:

Connection error: The remote name could not be resolved: 'autolk.veeam.com' (System.Exception)

Invalid answer received from https://vbr.butler.veeam.com: possible proxy server configuration issues

Cause

Veeam services use the proxy settings configured within Internet Options for the service account.

Solution

To resolve this issue, configure proxy settings within Internet Options (WinINET) for the service account as documented in KB4875.

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.

"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-16

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) created using the vbsf-export tool.

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 - using the vbsf-export tool
- 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-22

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.37.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.26.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.146.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.37.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.3.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.26.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.3.1.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.4.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.146.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.4.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.3.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.73	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
15 SP6	6.4.0-150600.23.125	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
15 SP5	5.14.21-150500.55.177	13.0.2.2	Veeam Backup & Replication 13.0.2.29 Uses the blksnap* kernel module.*
15 SP4	5.14.21-150400.24.228	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.320	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.96-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.37.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.26.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.146.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.156.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.37.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.3.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.26.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.3.1.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.4.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.146.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.4.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.3.el8uek	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
7.0-7.9 (RHCK)	3.10.0-1160.156.1.el7	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
7.7-7.9 (UEK6)	5.4.17-2136.338.4.2.el7uek	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
7.5-7.9 (UEK5)	4.14.35-2047.542.2.el7uek	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
7.1-7.9 (UEK4)	4.1.12-124.93.1.el7uek	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
6.4-6.10 (RHCK)	2.6.32-754.35.1.el6	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap kernel module.
6.8-6.10 (UEK4)	4.1.12-124.16.4	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
16	6.12.0-160000.35	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
15 SP7	6.4.0-150700.53.73	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
15 SP6	6.4.0-150600.23.125	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
15 SP5	5.14.21-150500.55.177	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the blksnap* kernel module.*
15 SP4	5.14.21-150400.24.228	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.320	6.3.2.1405	Veeam Backup & Replication 12.3.2.4854 Uses the veeamsnap* kernel module.*
openSUSE
Leap 16.0	6.12.0-160000.36	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.96-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.

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-07-17

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 defined in one step and used in later steps.

Step 1: Run an Integrity Check

Open Veeam Backup for Microsoft 365.
In the main menu ( ☰ ), expand Console, and select PowerShell.
^{Note: Launching PowerShell from outside Veeam Backup for Microsoft 365 may require manual loading of PowerShell modules.}
In the PowerShell console, run the following command to import the module used by this article:
^{This DLL module must be loaded directly to ensure the Start-VBORepositoryRepairSession cmdlet is available.}

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

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.

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.

Veeam Support Knowledge Base

Veeam Backup & Replication Platform Migration Guide (Windows to Linux)

Veeam Backup & Replication Platform Migration Guide(Windows to Linux)

Purpose

Before You Begin

Preparation Steps

Solution

Limitations due to Veeam Software Appliance Capabilities

Pre-Migration Considerations

Agent Management Related

Storage Management Related

Migration Procedure

Part 1: Deploy Veeam Software Appliance

Part 2: Prepare Windows-based Veeam Backup & Replication Server and Export Configuration Backup

Part 3: Import Configuration Backup

Part 4: Migration Verification

Post-Migration Considerations

Agent Management Related Post Migration Limitations and Considerations

Storage System Related

Standalone Enterprise Database Plug-ins Related

How to Configure Bypass Rules for Veeam Backup for Microsoft 365 Internet Proxy Setting

How to Configure Bypass Rules for Veeam Backup for Microsoft 365 Internet Proxy Setting

Purpose

Solution

How it Works

How to Configure

Configure the Controller

Configure the Windows Backup Proxies

How to Export Veeam Backup for Salesforce Data to Cloud Storage

How to Export Veeam Backup for Salesforce Data to Cloud Storage

Purpose

Overview

Preparation

Deployment Information

Red Hat, AlmaLinux, Rocky, and Oracle | Version 8

Red Hat, AlmaLinux, Rocky, and Oracle | Version 9

Ubuntu

Export Execution

Example

Supported Features

Limitations and Considerations

Next steps

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

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

Requirements

Known Issues

Download Information

For Veeam Backup & Replication on Windows

For Veeam Backup & Replication on Veeam Software Appliance

How to Install and Configure PgBouncer for Veeam Backup for Microsoft 365

How to Install and Configure PgBouncer for Veeam Backup for Microsoft 365

Purpose

Cause

Why should you deploy PgBouncer?

Solution

Part 1: Prepare PostgreSQL Configuration

Part 2: Install and Configure PgBouncer

List of Security Fixes and Improvements in Veeam Kasten for Kubernetes

List of Security Fixes and Improvements in Veeam Kasten for Kubernetes

Purpose

Security Fixes and Improvements

Veeam Kasten for Kubernetes 9.0.1

Veeam Kasten for Kubernetes 8.5.13

Veeam Kasten for Kubernetes 8.5.12

Veeam Kasten for Kubernetes 8.5.10

Veeam Kasten for Kubernetes 8.5.5

Veeam Kasten for Kubernetes 8.5.3

Veeam Kasten for Kubernetes 8.5.2

Veeam Kasten for Kubernetes 8.5.1

Veeam Kasten for Kubernetes 8.0.15

Veeam Kasten for Kubernetes 8.0.14

Veeam Kasten for Kubernetes 8.0.13

Veeam Kasten for Kubernetes 8.0.11

Veeam Kasten for Kubernetes 8.0.10

Veeam Kasten for Kubernetes 8.0.8

Veeam Kasten for Kubernetes 8.0.7

Veeam Kasten for Kubernetes 8.0.6

Veeam Kasten for Kubernetes 8.0.5

Veeam Kasten for Kubernetes 8.0.4

Veeam Kasten for Kubernetes 8.0.3

Veeam Backup & Replication Platform Migration Guide
(Windows to Linux)

**Veeam Kasten for Kubernetes 9.0.1**

**Veeam Kasten for Kubernetes 8.5.13**

**Veeam Kasten for Kubernetes 8.5.12**

**Veeam Kasten for Kubernetes 8.5.10**

**Veeam Kasten for Kubernetes 8.5.5**

**Veeam Kasten for Kubernetes 8.5.3**

**Veeam Kasten for Kubernetes 8.5.2**

**Veeam Kasten for Kubernetes 8.5.1**

**Veeam Kasten for Kubernetes 8.0.15**

**Veeam Kasten for Kubernetes 8.0.14**

**Veeam Kasten for Kubernetes 8.0.13**

**Veeam Kasten for Kubernetes 8.0.11**

**Veeam Kasten for Kubernetes 8.0.10**

**Veeam Kasten for Kubernetes 8.0.8**

**Veeam Kasten for Kubernetes 8.0.7**

**Veeam Kasten for Kubernetes 8.0.6**

**Veeam Kasten for Kubernetes 8.0.5**

**Veeam Kasten for Kubernetes 8.0.4**

**Veeam Kasten for Kubernetes 8.0.3**

**Veeam Kasten for Kubernetes 8.0.2**

**Veeam Kasten for Kubernetes 8.0.1**

**Veeam Kasten for Kubernetes 8.0.0**

**Veeam Kasten for Kubernetes 7.5.9**

**Veeam Kasten for Kubernetes 7.5.8**

**Veeam Kasten for Kubernetes 7.5.5**

**Veeam Kasten for Kubernetes 7.5.4**

**Veeam Kasten for Kubernetes 7.5.3**

**Veeam Kasten for Kubernetes 7.5.2**

**Veeam Kasten for Kubernetes 7.5.1**

**Veeam Kasten for Kubernetes 7.5.0**

**Veeam Kasten for Kubernetes 7.0.14**

**Veeam Kasten for Kubernetes 7.0.13**

**Veeam Kasten for Kubernetes 7.0.10**

**Veeam Kasten for Kubernetes 7.0.9**

**Veeam Kasten for Kubernetes 7.0.8**

**Veeam Kasten for Kubernetes 7.0.6**

**Veeam Kasten for Kubernetes 7.0.5**

**Veeam Kasten for Kubernetes 7.0.4**

**Veeam Kasten for Kubernetes 7.0.2**

**Veeam Kasten for Kubernetes 7.0.1**

**Veeam Kasten for Kubernetes 7.0.0**