How to Manually Configure Nginx For Use by Veeam Backup for Salesforce

February 11, 2025, 4:00 pm

≫ Next: Veeam ONE Report Error "Invalid query string"

≪ Previous: How to upgrade Veeam Backup for Salesforce to version 2.1.1.

$

0

0

How to Manually Configure Nginx For Use by Veeam Backup for Salesforce

KB ID:	4371
Product:	Veeam Backup for Salesforce | 3.1
Published:	2022-10-27
Last Modified:	2025-02-12

Purpose

This article documents how to manually configure Nginx for use with Veeam Backup for Salesforce 3.1 and higher.

Solution

1. Before making configuration changes, stop the Veeam Backup for Salesforce backend service:

systemctl stop vbsf-backend.service

Copy

2. Use Nginx template configuration files from the following folder on the Veeam Backup for Salesforce server and apply the required changes you want:
   

/opt/vbsf/nginx/etc

Copy

3. Restart the Nginx service to apply the configured changes:
   

systemctl restart nginx.service

Copy

4. Start the Veeam Backup for Salesforce backend service:
   

systemctl start vbsf-backend.service

Copy

5. Get the access token using this command:

sudo cat /opt/vbsf/vbsf-backend/config/init.properties | grep firstuser.token

Copy

6. In a browser, open the Veeam Backup for Salesforce URL with the access token from above.
   
   Example:

https://<vbsf_server_address>/?access_token=<access token>

Copy

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 ONE Report Error "Invalid query string"

February 12, 2025, 4:00 pm

≫ Next: Build Numbers and Versions of Veeam Recovery Orchestrator

≪ Previous: How to Manually Configure Nginx For Use by Veeam Backup for Salesforce

$

0

0

Veeam ONE Report Error "Invalid query string"

KB ID:	4707
Product:	Veeam ONE | 12 | 12.1 | 12.2 | 12.3
Published:	2025-02-13
Last Modified:	2025-02-13

Challenge

When previewing a report in Veeam ONE Web Client, the report fails to load with the error:

Error
Invalid query string

Cause

This error occurs when the URL used to access the Veeam ONE Web Client does not match the URL of the report preview.

For example, if the URL used to access Veeam ONE Web Client is https://one:1239, but the report preview loads the URL https://one.domain.tld:1239.

The underlying reason why the URL must match is due to cookie security in place within Veeam ONE Web Client that requires site URLs to match. This policy is intended as a security feature to prevent potential security risks such as cross-site request forgery (CSRF) and cross-site scripting (XSS) attacks.

Solution

To prevent this issue, use only the expected Veeam ONE Web Client URL.

 

Workaround

The URL used to access Veeam ONE Web Client must match the one expected by the software. The URL can be viewed and modified within the registry on the machine where Veeam ONE is installed.

Note: Changes to this registry value are not permanent and will be reverted by the Veeam ONE Installer during an upgrade.

Key Location: HKLM\SOFTWARE\Veeam\Reporter Enterprise\
Value Name: ReportViewerUri
Value Type: String Value (REG_SZ)
Value Data: 

The value data can be updated as needed to match the URL that will be used to access Veeam ONE Web Client.

Notes

• The Veeam ONE Reporting Service service must be restarted after any changes to the ReportViewerUri value.
• Changes to the ReportViewerUri value will be automatically reverted by the Veeam ONE installer during an upgrade. 
• The ReportViewerUri value is not case-sensitive.
• Changes to the ReportViewerUri value will not cause the Veeam ONE Web Client shortcut on the Desktop to be updated.
• It is not possible to specify more than one valid URI. Therefore, changing ReportViewerUri from its default will cause other users who attempt to use the original default URL to experience the "Invalid query string" error.

 

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

Build Numbers and Versions of Veeam Recovery Orchestrator

February 17, 2025, 4:00 pm

≫ Next: Release Information for Proxmox Virtual Environment Plug-In v12.1.3.197

≪ Previous: Veeam ONE Report Error "Invalid query string"

$

0

0

Build Numbers and Versions of Veeam Recovery Orchestrator

KB ID:	4358
Product:	Veeam Disaster Recovery Orchestrator | 5.0 Veeam Availability Orchestrator | 1.0 | 2.0 | 3.0 | 4.0 Veeam Recovery Orchestrator | 6.0 | 7.0 | 7.1 | 7.2
Published:	2022-09-22
Last Modified:	2025-02-18

This KB article lists all versions of Veeam Recovery Orchestrator and their respective build numbers.

For more information on downloading the latest version of Veeam Recovery Orchestrator, visit:

• My Account Portal - Product Downloads
• Latest Downloads Page
• Veeam Recovery Orchestrator — What's New PDF

_{Note: Version 5.0 of the product was known as Veeam Disaster Recovery Orchestrator.
Note: Prior to version 5.0, the product was known as Veeam Availability Orchestrator.}

Version	Build Number	Release Date	Release Notes
Veeam Recovery Orchestrator 7 Releases
Veeam Recovery Orchestrator 7.2 (Veeam Data Platform 12.3)	7.2.0.203	2025-02-18	HTML
Veeam Recovery Orchestrator 7.1 (Veeam Data Platform 12.2)	7.1.0.278	2024-08-28	HTML
Veeam Recovery Orchestrator 7.1 (Security Patch)	7.1.0.230 noteThe updated build number will only be displayed within the Programs & Features (appwiz.cpl) entry for Veeam Recovery Orchestrator. The build number shown within the UI and logs will still be listed as the previous version.	2024-06-10	KB4585
Veeam Recovery Orchestrator 7.1	7.1.0.205	2024-05-21	—
Veeam Recovery Orchestrator 7 (Security Patch)	7.0.0.379 noteThe updated build number will only be displayed within the Programs & Features (appwiz.cpl) entry for Veeam Recovery Orchestrator. The build number shown within the UI and logs will still be listed as the previous version.	2024-06-10	KB4585
Veeam Recovery Orchestrator 7	7.0.0.337	2023-12-05	PDF
Veeam Recovery Orchestrator 6 Releases
Veeam Recovery Orchestrator 6 P20230419	6.0.0.3516	2023-04-25	KB4437
Veeam Recovery Orchestrator 6	6.0.0.3516	2023-02-21	PDF
Veeam Disaster Recovery Orchestrator 5 Releases
Veeam Disaster Recovery Orchestrator 5.0	5.0.0.2768	2021-11-23	PDF
Veeam Availability Orchestrator 4 Releases
Veeam Availability Orchestrator 4.0	4.0.0.2088	2021-03-16	PDF
Veeam Availability Orchestrator 3 Releases
Veeam Availability Orchestrator 3.0	3.0.0.1770	2020-07-17	PDF
Veeam Availability Orchestrator 2 Releases
Veeam Availability Orchestrator 2.0 P1	2.0.1.1463	2019-08-27	KB2992
Veeam Availability Orchestrator 2.0	2.0.1.1403	2019-05-21	PDF
Veeam Availability Orchestrator 1 Releases
Veeam Availability Orchestrator 1.0	1.0.0.895	2018-02-27	PDF

Swipe to show more of the table

Related Articles

• Build Numbers and Versions of Veeam Backup & Replication
• Build Numbers and Versions of Veeam Backup for Nutanix AHV
• Build Numbers and Versions of Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization
• Build Numbers and Versions of Veeam ONE
• Build Numbers and Versions of Veeam Recovery Orchestrator
• Build Numbers and Versions of Veeam Service Provider Console
• Build Numbers and Versions of Veeam Agent for Microsoft Windows
• Build Numbers and Versions of Veeam Agent for Linux
• Build Numbers and Versions of Veeam Agent for Mac
• Build Numbers and Versions of Veeam Agent for IBM AIX
• Build Numbers and Versions of Veeam Agent for Oracle Solaris
• Build Numbers and Versions of Veeam Backup for Microsoft 365
• Build Numbers and Versions of Veeam Backup for AWS
• Build Numbers and Versions of Veeam Backup for Microsoft Azure
• Build Numbers and Versions of Veeam Backup for Google Cloud
• Build Numbers and Versions of Veeam Backup for Salesforce
• Veeam Data Cloud for Microsoft 365 Release Information and Build Numbers
• Veeam Data Cloud for Microsoft Azure Release Information and Build Numbers

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 Proxmox Virtual Environment Plug-In v12.1.3.197

February 23, 2025, 4:00 pm

≫ Next: Granular sudo Permissions for Management of Proxmox VE Host

≪ Previous: Build Numbers and Versions of Veeam Recovery Orchestrator

$

0

0

Release Information for Proxmox Virtual Environment Plug-In v12.1.3.197

KB ID:	4721
Product:	Veeam Backup & Replication | 12.3
Published:	2025-02-24
Last Modified:	2025-02-20

Requirements

This update to the Proxmox Virtual Environment Plug-In for Veeam Backup & Replication requires:

• Veeam Backup & Replication build 12.3.0.310
  You can check the build number in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.
  
• Proxmox Virtual Environment Plug-In for Veeam Backup & Replication build 12.1.1.1024
  You can check the current build number within the installed applications list.

 

After the updated Proxmox Virtual Environment Plug-In is installed, the Plug-In build number will be 12.1.3.197.

What's New

• Support for Non-Root User Access — Enhance your security setup by integrating Proxmox VE into Veeam Backup & Replication with a sudo user instead of the root user. Enjoy greater control and protection without compromising on functionality. For more information review KB4701.
• Support for Open vSwitch (OVS) — Open vSwitch, crafted specifically for virtualized environments, delivers optimal performance and flexibility for complex infrastructures.
• Support for Smart Object Storage API — Smart Object Storage API (SOSAPI) allows object storage vendors to more deeply integrate with Veeam Backup & Replication and improve performance and user experience. Proxmox VE backup jobs will now interact with SOSAPI-enabled object storage using extended SOSAPI capabilities instead of regular S3 API.
• Support for Nested Pools — Now offering seamless integration of Nested Pools, enabling users to manage and back up virtual machines within nested environments efficiently. 
• Backup engine enhancements — multiple threads are now utilized to read data, resulting in better performance.

 

Resolved Issues

• When restoring backups from different hypervisors, the virtual machine's OS type is set as 'other.'
  
  Now, when restoring from other hypervisors to Proxmox VE (PVE), the restored machine will have the correct OS type, reflecting that of the original backup.
• Backups of powered-off VMs with PCIe passthrough devices fail.
  
  Now, if a PCIe passthrough device is skipped from processing, the job will not process these devices in the backup configuration. As a result, such devices will not be restored as to avoid any conflicts. Such devices should be added manually after the restore.
• Backup of linked clones only processes the base disk without capturing delta changes.
  
  Now, backup jobs will fail if a VM is a linked clone, preventing false assurances of successful backups when only the base disk is backed up without the delta.

 

Download Information

Download Latest Plug-In

^{Filename: PVEPlugin_12.1.3.197.zip}

MD5: 648B9517B233570AF823FD0883EC9C70
SHA1: 3E77EA29E5066D07B98923180866AEB58CA44B7E

Deployment Information

