#1 Global Leader in Data Protection & Ransomware Recovery

Release notes for Veeam Backup & Replication 10a Cumulative Patch P20210609

KB ID: 4180
Product: Veeam Backup & Replication | 10
Published: 2021-06-10
Last Modified: 2022-03-23
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

This 10a release may only upgrade to 11a or higher.

The build of Veeam Backup & Replication 10a P20210609 listed in this article is only compatible with upgrading to Veeam Backup & Replication 11a (11.0.1.1261) or higher.

Any attempt to upgrade to v11 (11.0.0.837) will fail.

Requirements

Please confirm that you are running version 10a (build 10.0.1.4854) before installing this update. You can check this under Help | About in the Veeam Backup & Replication console. After the upgrade, your build number will be 10.0.1.4854 P20210609.

Veeam Cloud Connect tenants: ensure that your service provider uses version 11 P20210507 or later for their Cloud Connect infrastructure before deploying this patch.

Veeam Cloud Connect service providers: this patch cannot be deployed on the Cloud Connect infrastructure servers running version 10a. Please upgrade directly to version 11 instead.

New Features

  • Various product functionality should no longer incorrectly detect Windows 10 21H1 and Windows Server 2022 versions or refuse to work with them. Instead, it will attempt to process them using the existing logic created for previous OS versions. This change does not constitute the official support of these platforms, which is planned for version 11a.

Resolved Issues

  • Backported Microsoft .NET remoting changes from V11 to address a vulnerability (CVE-2021-35971) in the deserialization logic. Veeam would like to thank Markus Wulftange from Code White for reporting the vulnerability and for his collaboration with the mitigation.
  • Object storage: following an extended backup server downtime the retention policy stops cleaning up checkpoints as their immutability period expire; object storage certificate validation does not include a check of whether the certificate belongs to the specified S3 endpoint; changed the blocking “bucket has object versioning enabled” error to a warning to enable registering Backblaze B2 object storage buckets.
  • NAS backup: Improved performance of file share backup jobs when using file proxy servers with a large number of cores.

Known Issues

  • File level recovery on a remote backup console fails with the “Object of type cannot be converted” error. To work around the issue, please install the patch on all remote consoles manually.

Solution

This update has been superseded by Veeam Backup & Replication 10a Cumulative Patch P20220304.
More Recent Version Available

Please find the latest version of Veeam Backup & Replication here:

https://www.veeam.com/backup-replication-vcp-download.html

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.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.