https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2I0MTI2IiwiaGFzaCI6ImJhZWE1Y2QwLWE1Y2QtNDZiMS05OWQ2LWVjMWM1ODJhNDIzZSJ9
1-800-691-1991 | 9am - 8pm ET
EN

Release Notes for Veeam Backup & Replication 11 Cumulative Patches

KB ID: 4126
Product: Veeam Backup & Replication 11
Published: 2021-03-11
Last Modified: 2021-04-12

Requirements

Please confirm that you are running V11 GA (build 11.0.0.837) of any earlier patch level prior to installing this update. You can check this under Help | About in the backup console. After upgrade, your build number will be 11.0.0.837 P20210401.

Resolved Issues

This cumulative patch includes hotfixes for the following issues of the original V11 GA build:

P20210401

  • Following the upgrade to V11, the retention policy may erroneously delete some of the monthly GFS backups before their retention expires. The issue only affects Backup Copy jobs which have their latest full backup corrupted.

P20210324

  • Applicable to Cloud Connect service providers' infrastructure servers only: fix for the quartertly backups retention issue.

P20210319

  • Backup jobs appear to hang at 0KB on the hard disk reading step due to a race condition that may trigger on a very slow backup storage (usually when Windows deduplication is enabled). Potentially, any process that interacts with a backup file may hang when trying to open a backup file.
  • After upgrading to V11 directly from version 9.5, incremental backup and replication runs take longer and produce larger increments than with previous versions for host-based processing of vSphere and Hyper-V VMs.
  • Possible data loss with IBM storage snapshot integration due to a wrong LUN deleted during storage snapshot retention processing. This is caused by certain sequence of storage snapshot management operations outside Veeam resulting in a LUN with duplicate internal ID appearing on the storage.
  • Veeam.Backup.Service.exe may crash under heavy load if the Snapshot Hunter processing runs into an unexpected issue with the stuck snapshot processing.
  • When the scale-out backup repository Capacity Tier uses only the Copy policy, GFS backups will now be made immutable in hardened repository extents of the Performance Tier for the entire duration of their retention policy. Previously, GFS backups were only locked according to the hardened repository immutability settings to enable the Move policy to function correctly even when it was not enabled, making SOBR as a whole not compliant with certain WORM storage regulations.

Solution

If you have V11 GA build installed already, you can apply Cumulative Patch 20210401 using the following update package:
MD5: 619e10805a074b93d602c1c929e15146
SHA-1: 12e89df010d789521d56c77c4e36823f8ee0a861
For new installations and upgrades from the previous versions, use the V11 ISO version 20210401:
MD5: 0c12b5b062e70b8f178be559dc230232
SHA-1: cb8cb3d1064d20df9903408b54c26fb7e9ab0169
Reboot may be required

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

Please plan accordingly.

KB ID: 4126
Product: Veeam Backup & Replication 11
Published: 2021-03-11
Last Modified: 2021-04-12

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.