1. Download the updated Proxmox Virtual Environment Plug-In package using the link in this article.
2. Copy PVEPlugin_12.1.3.197.zip to the Veeam Backup Server.
3. Close any open Veeam Backup & Replication Consoles, and ensure no veeam.backup.shell.exe processes are running.
4. Unzip PVEPlugin_12.1.3.197.zip and run PVEPlugin_12.1.3.197.exe.

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.

Granular sudo Permissions for Management of Proxmox VE Host

February 23, 2025, 4:00 pm

≫ Next: Veeam My Account Portal - MFA Guide

≪ Previous: Release Information for Proxmox Virtual Environment Plug-In v12.1.3.197

$

0

0

Granular sudo Permissions for Management of Proxmox VE Host

KB ID:	4701
Product:	Veeam Backup & Replication | 12.3
Published:	2025-02-24
Last Modified:	2025-02-20

Proxmox Virtualization Plug-in Version Requirement

The capability to add Proxmox VE to Veeam Backup & Replication using a non-root sudo user was added in Proxmox Virtual Environment Plug-In version 12.1.3.197 for Veeam Backup & Replication 12.3.

Purpose

This article provides an example granular ‘sudoers’ configuration for the Linux account that will be used by Veeam Backup & Replication when managing a Proxmox VE host.

Solution

Dedicated Proxmox Veeam User Creation

1. Create an SSH login user.
   ^{Note: For the example permissions below, the account is named veeamdep. Configure the sudoer permissions to match the user name you select.}
2. Within the Proxmox configuration, add the user into the Datacenter.
   Datacenter > Permissions > Users > Add
3. Add the Administrator role for the root path ( Path: / ) to that user.
   Datacenter > Permissions > Add > User Permission

Proxmox Veeam User Account Specifications

• The Linux user account used by Veeam Backup & Replication for any Proxymox VE management operations must have /bin/bash shell set by default.
• The account must have root-equivalent permissions, which may be optionally restricted to the following specific list of commands as shown in the example sudoers file below:

veeamdep ALL=(root) PASSWD: /usr/sbin/dmidecode -s system-uuid
veeamdep ALL=(root) PASSWD: /usr/bin/kvm -S *
veeamdep ALL=(root) PASSWD: /usr/bin/qemu-img info *
veeamdep ALL=(root) PASSWD: /usr/bin/qemu-img create *
veeamdep ALL=(root) PASSWD: /usr/sbin/qm create *
veeamdep ALL=(root) PASSWD: /usr/sbin/qm ^showcmd [0-9]+ --pretty$
veeamdep ALL=(root) PASSWD: /usr/sbin/qm ^unlock [0-9]+$
veeamdep ALL=(root) PASSWD: /usr/bin/socat ^TCP-LISTEN:[0-9]+,bind=127\.0\.0\.1 UNIX-CONNECT:/[a-zA-Z0-9_./-]+$
veeamdep ALL=(root) PASSWD: /usr/bin/mkdir -p /var/lib/vz/snippets/
veeamdep ALL=(root) PASSWD: /usr/bin/pvenode cert info --output-format json
veeamdep ALL=(root) PASSWD: /usr/bin/pvesh ^get storage/([a-zA-Z0-9_-]+) --output json$
veeamdep ALL=(root) PASSWD: /usr/bin/pvesh ^set /nodes/([a-zA-Z0-9_-]+)/qemu/([0-9]+)/config --lock ([a-zA-Z]+)$
veeamdep ALL=(root) PASSWD: /usr/bin/pkill -9 -e -f -x socat *
veeamdep ALL=(root) PASSWD: /usr/sbin/lvchange -ay *
veeamdep ALL=(root) PASSWD: /usr/sbin/lvchange -an *
veeamdep ALL=(root) PASSWD: /usr/bin/rbd device map *
veeamdep ALL=(root) PASSWD: /usr/bin/mv ^-n /tmp/([a-zA-Z0-9_-]+\.config) /var/lib/vz/snippets/([a-zA-Z0-9_-]+\.config)$
veeamdep ALL=(root) PASSWD: /usr/bin/rm ^/[a-zA-Z0-9_/-]+/VeeamTmp[a-zA-Z0-9_.-]+$
veeamdep ALL=(root) PASSWD: /usr/bin/rm ^-f /[a-zA-Z0-9_/-]+/VeeamTmp[a-zA-Z0-9_.-]+$
veeamdep ALL=(root) PASSWD: /usr/bin/rm ^-f /var/lib/vz/snippets/[a-zA-Z0-9_-]+\.config$
veeamdep ALL=(root) PASSWD: /usr/bin/rm ^-f /var/lib/vz/template/iso/[a-zA-Z0-9_.-]+\.img$

Copy

Credentials Configuration within Veeam Backup & Replication 

Note: When using granular sudo permissions, ensure that the following options are not selected:

• Add account to the sudoers file — Enabling this option would cause the Veeam software to add the account to the sudoers file with broader permissions than those specified in the granular sudoers example.
• Use "su" if "sudo" fails — Enabling this option would cause Veeam Backup & Replication to switch to using the root account if any of the sudo commands fail due to a command not being included in the granular sudoers file. This could potentially mask a needed update to the granular sudoers file.

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

February 25, 2025, 4:00 pm

≫ Next: Release Information for Veeam Backup for Microsoft 365 8.1 and Cumulative Patches

≪ Previous: Granular sudo Permissions for Management of Proxmox VE Host

$

0

0

Veeam My Account Portal - MFA Guide

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

Purpose

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

Solution

Starting in December 2024, the option to enable MFA for My Account portal login was added. This allows users to enhance the security of their portal access using Time-based One-Time Passwords (TOTP) from authenticator apps.

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

How do I enable MFA for my My Account login?

