- Veeam Support Knowledge Base
- Veeam Backup & Replication 10 Cumulative Patch 1
Veeam Backup & Replication 10 Cumulative Patch 1
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
This update has been superseded by Veeam Backup & Replication 10 Cumulative Patch 2.
More Recent Version Available
Please find the latest version of Veeam Backup & Replication here:
Requirements
Please confirm that you are running version 10 (build 10.0.0.4461) prior to installing this update. You can check this under Help | About in the Veeam Backup & Replication console. After upgrade, your build number will be 10.0.0.4461 P1.
Cloud Connect users:
This patch is not compatible with the Cloud Connect infrastructure based on the RTM build 10.0.0.4442. Please confirm with your service provider that they are using the GA build 10.0.0.4461 (any patch level) prior to upgrading!
Solution
Veeam Backup & Replication 10 Cumulative Patch 1 is a hotfix rollup that addresses the following issues reported by our customers on the original build of v10:
General
General
- Defragment and compact functionality performs multiple passes on the same full backup for backup jobs that do not use per-VM backup file chains.
- Querying WMI API class "Backup" fails with error code 0x80131500, which affects integration such as Veeam Service Provider Console (formerly Veeam Availability Console).
- Start-VBRInstantRecovery PowerShell cmdlet fails to process restore points created by Backup Copy jobs.
- VCSP rental license point weights were updated according to the March 1st 2020 changes.
- Copying NAS backups to secondary target erroneously consumes licenses (in addition to licenses consumed by the primary file backup job).
- Capacity Tier copy policy may erroneously upload full backups to object storage periodically when source backup chains do not have periodic fulls.
- Resetting CBT on Active Full backup fails if the database contains orphaned ESXi hosts.
- Deleting a vApp from vCloud Director backup may delete the entire backup if backup chain type was recently changed to per-VM backup.
- Hyper-V backup jobs fail the "Object reference not set to an instance of an object" error in environments where at least one virtual machine is stored in the SCVMM Library.
- Replica VMs disk space estimation logic may return incorrect value due to case sensitivity with virtual disk paths, resulting in some disks contributing to the total size twice.
- SureBackup jobs using advanced multi-host virtual labs fail with the "Invalid configuration for device " error.
- SureBackup log export functionality fails with the "Object was not found" error for SureBackup jobs that include an Application Group.
- Backup to Tape job skips processing synthetic full backups with forever forward incremental source backup chains on days when full backup file merge happens.
More Information
This update has been superseded by Veeam Backup & Replication 10 Cumulative Patch 2
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.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
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
Verify your email to continue your product download
We've sent a verification code to:
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
Start using Veeam:
Download the product
&
Activate the license key
Thank you!
Your feedback has been received and will be reviewed.