1. Log in to my.veeam.com
2. Click the avatar icon in the top-right corner and select Edit profile.
   ^{Note: If you haven't recently updated your contact information, you may be prompted to do so before the menu option to Edit profile appears.}

3. Click the Enable MFA link at the bottom of the My profile page.

4. On the Account Security page that loads, click Set up authenticator application.

5. Follow the instructions on the next page to set up MFA using your authenticator app.

Recommendation: Enable Recovery authentication codes

After enabling Authenticator-based 2FA, we recommend also enabling Recovery authentication codes to ensure access in case the authenticator app is unavailable.

How do I disable MFA for my My Account login?

1. Log in to my.veeam.com
2. Click the avatar icon in the top-right corner and select Edit profile.
   ^{Note: If you haven't recently updated your contact information, you may be prompted to do so before the menu option to Edit profile appears.}

3. Click the Enable MFA link at the bottom of the My profile page.

4. On the Account Security page that loads, click the red Remove button within the Authenticator application section.

5. On the confirmation prompt, click Continue to remove the authenticator.

Recovery Codes Are Not Automatically Disabled

If Recovery authentication codes were enabled, they will remain active after removing the authenticator from the Two-factor authentication section. If recovery authentication codes are still active, you will be prompted to enter one to gain access to your account.

If you do not intend to add another Authenticator Application, you should consider disabling the Recovery Codes.

How do I enable Recovery authentication codes for my My Account login?

1. Log in to my.veeam.com
2. Click the avatar icon in the top-right corner and select Edit profile.
   ^{Note: If you haven't recently updated your contact information, you may be prompted to do so before the menu option to Edit profile appears.}

3. Click the Enable MFA link at the bottom of the My profile page.

4. On the Account Security page that loads, click Set up Recovery authentication codes.
   ^{Note: After clicking the link you may be redirected to a sign in page before continuing.}

5. On the next page that loads, you'll be presented with a series of recovery codes. Save the list, check the box, and click Complete Setup.

Save the Recovery Codes

The recovery codes won't appear again after leaving the page.

How do I disable Recovery authentication codes for my My Account login?

1. Log in to my.veeam.com
2. Click the avatar icon in the top-right corner and select Edit profile.
   ^{Note: If you haven't recently updated your contact information, you may be prompted to do so before the menu option to Edit profile appears.}

3. Click the Enable MFA link at the bottom of the My profile page.

4. On the Account Security page that loads, click the red Remove button within the Recovery authentication codes section.

5. On the confirmation prompt, click Continue to Remove Recovery codes.

What happens if I use all 12 recovery codes?

When you log in using the 12th recovery code, you will be presented with another 12 recovery codes, which you should save before proceeding.

When I attempt to use a recovery code it says "Invalid recovery authentication code."

Either the recovery code you entered was wrong or not what the system expected. When using the recovery code entry, the prompt will indicate which code must be entered (e.g., #1, #2, etc.).

I've lost access to my authenticator and recovery codes, how do I recover my account?

For assistance, please contact your Veeam sales representative, who will verify your identity and contact the Veeam support team to disable MFA for your account.

If you are unsure who your Veeam sales representative is, please use the Contact Sales form.

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.1 and Cumulative Patches

February 26, 2025, 4:00 pm

≫ Next: Veeam Intelligence Updates

≪ Previous: Veeam My Account Portal - MFA Guide

$

0

0

Release Information for Veeam Backup for Microsoft 365 8.1 and Cumulative Patches

KB ID:	4711
Product:	Veeam Backup for Microsoft 365 | 8.1
Published:	2025-01-23
Last Modified:	2025-02-27

Requirements

This release can be used to:

• update manually from a previous Veeam Backup for Microsoft 365 8.1 release to the latest Cumulative Patch.
• upgrade an existing v7 or v8 deployment of Veeam Backup for Microsoft 365 to v8.1.
• install a new deployment of Veeam Backup for Microsoft 365 v8.1.

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

Release Information

8.1.0.3503

2025-02-27

Enhancements

• The mechanism of assigning licenses to processed objects was optimized to eliminate excessive request queues.
• The process of collecting information on protected users and their mailboxes was optimized to eliminate excessive queries to individual proxies within a pool.
• Multiple optimizations were made to the processing of individual objects in a proxy pool to avoid oversaturation of processing resources.
• Retention cleanup tasks were optimized to prevent them blocking backup jobs under certain conditions.
• Removed processing delays and slowness in certain operations were eliminated, including retrieving session statistics and resolving objects in a proxy pool after stopping or restarting one of the proxies within a pool.

Resolved issues

• Execution of the  Get-VBOVersion fails with the error:

  The build date was not found for assembly: powershell_ise, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35.
  

8.1.0.331

2025-02-11

Resolved Issues

• In highly loaded environments, processing operations executed on a proxy pool may take longer than expected after one of the proxies in the pool has been restarted, removed, or gone offline.

8.1.0.305

2025-01-23

• Release Notes for Veeam Backup for Microsoft 365 8.1 

Enhancements

• Support for Ubuntu 24.04 and RedHat 9.4 as backup proxy operating systems.
• Multiple stability, performance, and scalability improvements delivered to ensure product reliability.

Resolved Issues

General

• Repository indexing may fail with the error:

  Retry transient error after 00:00:00: Npgsql.NpgsqlException (0x80004005): Exception while reading from stream.
  

• Protection of a host running Veeam Backup for Microsoft 365 using other Veeam solutions may fail with the error:

  VSSControl: Failed to prepare guest for freeze, wait timeout {value} sec.
  

• Under certain conditions, retention cleanup may fail to start, displaying the error:

  Cannot start the retention session because this repository is in use by other sessions.
  

• On immutable object storage repositories associated with a proxy  pool, the extension of the immutability period may fail with the error:

  Item previews are missing (ID: {ID} ({value} bytes)).
  

Upgrade 

• Upgrading a Linux proxy in a proxy pool may fail with the error:

  The command timed out: sudo systemctl stop Veeam.Archiver.Proxy. Current output: {proxy name} was not upgraded.
  

• Under certain conditions, indexing and upgrading an object storage repository may get stuck.
• Upgrading an object storage repository may get stuck.
• Under certain conditions, upgrading an object storage repository may fail with the error:

  Cannot find a web backup for the internal web ID: {ID}.
  

Backup and Backup Copy

• A backup or backup copy job with SharePoint, OneDrive, or Teams data may fail with the error:

  Cannot find object {path}.
  

  For more details, see KB4678.
• Under certain conditions, an Exchange backup job processed in a proxy pool may remain stuck in a running state.
• Under certain conditions, a backup job processed in a proxy pool may become stuck in a running or failed state, and attempts to stop or restart the job fail with errors.
• An Exchange backup job may fail with the error:

  Processing mailbox {user@domain.com} failed with error: Unable to access object storage (reason: Cannot access a disposed object. Object name: 'Veeam.Core.Memory.Reference`2.
  

• A OneDrive backup job may mistakenly attempt to download items blocked by a virus scanner, resulting in a failure with the warning: Failed to backup item:

  {path}, Failed to download block in time: {time}.
  

• The size of backup data transferred by a backup copy job can significantly exceed the size of the source data.
• An Exchange backup to an object storage repository may fail with the error:

  Npgsql.PostgresException (0x80004005): 23505: duplicate key value violates unique constraint “pk_exchange_items_previews_uploads”.
  

• Under certain conditions, a backup copy job transferring SharePoint and Teams data may get stuck in the running state.
• Under certain rare conditions, a backup copy job transferring Exchange data to an archive-tier object storage repository fails with the error:

  The response status code does not indicate success: 409 (this operation is not permitted on an archived blob).
  

Restore

• In Veeam Explorer for Microsoft SharePoint, browsing a SharePoint, Teams (files), or OneDrive backup from an object storage repository may fail with the error:

  Cannot find object {path} or Task failed with exception (task ID: {ID}).
  

  For more details, see KB4678.
• Restoring of Exchange data may fail with the error:

  Failed to get task result because the task does not exist (ID: {ID}).
  

• Under certain rare conditions, when exploring SharePoint backups stored in a Jet-based repository, some items may not be displayed. For more details, see KB4704.
• When initiated via REST APIs, exploring a SharePoint backup containing a Discussion Board may fail with the error:

  Object reference not set to an instance of an object.
  

• In Veeam Explorer for Microsoft Exchange, when an email item is exported to a .MSG file, diacritics are replaced with fallback characters.
• Veeam Explorer for Microsoft SharePoint may not display any content if the backup was retrieved from an archive-tier object storage.

REST APIs

• Execution of the following endpoint with the useAuthentication parameter set to false may fail with the error below:
  (POST) /v8/RestoreSessions/{restoreSessionId}/organization/mailboxes/{mailboxId}/items/sendToDifferentAddress

  Object reference not set to an instance of an object.
  

Download Information

• Upgrade Requirements
• New Install Requirements
• Veeam Backup for Microsoft 365 8.1 Release Notes

Download latest 8.1 ISO

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

Manual Updating

To manually update an existing Veeam Backup for Microsoft 365 version 8.1 (8.1.x) deployment to the latest Cumulative Patch listed on this page, follow the same steps as upgrading Veeam Backup for Microsoft 365.

1. Download the latest ISO.
2. Ensure that there are no active Backup or Restore sessions running.
3. Close all Veeam Backup for Microsoft 365 and PowerShell consoles.
4. Mount the ISO on the Veeam Backup for Microsoft 365 server.
5. Run Veeam.Setup from the ISO.
6. Click Update and follow the prompts to update the software.

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 Intelligence Updates

February 26, 2025, 4:00 pm

≫ Next: How to Relocate Veeam Backup & Replication Backup Files

≪ Previous: Release Information for Veeam Backup for Microsoft 365 8.1 and Cumulative Patches

$

0

0

Veeam Intelligence Updates

KB ID:	4539
Product:	Veeam Backup & Replication | 12.1 | 12.2 | 12.3 Veeam ONE | 12.3
Published:	2024-02-05
Last Modified:	2025-02-27

To learn more about using Veeam Intelligence with Veeam Backup & Replication, review Veeam Backup & Replication User Guide - Veeam Intelligence.

To learn more about using Veeam Intelligence with Veeam ONE, review Veeam One Reporting Guide - Veeam Intelligence.

Purpose

This article documents new features, enhancements, and fixes deployed for the Veeam Intelligence backend logic.

Since all Veeam Intelligence updates are server-side, no updates to Veeam Backup & Replication or Veeam ONE are required to take advantage of the changes described in this article.

Release Information

2025-02-27

Enhancements

• Redundant LLM Instances for Failback: Redundant LLM instances have been added to enable failback between secure Azure OpenAI instances, ensuring continuous service availability and enhanced resilience.

• Enhanced Conversational Logic: The conversation engine now summarizes user context between responses, resulting in more coherent and contextually aware interactions.

• Multi-Agent Architecture in Advanced Mode: A dedicated agent now handles both conversational queries and technical documentation exploration. Additional on-demand agents are provisioned to address specialized data analysis topics.

• Improved Artifact Handling: Artifact management has been refined to better process and utilize datasets generated during Veeam Intelligence data analysis.

• Enhanced Python Code Executor in the Veeam Intelligence Sandbox: The code executor now supports advanced requests, including sorting results and combining/filtering multi-API outputs for improved data processing.

2024-12-03

Starting with this release, the Veeam AI Assistant has been renamed to Veeam Intelligence. 

Veeam Intelligence Basic Mode for Veeam ONE

Veeam Intelligence includes a new online search tooling for Veeam online technical documentation, instead of vectorizing these documents. Allowing for real-time, always up-to-date answers based on these documents.

Veeam Intelligence Advanced Mode for Veeam ONE

The superior and most complete Veeam Intelligence option. Customers can get insights about their Data Protection as Veeam Intelligence queries data that matches the question in natural language, adds context, and provides a comprehensive answer with actionable steps to follow.

2024-08-27

Enhancements

• AI Model — The backend AI model now uses GPT-4o.

2024-01-22

Enhancements

• Trial license support — backup servers with trial licenses are allowed to use the Veeam AI Assistant functionality for the duration of the license.
• Continuous improvements to enhance the quality of responses.

Resolved Issues

• Certain combinations of Socket and VUL licenses are not accepted by the licensing validation service, preventing the use of the Veeam AI Assistant.

2023-12-25

Enhancements

• REST and PowerShell code analysis —  users may now submit their REST API or PowerShell based scripts created for backup server management along with the explanation of the problem that needs fixed. The Veeam AI Assistant will analyze the code to identify the issue and suggest modifications that may help to resolve the problem.
• REST code generation — the Assistant now supports generating code for managing backup server using the REST API. While Assistant can generate code in any programming language requested by the user, using Python delivers the best results. The generated code can be tailored to the customer's needs by providing comprehensive, informative, and detailed requests.
  
  Usage Examples:
  • How do I get an access token for using REST API?
  • Please write a Python script to get information about my failed backup jobs.
  • Please write a Python script using VBR Rest API to get all detected "Infected" events from the malware detection component that happened after 2024-01-16 00:00.

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 Relocate Veeam Backup & Replication Backup Files

February 26, 2025, 4:00 pm

≫ Next: vCenter Server Appliance - Backup/Restore Recommendations

≪ Previous: Veeam Intelligence Updates

$

0

0

How to Relocate Veeam Backup & Replication Backup Files

KB ID:	1729
Product:	Veeam Backup & Replication | 12 | 12.1 | 12.2 | 12.3
Published:	2013-02-08
Last Modified:	2025-02-27

Other Data Relocation-Related Articles

• KB2236 —Moving backup files to/from a Scale-Out Backup Repository.
• KB2321 — Changing the backup location of Veeam Agent jobs operating in Standalone mode (not directly controlled by Veeam Backup & Replication) but targeting a Veeam Backup & Replication server's repository.
• KB4493 — Moving backup data for a file backup or object storage backup to a different repository.
• KB1856 — How to Seed a Backup Copy Job

Purpose

This article provides information about relocating the backup data managed by Veeam Backup & Replication between repositories, including between simple Backup Repositories, Scale-Out Backup Repositories, and Object Storage Repositories.

Solution

Summary

This article documents two methods of relocating backup files:

• Modern method using built-in Move Backup feature.
• Legacy manual file relocation method.

Limitations of Legacy Method

The legacy method to relocate backup files was developed prior to the advent of the native built-in backup file relocation features, Move Backup & Copy Backup. The legacy method involves the user manually moving the backup files, whereas the built-in Backup Move and Backup Copy features utilize the same engine that creates the restore points to automate the backup relocation process. Customers are strongly encouraged to use the built-in Move Backup function when possible. The legacy method documented in this KB article has the following limitations, which are not present with the built-in Move Backup function (explained in italics for each entry below).

• Backup files manually moved to a Fast Clone capable repository (ReFS or XFS) will not be able to utilize Fast Clone until a new Active Full is created.
  
  The built-in Backup Move function, on the other hand, has technology that can migrate backup files in such a way as to preserve Fast Clone functionality without the need to create a new Active Full.
• Manually moving spaceless Synthetic Fulls created by Fast Clone will be inflated to their full size on the destination storage.
  
  The integrated Backup Move function can preserve the space savings of fast clone created synthetic fulls when used to move backup files between Fast Clone compatible repositories.
• The legacy methods documented in this article should not be used to move backup files to or from an Immutable Hardened Linux Repository.
  
  The built-in Backup Move function is capable of handling the intricacies of managing the immutable state of the files on the source or destination Immutable Linux Repository, allowing it to be used to migrate to or from an Immutable Hardened Linux Repository.

Modern Method - Using Built-in Move Backup Feature

Primary Methods

Backup Jobs

• Moving Backups to Another Repository
• Moving Backups to Another Job
• Managing Failed Activities

Backups Copy Jobs

• Moving Backups to Another Repository
• Moving Backups to Another Job
• Managing Failed Activities

Alternate Method to Change the Repository a Job Uses

For more information about the Backup Move feature, please review Veeam Backup & Replication User Guide - Backup Move. That user guide mentions, "Alternatively, you can change the repository in the job settings." Which is what is described here:

1. Disable the backup job(s) planned to be moved.
   
2. (Optional) Create a new repository for the new location where backup files will be located.
   
3. Edit the Backup Job.
4. Switch to the Storage tab.
5. Using the Backup repository drop-down selector, select the new Repository the job should use.
6. Click Next, and a pop-up will appear asking if you want the software to move the existing backup files to the new repository or create a new full backup (start a new backup chain).
7. Select Move Existing.

8. The Move Backup to Another Location window will appear, and the repository selected in Step 5 will be preselected and greyed out. Click Ok to start the Move Backup task in the background.

9. Click Next, Apply, and Finish to complete editing the backup job.
10. Under the Last  24 Hours > Running node, you will notice a Move Backup task occurring. You may double-click on that task to check the progress of the Backup Move task.

11. When the Move Backup task is completed, the job may resume being used.

Legacy Method - Manual File Relocation and Remapping

Procedure Outline

• The customer manually copies or moves the backup files to the new repository.
• Rescan the new repository to make Veeam Backup & Replication aware of the relocated restore points.
• Editing the existing or new job and map that job to the relocated restore points.
• Remove the old restore points from the Veeam Backup & Replication configuration or from disk entirely.

Use case

This method is helpful for situations where utilizing the built-in Move Backup function would not be advantageous, for example, when the connection between the old repository and new repository may be a low-speed connection, and it is more efficient for the backup administrator to move the backups from one site to another physically.

Manual Relocation Procedure

1. Disable the backup job(s) planned to be moved; this will prevent additional restore points from being created during the repository transition. Disabling the job/jobs will also stop any SQL Transaction Log backups, as those running during the transition will cause the final step to fail.
   
2. (Optional if reusing an existing backup repository)
   Create a new repository for the new location where backup files will be located.
   
3. Manually move the backup files to the new repository path. You must include the metadata file (.vbm), full backup files (.vbk), and any needed incremental files (.vib or .vrb).
   
   

   Note:

   • It is recommended that all backup files be moved, but you may omit incremental files if needed. However, if you decide not to move/copy all backup files to the new storage, you must use the “Forget Missing Restore Points” function to clear any references to backup files that were not moved/copied (detailed in Step 7). 
   • There will be folders created inside the directory/path for job names. If your repository path is set as E:\Backups, Job A will go to E:\Backups\Job A.
4. Rescan the destination repository.

5. If the backup files are not encrypted, skip this step.
   If the backup files are encrypted, the encrypted backup will appear under the Backups > Disk (encrypted) node in the inventory pane. In the working area, select the imported backup and click Specify Password on the ribbon, or right-click the backup and select Specify password. (More Information)

6. Observe that after the Rescan has been completed, there will be duplicate entries for the backup files. One is associated with the old Repository under Backups > Disk, and the other is associated with the new repository under Backups > Disk (Imported).
   

Backups listed under Backups > Disk still linked to the old repository.

Backups listed under Backups > Disk (Imported) linked to the new repository.

7. Validate that all backup files associated with the job were relocated by checking the properties of the Backup entry under Disk (Imported).

• If no files are listed in italics, all files were correctly relocated to the new repository. Proceed to the next step.
• If files are listed in italics, this indicates known files were not copied, either unintentionally or intentionally:
  • If files are unintentionally missing, go back to Step 3 and ensure all files are moved.
  • If files were intentionally omitted during Step 3, right-click on any italicized entry and select Forget > All unavailable backups.

8. Edit the Backup or Backup Copy Job, and go to the Storage or Target tab, and from the drop-down menu, select the new repository.

9. After selecting the new repository, click the Map backup link, and in the Select Backup window that appears, expand the repository and select the backup that was relocated.

10. Press Next through the rest of the pages of the wizard to finalize the setting. If no error occurs, and the job now lists the new repository in its Repository column, the mapping has been completed.

11. Verify migration by checking under Backups > Disk to see that the Job's backup files listed there are now associated with the new repository.

12. After testing that the job functions as expected and uses the new repository, the restore points on the old repository can be removed from the Backups > Disk (Orphaned) section using the Delete from disk operation.

Note

If you have attempted to manually import the backup, before performing the steps outlined in this article, you must first "Remove from configuration" any backups that were manually imported. These will be identifiable in the Backups > Disk (Imported) section. They will be listed with the suffix _imported and will have no repository listed in the Repository column.

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.

vCenter Server Appliance - Backup/Restore Recommendations

March 3, 2025, 4:00 pm

≫ Next: Release Information for Hitachi Plug-In for Veeam Backup & Replication

≪ Previous: How to Relocate Veeam Backup & Replication Backup Files

$

0

0

vCenter Server Appliance - Backup/Restore Recommendations

KB ID:	2328
Published:	2017-08-09
Last Modified:	2025-03-04
Languages:	JP

Native File-Based Backup and Restore ^{[Recommended]}

vCenter Server Appliance Data Integrity Best Practices recommends using the native file-based backup and restore operations to protect the vCenter Server Appliance.

Review: VMware vSphere User Guide: Considerations and Limitations for File-Based Backup and Restore
 

Backup

• VMware vSphere User Guide: Schedule a File-Based Backup
• File-Based Backups stored in an SMB or NFS share can be further protected using Veeam Backup & Replication's NAS Backup functionality.

Restore

• VMware vSphere User Guide: Restore vCenter Server from a File-Based Backup

Image-Based Backup and Restore ^{[Not Recommended]}

Considerations and Limitations

Protecting the vCenter Server Appliance (VCSA) using Veeam Backup & Replication is no longer recommended. Instead, Veeam advises customers to utilize the native file-based backup and restore features. This method provides both the simplest and most reliable way to restore the VCSA.

In the past, the need to protect the vCenter outweighed the limitations associated with image-based backups. However, with the advancements in native file-based backups and the simplified VCSA restore process, the necessity for image-based backups has diminished. Although it's technically possible to back up the VCSA using Veeam Backup & Replication, the potential complications make it less appealing.

• Post-Restore VCSA Repair: Image-based backup software, like Veeam Backup & Replication, cannot create a transactionally consistent backup of the VCSA. Consequently, all restore points are only crash-consistent. After restoring the VCSA, it will behave as if it reboot after a hard crash, leaving tasks in an inconsistent state that may require extensive work with VMware Support to resolve.
• Post-Restore Environment State: When restoring the VCSA from an image-based backup, any differences that occurred between when the backup was created and when the restore was performed will not be known by the restored VCSA and may require extensive work with VMware Support to reconcile.
• Impact of VCSA Backup: Backing up the VCSA while backup jobs for other VMs are occurring can increase the likelihood of causing those other jobs to fail. This is due to the impact of snapshot creation and removal stun on the VCSA.
• VMware vSphere User Guide: Considerations and Limitations for Image-Based Backup and Restore

Having considered all of the limitations and possible impacts, if you still wish to protect the vCenter Server Appliance with an image-based backup using Veeam Backup & Replication, click the following heading to expand the section with advice on doing so:

Image-Based Backup and Restore Advice

Image-based backup of the VCSA may be performed for an added level of protection to complement an existing native file-based backup. Preference should always be given to backing up and restoring using the native File-Based Backups.

Review: VMware vSphere User Guide: Considerations and Limitations for Image-Based Backup and Restore

 

Backup

• Create a dedicated backup job for the VCSA.
• Schedule the backup job protecting the VCSA to run when no other backup jobs occur.
  Scheduling this way will prevent conflicts when other backup jobs attempt to send requests to the VCSA when it may be briefly unavailable during snapshot creation and removal events, which occur at the start and end of the backup job.
• Disable VMware Tools Quiescence within the job protecting the VCSA.
• Disable Application-Aware Processing and Guest File System Indexing within the job for the VCSA.
   

Restore

• Before initiating an Image-Based restore of the VCSA, review the following documents:
  • VMware vSphere User Guide: Considerations and Limitations for Image-Based Backup and Restore
  • Restore a vCenter Server Image-based Environment
  • How to restore your vCenter when there is no vCenter
• Perform an Entire VM Restore or Instant VM Restore.
  

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 Hitachi Plug-In for Veeam Backup & Replication

March 16, 2025, 5:00 pm

≫ Next: CVE-2025-23120

≪ Previous: vCenter Server Appliance - Backup/Restore Recommendations

$

0

0

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

KB ID:	4191
Product:	Veeam Backup & Replication | 12 | 12.1 | 12.2 | 12.3
Published:	2021-07-21
Last Modified:	2025-03-17

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.1.225, make sure that you are running Veeam Backup & Replication build 12.0.0.1420 P20230718 or higher. 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 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.

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 DRS attribute. The attribute must be inherited to 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.
• Adding Hitachi storage to the Veeam Backup & Replication infrastructure via Service Processor (SVP) IP is only supported for the VSP 5000 and VSP One Block series. For other storage models, use one of the CTL1/CTL2 IP addresses when adding the storage.
• 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. If you want to enable VM processing using VMware snapshots, 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.

Deployment Information

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

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

Download Information

Download Hitachi Plug-In

^{Release date: 2025-03-17}

MD5: 9D98091EDE24E0BA56DA8DE6229CFE8E
SHA1: B6D4E775FA9E578BE7D288A80E8E12520ECF69D6

Previous Versions

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

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.

CVE-2025-23120

March 18, 2025, 5:00 pm

≫ Next: List of Security Fixes and Improvements in Veeam Backup & Replication

≪ Previous: Release Information for Hitachi Plug-In for Veeam Backup & Replication

$

0

0

CVE-2025-23120

KB ID:	4724
Product:	Veeam Backup & Replication | 12 | 12.1 | 12.2 | 12.3
Published:	2025-03-19
Last Modified:	2025-03-19

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.

Issue Details

CVE-2025-23120

A vulnerability allowing remote code execution (RCE) by authenticated domain users.

Severity: Critical
CVSS v3.1 Score: 9.9AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Source: Reported by Piotr Bazydlo of watchTowr.

Note: This vulnerability only impacts domain-joined backup servers, which is against the Security & Compliance Best Practices.

Afffected Product

Veeam Backup & Replication 12.3.0.310 and all earlier version 12 builds.
_{Note: Unsupported product versions are not tested, but are likely affected and should be considered vulnerable.}

Solution

The vulnerability documented in this section was fixed starting in the following build:

• Veeam Backup & Replication 12.3.1 (build 12.3.1.1139)

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

List of Security Fixes and Improvements in Veeam Backup & Replication

March 18, 2025, 5:00 pm

≫ Next: Build Numbers and Versions of Veeam Backup for Nutanix AHV

≪ Previous: CVE-2025-23120

$

0

0

List of Security Fixes and Improvements in Veeam Backup & Replication

KB ID:	3103
Product:	Veeam Backup & Replication | 10 | 11 | 12 | 12.1 | 12.2 | 12.3 | 12.3.1 Veeam Cloud Connect | 10 | 11 | 12 | 12.2 | 12.3
Published:	2020-03-02
Last Modified:	2025-03-19

Purpose

This article describes all security-related fixes and improvements introduced in each release or update of Veeam Backup & Replication.

The goal of this article is to provide our customers' security and compliance teams with detailed information on security improvements between releases, in order to help them make an informed decision on whether it is critical to upgrade from their current Veeam Backup & Replication version to a latter one.

Security Fixes and Improvements

12.3.1.1139

• CVE-2025-40711 vulnerability was fixed.

 

12.3.0.310

• curl upgraded to version 8.10.1
• CVE-2024-40717 vulnerability was fixed.
• CVE-2024-42451 vulnerability was fixed.
• CVE-2024-42452 vulnerability was fixed.
• CVE-2024-42453 vulnerability was fixed.
• CVE-2024-42455 vulnerability was fixed.
• CVE-2024-42456 vulnerability was fixed.
• CVE-2024-42457 vulnerability was fixed.
• CVE-2024-45204 vulnerability was fixed.
   

12.2.0.334

• npgsql upgraded to 6.0.11
• libxml upgraded to version 2.13.3
• curl upgraded to version 8.8.0
• CVE-2024-39718 vulnerability was fixed.
• CVE-2024-40710 vulnerability was fixed.
• CVE-2024-40711 vulnerability was fixed.
• CVE-2024-40712 vulnerability was fixed.
• CVE-2024-40713 vulnerability was fixed.
• CVE-2024-40714 vulnerability was fixed.
   

12.1.2.172

• PuTTY updated to version 0.81
• VMware Virtual Disk Development Kit (VDDK) was updated to 7.0.3.4 to address  CVE-2023-38545.
• Microsoft .NET 6.0.25 was updated to 6.0.29. 
• Microsoft WebView2 was updated to 123.0.2420.81. 
• PostgreSQL installer was updated to 15.6.1. 
• Curl was updated to 8.5.
• Vulnerability CVE-2024-29849 in Veeam Backup Enterprise Manager was fixed.
  
• Vulnerability CVE-2024-29850 in Veeam Backup Enterprise Manager was fixed.
  
• Vulnerability CVE-2024-29851 in Veeam Backup Enterprise Manager was fixed.
• Vulnerability CVE-2024-29852 in Veeam Backup Enterprise Manager was fixed.
  
  

12.1.1.56

• PuTTY updated to version 0.80
   

12.1.0.2131

• OpenSSL library updated to 1.0.2zi
• LZ4 library updated to 1.9.4
• curl updated to 8.0.1
• Azure Identity package updated to 1.10.2
• Stronger backup encryption (see What's New in 12.1 p.7)
• Enhanced protection for stored credentials  (see What's New in 12.1 p.7)
   

12.0.0.1420 P20230412

• OpenSSL Library updated to the newest version (1.0.2zg).
   

12.0.0.1420 P20230223

• Vulnerability (CVE-2023-27532) in Veeam Backup Service was fixed.
  This vulnerability was reported by Shanigen.
   

12.0.0.1420

• Added support for networks with NTLM authentication disabled (Kerberos-only authentication).
• Added Best Practices Analyzer to check product configuration.
• Audit capabilities were improved.
• Added possibility to limit the number of logon sessions per user and to log off users after an inactivity period
• SMTP certificates validation was added for email notifications
• Network communication between CDP components is encrypted with TLS
• Disabled insecure TLS protocols in communication with VMware infrastructure
• zlib has been updated to version 1.2.13
• OpenSSL version has been updated to 1.0.2ze
• Putty has been updated to version 0.76
  
  

11.0.1.1261 P20240304

• VMware Virtual Disk Development Kit (VDDK) was updated to 7.0.3.4.
• OpenSSL was updated to v1.0.2zi.
• liblz4 was updated to v1.9.4.
• zlib was updated to v1.2.13.
• PuTTY was updated to 0.80.
   

11.0.1.1261 P20230227

• Vulnerability (CVE-2023-27532) in Veeam Backup Service was fixed.
  This vulnerability was reported by Shanigen.
   

11.0.1.1261 P20220302

• Vulnerabilities (CVE-2022-26500, CVE-2022-26501) in Veeam Distribution Service were fixed.
  These vulnerabilities were reported by Nikita Petrov (Positive Technologies).
  
• Vulnerability (CVE-2022-26504) in Veeam.Backup.PSManager was fixed.
• Vulnerability (CVE-2022-26503) in Veeam Agent for Microsoft Windows was fixed.
  This vulnerability was reported by Nikita Petrov (Positive Technologies).
   

11.0.1.1261

• Linux data mover: Added support for ECDHE TLS cipher suites; improved transport security.
• Veeam Backup Enterprise Manager: hardened HTTP header configuration; disabled HTTP Trace method; restricted an ability to log into the Self-Service Restore Portal under NETWORK SERVICE accounts (the portal was dysfunctional for such logins).
• Helper appliances: updated OpenVPN to version 2.4.11; updated OpenSSH to version 8.6.
• Debug logs: Addressed issues which could result in sensitive information logged under certain circumstances.
   

11.0.0.837 P20210507

• Vulnerability (CVE-2021-35971) in the deserialization logic of Microsoft .NET remoting has been fixed.
   

11.0.0.837

• .NET remoting communication security has been improved.
  
• Data Mover communication protocol security has been improved.
• Agent Management architecture security has been improved.
• Veeam Explorers integration security has been improved
• Veeam Backup Enterprise Manager Web App configuration and headers security has been improved.
• Addressed issues which could cause sensitive information logged in certain circumstances.
• Third-party libraries in FLR and SureBackup helper appliance have been updated to current versions.
• Sustansys.Saml2 has been updated to version 2.7 to address known vulnerabilities.
• LZ4 compression library version has been updated to version 1.9.2
   

10.0.1.4854 P20220304

• Vulnerabilities (CVE-2022-26500, CVE-2022-26501) in Veeam Distribution Service were fixed.
  These vulnerabilities were reported by Nikita Petrov (Positive Technologies).
  
• Vulnerability (CVE-2022-26504) in Veeam.Backup.PSManager was fixed.
• Vulnerability (CVE-2022-26503) in Veeam Agent for Microsoft Windows was fixed.
  This vulnerability was reported by Nikita Petrov (Positive Technologies).
   

10.0.1.4854 P20210609

• Vulnerability (CVE-2021-35971) in the deserialization logic of Microsoft .NET remoting has been fixed.
   

10.0.1.4854

• NAS Backup functionality can be used to gain unprivileged access to files on managed servers.
• Weak credentials encryption issue in guest processing command line parameter and in PowerShell cmdlet logs.
• Server and IIS version information is included in the response header of the Veeam Backup Enterprise Manager web app.
• Security of Agent Management architecture has been improved.
• Security of Cloud Connect architecture has been improved.
• libcurl version has been updated to 7.70
   

10.0.0.4461

• A custom security descriptor was provided for the driver's control device (vulnerability reported by Mile Karry).
• Deserialization issues were fixed (vulnerability reported by Harrison Neal).
• A user authorization issue was fixed (vulnerability reported by Harrison Neal).
• Security of the Enterprise Manager Web App configuration was improved.
• Support for weak SSH ciphers was disabled in the recovery media ISOs.
• OpenSSL library was updated to version 1.0.2t
• Putty was updated to version 0.73
• Weak TLS ciphers were disabled in the Surebackup Linux appliance.

More Information

As we're establishing this new process, we appreciate any feedback on the content or format of this KB article. Please let us know in the corresponding topic on the Veeam Community Forums. If your feedback is too sensitive to be shared publicly, please submit it by opening a support case. We highly appreciate your collaboration!

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

Build Numbers and Versions of Veeam Backup for Nutanix AHV

March 18, 2025, 5:00 pm

≫ Next: Release Information for Veeam Backup & Replication 12.3

≪ Previous: List of Security Fixes and Improvements in Veeam Backup & Replication

$

0

0

Build Numbers and Versions of Veeam Backup for Nutanix AHV

KB ID:	4299
Product:	Veeam Backup for Nutanix AHV | 2.0 | 2.1 | 3.0 | 4.0 | 5.0 | 5.1 | 6 | 6.1 | 7 Veeam Availability for Nutanix AHV | 1.0
Published:	2022-04-13
Last Modified:	2025-03-19

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

For more information on downloading the latest version of Veeam Backup for Nutanix AHV, visit:

• Veeam Backup for Nutanix AHV — Current Version Download Page

Starting with the release of Veeam Backup & Replication 12.1, the What's New information for integrated products, like Veeam Backup for Nutanix AHV, is included in the Veeam Backup & Replication What's New PDF.

^{Note: Prior to version 2.0, the product was known as Veeam Availability for Nutanix.}

Version	Build Number	Plug-In Build	Release Date	Release Notes	Product Guides
Veeam Backup for Nutanix AHV 7 Releases
Veeam Backup for Nutanix AHV 7.1	7.0.1.12	12.7.1.12	2025-03-19
Veeam Backup for Nutanix AHV 7.0	7.0.0.241	12.7.0.172	2024-12-03	HTML
Veeam Backup for Nutanix AHV 6 Releases
Veeam Backup for Nutanix AHV 6.1	6.1.0.14	12.6.1.15	2024-09-26	KB4668	HTML
Veeam Backup for Nutanix AHV 6.0	6.0.0.1228	12.6.0.632	2024-08-24	HTML	ZIP
Veeam Backup for Nutanix AHV 5 Releases
Veeam Backup for Nutanix AHV 5.1	5.1.0.7	12.5.1.8	2023-12-05	KB4521	-
Veeam Backup for Nutanix AHV 5	5.0.0.1080	12.5.0.465	2023-09-27	PDF	-
Veeam Backup for Nutanix AHV 4 Releases
Veeam Backup for Nutanix AHV 4a	4.0.1.18	12.1.4.5	2023-04-19	KB4426	-
Veeam Backup for Nutanix AHV 4	4.0.0.1899	12.0.4.1020	2023-02-14	PDF	-
Veeam Backup for Nutanix AHV 3a Releases
Veeam Backup for Nutanix AHV 3a	3.1.36	11.1.3.33	2022-01-18	KB4272	-
Veeam Backup for Nutanix AHV 3	3.0.775	11.0.3.819	2021-09-24	PDF KB4214	-
Veeam Backup for Nutanix AHV 2 Releases
Veeam Backup for Nutanix AHV 2.1	2.1.396		2021-02-24	PDF KB4117	-
Veeam Backup for Nutanix AHV 2	2.0.558		2020-03-24	PDF KB3133	-
Veeam Availability for Nutanix 1 Releases
Veeam Availability for Nutanix 1.0 U3	1.0.829		2019-10-09	KB3013	-
Veeam Availability for Nutanix 1.0 U2	1.0.632		2019-05-30	KB2956	-
Veeam Availability for Nutanix 1.0 U1	1.0.457		2018-11-30		-
Veeam Availability for Nutanix 1.0	1.0.342		2018-07-26		-

Swipe to show more of the table

Related Articles

• Build Numbers and Versions of Veeam Backup & Replication
• Build Numbers and Versions of Veeam Backup for Nutanix AHV
• Build Numbers and Versions of Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization
• Build Numbers and Versions of Veeam ONE
• Build Numbers and Versions of Veeam Recovery Orchestrator
• Build Numbers and Versions of Veeam Service Provider Console
• Build Numbers and Versions of Veeam Agent for Microsoft Windows
• Build Numbers and Versions of Veeam Agent for Linux
• Build Numbers and Versions of Veeam Agent for Mac
• Build Numbers and Versions of Veeam Agent for IBM AIX
• Build Numbers and Versions of Veeam Agent for Oracle Solaris
• Build Numbers and Versions of Veeam Backup for Microsoft 365
• Build Numbers and Versions of Veeam Backup for AWS
• Build Numbers and Versions of Veeam Backup for Microsoft Azure
• Build Numbers and Versions of Veeam Backup for Google Cloud
• Build Numbers and Versions of Veeam Backup for Salesforce
• Veeam Data Cloud for Microsoft 365 Release Information and Build Numbers
• Veeam Data Cloud for Microsoft Azure Release Information and Build Numbers

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 & Replication 12.3

March 18, 2025, 5:00 pm

≫ Next: Build Numbers and Versions of Veeam Agent for Microsoft Windows

≪ Previous: Build Numbers and Versions of Veeam Backup for Nutanix AHV

$

0

0

Release Information for Veeam Backup & Replication 12.3 and Updates

KB ID:	4696
Product:	Veeam Backup & Replication | 12.3
Published:	2024-12-03
Last Modified:	2025-03-19

Requirements

You can check the installed build number in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.

Release Information

12.3.1.1139

2025-03-19

Security

Vulnerabilities

^{Indicated severity values are CVSS 3.1 scores.}

Veeam Backup & Replication

• CVE-2025-40711 | Severity: Critical (9.9)
  A vulnerability allowing remote code execution (RCE) by authenticated domain users.
  
  Note: This vulnerability only impacts domain-joined backup servers, which is against the Security & Compliance Best Practices.

New features and enhancements

Platform Support

• VMware vSphere 9.0 readiness based on the pre-release builds. The official support will be confirmed with a full regression testing of the GA build when it becomes available. This article and KB2443 will be updated with a support statement following that.
• IBM Db2 plug-in now supports Db2 version 12.1 and SLES 12 SP5.
• SAP HANA plug-in now supports SAP HANA 2.0 SPS 08 and SLES 15 SP6 for SAP HANA on IBM Power.

Microsoft Entra ID Backup

• Protection of conditional access policies can now be enabled by adding the following registry value to the Veeam Backup Server.
  Due to popular demand, this functionality has been backported from the next major release, where it will become available as an option in the user interface.
  Note: This functionality is only available for Essentials, Advanced, and Premium editions.
  
  Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
  Value Name: EntraIdBackupSupportsConditionalAccessPolicyRestore
  Value Type: DWORD (32-bit) Value
  Value Data: 1
• License consumption logic was updated to no longer consume licenses for external (guest) users and disabled users. Any licenses associated with previously licensed objects will be released automatically 30 days after installing 12.3.1. Alternatively, you can revoke these licenses immediately using the License Information dialog.

Nutanix AHV

• Removed the experimental support designation for malware detection, guest file indexing, and application-aware processing, except database log file shipping, which will still be considered experimental.
  Note: The experimental status removal does not retroactively apply to existing 12.3.0 installs and requires updating to 12.3.1 due to the included related bugfix.

Proxmox VE

• Updated ProxmoxVE plug-in enables the usage of non-root users to register Proxmox, support for Open vSwitch (OVS) networking, Object Storage API (SOSAPI), Nested Pools for backup jobs scope, and brings further backup performance improvements. For more information, please refer to KB4721.

VMware vSphere

• Instant VM Recovery engine improvements deliver a 5x increased number of simultaneous instant VM recoveries: up to 1000 VMs per backup server and up to 200 VMs per vPowerNFS server. The readiness check for VM migration to production storage has also been optimized to improve performance.
• Automatically disconnect vPower NFS datastores after Instant VM Recovery sessions are completed, reduce alarms or misleading capacity planning calculations caused by disconnected vPower NFS datastores. To configure, create the following registry value on the backup server:
  Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
  Value Name: vPowerNFSUnmountDatastore
  Value Type: DWORD (32-bit) Value
  Value Data: 1

Malware Detection

• Custom Internet proxy support has been added for downloading updates to the Veeam Threat Hunter threat signatures. To configure, create the following registry value on the Mount Server:
  
  Key Location: HKLM\ SOFTWARE\Veeam\Veeam Threat Hunter\
  Value Name: VTHInternetProxy
  Value Type: String Value (REG_SZ)
  Value Data: <proxy>:<port>
  
  Note: The system-wide Internet proxy settings are now also respected; see the Resolved Issues section below.
  
  

Object Storage

• Automatic bucket creation mode is now used by default for newly created S3-compatible object storage repositories.
• Improved object storage compatibility by allowing the backup server to ignore errors caused by S3-compatible object storage using unconventional storage class names. This can be enabled by creating the following registry value on the Veeam Backup Server:
  
  Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
  Value Name: S3IgnoreCustomStorageClasses
  Value Type: DWORD (32-bit) Value
  Value Data: 1

Secondary Storage Integrations

• Dell Data Domain DD OS versions 8.2 and 8.3 support added for Data Domain integration as a backup repository.
• Microsoft SQL Server plug-in performance improvements when writing to deduplication appliances, thanks to leveraging parallel streams, each using its own VAB file, even when backing up a single database.

Unstructured Data Backup

• Metadata captured by the Amazon S3 Metadata service is now included in object storage backups to ensure comprehensive bucket data protection.

Configuration Database

• TLS connection support for the PostgreSQL configuration database has been added for improved security when hosting the database on an external server.

Email Notifications

• OAuth 2.0 support for nonstandard Azure regions, including the U.S. Government, China, and Germany, is now available for email notifications. To enable this, create the following registry value on the Veeam Backup Server:
  
  Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
  Value Name: EmailNotificationMicrosoftCloudInstance
  Value Type: String Value (REG_SZ)
  Value Data: <desired_region_name>

Setup

• New ISO-based update distribution reduces downtime by accerleating update installation and eliminates the additional disk space requirement on the backup server, which was previously needed for unpacking the update before its installation.
• Windows Script Host no longer needs to be temporarily enabled to install product updates.

Veeam Vault

• Added automatic upgrade of Veeam Vault V1 backup repositories (shared keys authentication) to V2 (Entra ID authentication) for added security and improved user experience.

API

• New REST API capabilities include changing existing password records, rescanning all backup repository types, downloading metadata for Unstructured Data backups, and performing backup deletion.
• New PowerShell capabilities include connection to Veeam Vaults, querying, and restoring protected Microsoft Entra ID conditional access policies.

Resolved Issues

General

• When deleting backups from disk, the backup console should no longer require a decryption password to be provided for encrypted backups.
• Backups in legacy per-VM backup file format should no longer disappear from the Backups > Disk node, preventing you from initiating backup metadata format upgrade.

Proxmox VE

• OS type of VMs restored from backups of other hypervisors is erroneously set as Other.
• Backups of powered-off VMs with PCIe passthrough devices fail due to an attempt to back up those devices.
• Backup of VMs that are linked clones is not supported and will now correctly fail instead of processing only the base disk without capturing delta.

Nutanix AHV

• The job scheduler should no longer suspend the initiation of scheduled backup jobs in certain circumstances.
• Scheduled or manual active full protection domain backup jobs should no longer create incremental rather than full VM restore points.
• Prism Central category-based exclusions can now be set for jobs using cluster as a backup scope.
• Nutanix Guest Tools quiescence advanced job settings are not properly communicated to Nutanix clusters during backup jobs.
• In rare circumstances, retention policy processing may delete some restore points preemptively.

Agent Management

• Backup agents fail to perform retention processing for backups located on SOBR Capacity Tier extents after the backup chain has been evacuated from a Performance Tier extents running in a direct connection mode.
• Veeam Agent for Windows Recovery Media created from Microsoft Windows Server 2025 or Microsoft Windows 11 24H2 machines in certain configuration states, fails to boot.

Malware detection

• Veeam Threat Hunter signature update process ignores the system-wide Internet proxy settings and may experience intermittent interruptions due to not retrying unexpected HTTP errors.
• Indicators of compromise detection remains enabled even if the parent File system activity analysis checkbox is cleared.

Object Storage

• Entire VM restore from scale-out repository Archive Tier may fail for encrypted backups with the error:

  Master key not found for keyset
  

• Restoring from a backup that has been retrieved from the scale-out repository Archive Tier may fail with the error:

  Agent failed to process method {DataTransfer.RestoreText}
  

• Reverting Archive Tier to previous checkpoints using the corresponding PowerShell cmdlet is not possible after a scale-out repository has been recreated.
• In certain circumstances, if the initial archiving session fails, all subsequent archiving sessions will fail with the error:

  Index in DB is not synchronized with archive
  

• Continuously interrupting Capacity Tier offload sessions may result in checkpoints being deleted before the corresponding restore point can be stored, resulting in all subsequent offload sessions failing with the error:

  Index is not synchronized
  

• Importing encrypted backup containing duplicate encryption keys from Capacity Tier fails with the error:

  Failed to import backup: Violation of unique key constraint
  

Tape

• Backup to Tape jobs will be interrupted by source File Backup job even when the “Prevent this job from being interrupted by source backup jobs” option is selected.
• Backup to Tape jobs may experience performance degradation when processing backups produced by File Backup jobs.
• The latest firmware updates for some hardware encryption modules cause recovery failures due to the presence of unrecognizable KAD (Key-Associated Data) descriptors.
• Configuration database records are not removed after a tape media is erased, causing unnecessary database size growth.

Cloud Connect

• Switch-VBRCloudTenantsQuotaRepositoryToSOBR cmdlet fails to execute for tenants with multiple quotas assigned.

12.3.0.310

2024-12-03

Release Information

• Release Notes
• What's New

Download Information

The installed build number can be found in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.

Updating to Veeam Backup & Replication 12.3.1 From 12.3

Use the following Updater ISO for:

• Updating existing deployments of Veeam Backup & Replication 12.3.

DOWNLOAD 12.3.1 Update

^{Filename: VeeamBackup&Replication_12.3.1.1139_20250315_update.iso}
MD5: 70E802E77F3FC109E85F8FA859F31950
SHA1: 308E6AE02474208A08418734598CFBA0E7AF82D0

Upgrading to Veeam Backup & Replication 12.3 From Previous Versions

Use the following ISO for:

• New deployments of Veeam Backup & Replication 12.3.
• Upgrading existing deployments of Veeam Backup & Replication (11a, 12, 12.1, 12.2) to 12.3.
  

Remember to always review the Upgrade Checklist as part of your upgrade process.

DOWNLOAD latest 12.3 ISO

See the Current Versions Download Page for ISO hashes.

Reboot May Be Required

Please note that a reboot may be required after installing the update. 

Please plan accordingly.

ISO Release History

^{Previously released files are not publicly available for download. Mouse-over or tap the filenames in the table to view a file's MD5 and SHA1 checksum.}

Release Date	ISO Filename	Changelog
Veeam Backup & Replication 12.3.1.1139 Releases
2025-03-19	VeeamBackup&Replication_12.3.1.1139_20250315.isoMD5: 447564A6A740479678C18E33E2296CC8 SHA1: BB94F8A40EDE5F7E55417E018BFF603903AD243A	Initial Release
Veeam Backup & Replication 12.3.0.310 Releases
2025-02-24	VeeamBackup&Replication_12.3.0.310_20250221.isoMD5: 3C33E8D6F7F051EEBC642814EA296721 SHA1: 19693E8C8D7EDDAA828745EA59020D4A9DDF7488	Google Cloud Plug-In for Veeam Backup & Replication package updated.
2024-12-16	VeeamBackup&Replication_12.3.0.310_20241211.isoMD5: 6B075E5910D1E2F47B77562FE8C42E16 SHA1: B7BC52A580BAC04A7ECD5DCFFDBD1C4C2E7E62B4	The installer now checks if Windows Script Host is disabled. (To prevent the issue documented on KB4698.)
2024-12-03	VeeamBackup&Replication_12.3.0.310_20241201.isoMD5: 92B9BA7506E07889DAFFE92DB15D093C SHA1: 972A8A38BBDBE80C0D11284E99586AFDF60DD56D	Initial Release

Swipe to show more of the table

Updater ISO Release History

^{Previously released files are not publicly available for download. Mouse-over or tap the filenames in the table to view a file's MD5 and SHA1 checksum.}

Release Date	Updater ISO Filename	Changelog
Veeam Backup & Replication 12.3.1.1139 Releases
2025-03-19	VeeamBackup&Replication_12.3.1.1139_20250315_update.isoMD5: 70E802E77F3FC109E85F8FA859F31950 SHA1: 308E6AE02474208A08418734598CFBA0E7AF82D0	Initial Release

Swipe to show more of the table

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

---

Build Numbers and Versions of Veeam Agent for Microsoft Windows

March 18, 2025, 5:00 pm

≫ Next: Error: "Cannot find the object on the mount host."

≪ Previous: Release Information for Veeam Backup & Replication 12.3

$

0

0

Build Numbers and Versions of Veeam Agent for Microsoft Windows

KB ID:	2683
Product:	Veeam Agent for Microsoft Windows | 2.0 | 2.1 | 2.2 | 3.0.2 | 4.0 | 5.0 | 6.0 | 6.1 | 6.2 | 6.3 | 6.3.1
Published:	2018-07-10
Last Modified:	2025-03-19

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

For more information on downloading the latest version of Veeam Agent for Microsoft Windows, visit:

• Veeam Agent for Microsoft Windows — Current Version Download Page
• Veeam Agent for Microsoft Windows — What's New (Current Version)

_{Note: Prior to version 2.0, the product was known as Veeam Endpoint Backup.}

Version	Build Number	Release Date	Release Notes	Product Guides
Veeam Agent for Microsoft Windows 6 Releases
Veeam Agent for Microsoft Windows 6.3.1 included with Veeam Backup & Replication 12.3.1	6.3.1.1074	2025-03-19	HTML
Veeam Agent for Microsoft Windows 6.3 included with Veeam Backup & Replication 12.3	6.3.0.177	2024-12-03
Veeam Agent for Microsoft Windows 6.2 included with Veeam Backup & Replication 12.2	6.2.0.121	2024-08-28	HTML	ZIP
Veeam Agent for Microsoft Windows 6.1.2 included with Veeam Backup & Replication 12.1.2	6.1.2.134	2024-05-21	PDF	ZIP
Veeam Agent for Microsoft Windows 6.1 included with Veeam Backup & Replication 12.1	6.1.0.349	2023-12-05	-	ZIP
Veeam Agent for Microsoft Windows 6.0.2 included with Veeam Backup & Replication 12 P20230412	6.0.2.1090	2023-04-13	PDF	ZIP
Veeam Agent for Microsoft Windows 6 GA included with Veeam Backup & Replication 12 GA	6.0.0.960	2023-02-14	PDF	ZIP
Veeam Agent for Microsoft Windows 6 RTM included with Veeam Backup & Replication 12 RTM	6.0.0.959	2023-01-30	-	-
Veeam Agent for Microsoft Windows 5 Releases
Veeam Agent for Microsoft Windows 5.0.3.5029 included with Veeam Backup & Replication 11a P20240304	5.0.3.5029	2024-03-07	( ! )This build was included within the Veeam Backup & Replication 11a P20240304 package. See KB4245	-
Veeam Agent for Microsoft Windows 5.0.3 included with Veeam Backup & Replication 11a P20220302	5.0.3.4708	2022-03-12	PDF	-
Veeam Agent for Microsoft Windows 5.0.2 included with Veeam Backup & Replication 11a P20211211	5.0.2.4680	2021-12-22	PDF	-
Veeam Agent for Microsoft Windows 5.0.1 GA included with Veeam Backup & Replication 11a GA	5.0.1.4584	2021-10-07	PDF	-
Veeam Agent for Microsoft Windows 5.0.1 RTM included with Veeam Backup & Replication 11a RTM	5.0.1.4584	2021-09-24	-	-
Veeam Agent for Microsoft Windows 5 GA included with Veeam Backup & Replication 11 GA	5.0.0.4301	2021-02-24	PDF	-
Veeam Agent for Microsoft Windows 5 RTM included with Veeam Backup & Replication 11 RTM	5.0.0.4300	2021-02-11	-	-
Veeam Agent for Microsoft Windows 4 Releases
Veeam Agent for Microsoft Windows 4.0.2 included with Veeam Backup & Replication 10a P20220304	4.0.2.2208	2022-03-12	PDF	-
Veeam Agent for Microsoft Windows 4.0.1 included with Veeam Backup & Replication 10a GA	4.0.1.2169	2020-08-04	PDF	-
Veeam Agent for Microsoft Windows 4 included with Veeam Backup & Replication 10 GA	4.0.0.1811	2020-02-18	PDF	-
Veeam Agent for Microsoft Windows 3 Releases
Veeam Agent for Microsoft Windows 3.0.2 included with Veeam Backup & Replication 9.5 U4b	3.0.2.1170	2019-07-16	PDF	-
Veeam Agent for Microsoft Windows 3.0.1 included with Veeam Backup & Replication 9.5 U4a	3.0.1.1039	2019-03-26	PDF	-
Veeam Agent for Microsoft Windows 3 included with Veeam Backup & Replication 9.5 U4	3.0.0.748	2019-01-22	PDF	-
Veeam Agent for Microsoft Windows 2 Releases
Veeam Agent for Microsoft Windows 2.2	2.2.0.589	2018-07-03	PDF	-
Veeam Agent for Microsoft Windows 2.1	2.1.0.423	2017-12-19	PDF	-
Veeam Agent for Microsoft Windows 2.0	2.0.0.700	2017-05-11	PDF	-
Veeam Endpoint Backup 1 Releases
Veeam Endpoint Backup 1.5	1.5.0.306	2016-03-17	PDF	-
Veeam Endpoint Backup 1.1	1.1.1.212	2015-10-05	PDF	-
Veeam Endpoint Backup 1.0	1.0.0.1954	2015-04-14	PDF	-

Swipe to show more of the table

Related Articles

• Build Numbers and Versions of Veeam Backup & Replication
• Build Numbers and Versions of Veeam Backup for Nutanix AHV
• Build Numbers and Versions of Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization
• Build Numbers and Versions of Veeam ONE
• Build Numbers and Versions of Veeam Recovery Orchestrator
• Build Numbers and Versions of Veeam Service Provider Console
• Build Numbers and Versions of Veeam Agent for Microsoft Windows
• Build Numbers and Versions of Veeam Agent for Linux
• Build Numbers and Versions of Veeam Agent for Mac
• Build Numbers and Versions of Veeam Agent for IBM AIX
• Build Numbers and Versions of Veeam Agent for Oracle Solaris
• Build Numbers and Versions of Veeam Backup for Microsoft 365
• Build Numbers and Versions of Veeam Backup for AWS
• Build Numbers and Versions of Veeam Backup for Microsoft Azure
• Build Numbers and Versions of Veeam Backup for Google Cloud
• Build Numbers and Versions of Veeam Backup for Salesforce
• Veeam Data Cloud for Microsoft 365 Release Information and Build Numbers
• Veeam Data Cloud for Microsoft Azure Release Information and Build Numbers

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.

Error: "Cannot find the object on the mount host."

March 18, 2025, 5:00 pm

≫ Next: Build Numbers and Versions of Veeam Agent for Linux

≪ Previous: Build Numbers and Versions of Veeam Agent for Microsoft Windows

$

0

0

Error: "Cannot find the object on the mount host."

KB ID:	4722
Product:	Veeam Backup & Replication | 12.3.1
Published:	2025-03-19
Last Modified:	2025-03-19

Challenge

When attempting to perform a Guest Files restore from Veeam Backup Enterprise Manager, the restore fails with the error:

Cannot find the object on the mount host. Read KB4722 for more details.

Cause

This error occurs when the Guest OS partition that is being mounted is formatted with a filesystem or filesystem version that the mount Helper Host server cannot read.

For example, an Alma 9.4 Linux machine uses XFS driver version 6, but the Helper Host, which is used to mount the disks, runs Ubuntu 20.04.04 and only has XFS driver version 5. The version 5 XFS driver is incompatible with version 6, so the filesystem cannot be mounted.

Solution

As documented in the Preparing for File Search and Restore (non-Windows machines) section of the Veeam Backup Enterprise Manager user guide:

When you start guest OS file restore from Enterprise Manager, the helper host (or appliance) settings are obtained from the configuration database of the backup server. If no helper host or helper appliance configuration is found for the user account, Veeam Backup & Replication uses the configuration that was last selected at the Helper host step of the Guest File Restore wizard. Thus, before you start file-level restore from Enterprise Manager, make sure the settings are properly configured on the backup server. For details, see the Specify Helper Host section of the Veeam Backup & Replication User Guide.

Ensure that the Helper Host specified in Veeam Backup & Replication is fully compatible with the disks of the Linux machine that will be restored.

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

Build Numbers and Versions of Veeam Agent for Linux

March 18, 2025, 5:00 pm

≫ Next: Build Numbers and Versions of Veeam Agent for Mac

≪ Previous: Error: "Cannot find the object on the mount host."

$

0

0

Build Numbers and Versions of Veeam Agent for Linux

KB ID:	2681
Product:	Veeam Agent for Linux | 1.0 | 2.0.1 | 3.0 | 4.0 | 5.0 | 6.0 | 6.1 | 6.2 | 6.3 | 6.3.1
Published:	2022-09-22
Last Modified:	2025-03-19

This KB article lists all versions of Veeam Agent for Linux and their respective build numbers.

For more information on downloading the latest version of Veeam Agent for Linux, visit:

• Veeam Agent for Linux — Current Version Download Page
• Veeam Agent for Linux — What's New (Latest Version)

Version	Build Number	Release Date	Release Notes	Product Guides
Veeam Agent for Linux 6 Releases
Veeam Agent for Linux 6.3.1 included with Veeam Backup & Replication 12.3.1	6.3.1.1016	2025-03-19	HTML
Veeam Agent for Linux 6.3 included with Veeam Backup & Replication 12.3	6.3.0.73	2024-12-03	HTML
Veeam Agent for Linux 6.2 included with Veeam Backup & Replication 12.2	6.2.0.101	2024-08-28	HTML	ZIP
Veeam Agent for Linux 6.1.2 included with Veeam Backup & Replication 12.1.2	6.1.2.1781	2024-05-21	PDF	ZIP
Veeam Agent for Linux 6.1 included with Veeam Backup & Replication 12.1	6.1.0.1498	2023-12-05	—	ZIP
Veeam Agent for Linux 6.0.3 included with Veeam Backup & Replication 12 P20230718	6.0.3.1221	2023-07-20	PDF	ZIP
Veeam Agent for Linux 6.0.2 included with Veeam Backup & Replication 12 P20230412	6.0.2.1168	2023-04-13	PDF	ZIP
Veeam Agent for Linux 6.0 GA included with Veeam Backup & Replication 12 GA	6.0.0.1060	2023-02-14	PDF	ZIP
Veeam Agent for Linux 6.0 RTM included with Veeam Backup & Replication 12 RTM	6.0.0.1058	2023-01-30	—	—
Veeam Agent for Linux 5 Releases
Veeam Agent for Linux 5.0.2.4707 included with Veeam Backup & Replication 11a P20240304	5.0.2.4707	2024-03-07	( ! )This build was included within the Veeam Backup & Replication 11a P20240304 package. See KB4245	—
Veeam Agent for Linux 5.0.2 included with Veeam Backup & Replication 11a P20211211	5.0.2.4567	2021-12-22	PDF	—
Veeam Agent for Linux 5.0.1 GA included with Veeam Backup & Replication 11a GA	5.0.1.4493	2021-10-07	PDF	—
Veeam Agent for Linux 5.0.1 RTM included with Veeam Backup & Replication 11a RTM	5.0.1.4493	2021-09-24	—	—
Veeam Agent for Linux 5 GA included with Veeam Backup & Replication 11 GA	5.0.0.4318	2021-02-24	PDF	—
Veeam Agent for Linux 5 RTM included with Veeam Backup & Replication 11 RTM	5.0.0.4318	2021-02-11	—	—
Veeam Agent for Linux 4 Releases
Veeam Agent for Linux 4.0.1 included with Veeam Backup & Replication 10a GA	4.0.1.2365	2020-07-21	PDF	—
Veeam Agent for Linux 4.0 included with Veeam Backup & Replication 10 GA	4.0.0.1961	2020-02-18	PDF	—
Veeam Agent for Linux 3 Releases
Veeam Agent for Linux 3.0.2 included with Veeam Backup & Replication 9.5 U4b	3.0.2.1185	2019-07-16	PDF	—
Veeam Agent for Linux 3.0.1 included with Veeam Backup & Replication 9.5 U4a	3.0.1.1046	2019-03-26	PDF	—
Veeam Agent for Linux 3.0 included with Veeam Backup & Replication 9.5 U4	3.0.0.865	2019-01-22	PDF	—
Veeam Agent for Linux 2 Releases
Veeam Agent for Linux 2.0.1	2.0.1.665	2018-07-03	PDF	—
Veeam Agent for Linux 2.0	2.0.0.400	2017-12-19	—	—
Veeam Agent for Linux 1 Releases
Veeam Agent for Linux 1.0.1	1.0.1.364	2017-05-22	PDF	—
Veeam Agent for Linux 1.0	1.0.0.944	2016-12-13	—	—

Swipe to show more of the table

Related Articles

• Build Numbers and Versions of Veeam Backup & Replication
• Build Numbers and Versions of Veeam Backup for Nutanix AHV
• Build Numbers and Versions of Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization
• Build Numbers and Versions of Veeam ONE
• Build Numbers and Versions of Veeam Recovery Orchestrator
• Build Numbers and Versions of Veeam Service Provider Console
• Build Numbers and Versions of Veeam Agent for Microsoft Windows
• Build Numbers and Versions of Veeam Agent for Linux
• Build Numbers and Versions of Veeam Agent for Mac
• Build Numbers and Versions of Veeam Agent for IBM AIX
• Build Numbers and Versions of Veeam Agent for Oracle Solaris
• Build Numbers and Versions of Veeam Backup for Microsoft 365
• Build Numbers and Versions of Veeam Backup for AWS
• Build Numbers and Versions of Veeam Backup for Microsoft Azure
• Build Numbers and Versions of Veeam Backup for Google Cloud
• Build Numbers and Versions of Veeam Backup for Salesforce
• Veeam Data Cloud for Microsoft 365 Release Information and Build Numbers
• Veeam Data Cloud for Microsoft Azure Release Information and Build Numbers

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

Build Numbers and Versions of Veeam Agent for Mac

March 18, 2025, 5:00 pm

≫ Next: Build Numbers and Versions of Veeam Agent for IBM AIX

≪ Previous: Build Numbers and Versions of Veeam Agent for Linux

$

0

0

Build Numbers and Versions of Veeam Agent for Mac

KB ID:	4354
Product:	Veeam Agent for Mac | 1.0 | 2.0 | 2.1 | 2.2 | 2.3 | 2.3.1
Published:	2022-09-22
Last Modified:	2025-03-19

This KB article lists all versions of Veeam Agent for Mac and their respective build numbers.

For more information on downloading the latest version of Veeam Agent for Mac, visit:

• Veeam Agent for Mac — Current Version Download Page
• Veeam Agent for Mac — What's New (Current Version)

Version	Build Number	Release Date	Release Notes	Product Guides
Veeam Agent for Mac 2 Releases
Veeam Agent for Mac 2.3.1 included with Veeam Backup & Replication 12.3.1	2.3.1.1009	2025-03-19	HTML
Veeam Agent for Mac 2.3 included with Veeam Backup & Replication 12.3	2.3.0.65	2024-12-03	HTML
Veeam Agent for Mac 2.2 included with Veeam Backup & Replication 12.2	2.2.0.81	2024-08-28	HTML	ZIP
Veeam Agent for Mac 2.1.2 included with Veeam Backup & Replication 12.1.2	2.1.2.464	2024-05-21	PDF	ZIP
Veeam Agent for Mac 2.1 included with Veeam Backup & Replication 12.1	2.1.0.244	2023-12-05	—	ZIP
Veeam Agent for Mac 2.0.3 included with Veeam Backup & Replication 12 P20230718	2.0.3.904	2023-07-18	PDF	ZIP
Veeam Agent for Mac 2.0.2 included with Veeam Backup & Replication 12 P20230412	2.0.2.854	2023-04-13	PDF	ZIP
Veeam Agent for Mac 2.0 GA included with Veeam Backup & Replication 12 GA	2.0.0.750	2023-02-14	PDF	ZIP
Veeam Agent for Mac 2.0 RTM included with Veeam Backup & Replication 12 RTM	2.0.0.747	2023-01-30	—	—
Veeam Agent for Mac 1 Releases
Veeam Agent for Mac 1.0.1 included with Veeam Backup & Replication 11a GA	1.0.1.822	2021-10-07	PDF	—
Veeam Agent for Mac 1.0	1.0.0.713	2021-02-24	PDF	—

Swipe to show more of the table

Related Articles

• Build Numbers and Versions of Veeam Backup & Replication
• Build Numbers and Versions of Veeam Backup for Nutanix AHV
• Build Numbers and Versions of Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization
• Build Numbers and Versions of Veeam ONE
• Build Numbers and Versions of Veeam Recovery Orchestrator
• Build Numbers and Versions of Veeam Service Provider Console
• Build Numbers and Versions of Veeam Agent for Microsoft Windows
• Build Numbers and Versions of Veeam Agent for Linux
• Build Numbers and Versions of Veeam Agent for Mac
• Build Numbers and Versions of Veeam Agent for IBM AIX
• Build Numbers and Versions of Veeam Agent for Oracle Solaris
• Build Numbers and Versions of Veeam Backup for Microsoft 365
• Build Numbers and Versions of Veeam Backup for AWS
• Build Numbers and Versions of Veeam Backup for Microsoft Azure
• Build Numbers and Versions of Veeam Backup for Google Cloud
• Build Numbers and Versions of Veeam Backup for Salesforce
• Veeam Data Cloud for Microsoft 365 Release Information and Build Numbers
• Veeam Data Cloud for Microsoft Azure Release Information and Build Numbers

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

Build Numbers and Versions of Veeam Agent for IBM AIX

March 18, 2025, 5:00 pm

≫ Next: Build Numbers and Versions of Veeam Agent for Oracle Solaris

≪ Previous: Build Numbers and Versions of Veeam Agent for Mac

$

0

0

Build Numbers and Versions of Veeam Agent for IBM AIX

KB ID:	4355
Product:	Veeam Agent for IBM AIX | 1.0 | 2.0 | 3.0 | 4.0 | 4.1 | 4.5 | 4.6 | 4.6.1
Published:	2022-09-22
Last Modified:	2025-03-19

This KB article lists all versions of Veeam Agent for IBM AIX and their respective build numbers.

For more information on downloading the latest version of Veeam Agent for IBM AIX, visit:

• Veeam Agent for IBM AIX — Current Version Download Page
• Veeam Agent for IBM AIX — What's New (Current Version)

Version	Build Number	Release Date	Release Notes	Product Guides
Veeam Agent for IBM AIX 4 Releases
Veeam Agent for IBM AIX 4.6.1 included with Veeam Backup & Replication 12.3.1	4.6.1.1789	2025-03-19	HTML
Veeam Agent for IBM AIX 4.6 included with Veeam Backup & Replication 12.3	4.6.0.1772	2024-12-03	HTML
Veeam Agent for IBM AIX 4.5 included with Veeam Backup & Replication 12.2	4.5.0.1616	2024-08-28	HTML	ZIP
Veeam Agent for IBM AIX 4.1.1 included with Veeam Backup & Replication 12.1.2	4.1.1.1423	2024-05-21	PDF	ZIP
Veeam Agent for IBM AIX 4.1 included with Veeam Backup & Replication 12.1	4.1.0.1401	2023-12-05	—	ZIP
Veeam Agent for IBM AIX 4.0.1 included with Veeam Backup & Replication 12 P20230412	4.0.1.1173	2023-04-13	PDF	ZIP
Veeam Agent for IBM AIX 4.0 included with Veeam Backup & Replication 12 GA	4.0.0.891	2022-05-30	PDF	ZIP
Veeam Agent for IBM AIX 3 Releases
Veeam Agent for IBM AIX 3.0 included with Veeam Backup & Replication 11a GA	3.0.0.561	2021-10-07	PDF	—
Veeam Agent for IBM AIX 2 Releases
Veeam Agent for IBM AIX 2.0	2.0.0.256	2020-09-03	PDF	—
Veeam Agent for IBM AIX 1 Releases
Veeam Agent for IBM AIX 1.0	1.0.0.39	2018-09-20	PDF	—

Swipe to show more of the table

Related Articles

• Build Numbers and Versions of Veeam Backup & Replication
• Build Numbers and Versions of Veeam Backup for Nutanix AHV
• Build Numbers and Versions of Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization
• Build Numbers and Versions of Veeam ONE
• Build Numbers and Versions of Veeam Recovery Orchestrator
• Build Numbers and Versions of Veeam Service Provider Console
• Build Numbers and Versions of Veeam Agent for Microsoft Windows
• Build Numbers and Versions of Veeam Agent for Linux
• Build Numbers and Versions of Veeam Agent for Mac
• Build Numbers and Versions of Veeam Agent for IBM AIX
• Build Numbers and Versions of Veeam Agent for Oracle Solaris
• Build Numbers and Versions of Veeam Backup for Microsoft 365
• Build Numbers and Versions of Veeam Backup for AWS
• Build Numbers and Versions of Veeam Backup for Microsoft Azure
• Build Numbers and Versions of Veeam Backup for Google Cloud
• Build Numbers and Versions of Veeam Backup for Salesforce
• Veeam Data Cloud for Microsoft 365 Release Information and Build Numbers
• Veeam Data Cloud for Microsoft Azure Release Information and Build Numbers

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.