- Veeam Support Knowledge Base
- Veeam Backup & Replication 10 Cumulative Patch 2
Veeam Backup & Replication 10 Cumulative Patch 2
Get weekly article updates
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
Oops! Something went wrong.
Please, try again later.
This update has been superseded by Veeam Backup & Replication 10a.
More Recent Version Available
Please find the latest version of Veeam Backup & Replication here:
Requirements
Please confirm that you are running the GA build of version 10 (build 10.0.0.4461 or 10.0.0.4461 P1) 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 P2.
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 2 adds the official VMware vSphere 7 support and includes hotfixes for the following issues reported by our customers on the original build of v10:
Agent Management
Agent Management
- Managed by Agent backup policies do not respect the retention policy setting for Microsoft Windows machines, always forcing it to 7 regardless of the value specified.
- Added support for Cape Town and Milan data center regions in all related functionality.
- Failed GFS full backup transform may result in the job to start failing with the “Failed to process method {Transform.Patch}: There is an item with the specified name and another type” error.
- Under certain circumstances, backup jobs may fail with the “Cannot retrieve physical extents for connecting iSCSI target IQN {0} on proxy IQN {1}” error.
- In the environments where the Network Extension Appliance has the same name as the corresponding Tenant, deleting the appliance will also remove tenant’s replicas.
- Under certain circumstances, task slots may not be released at the end of the job session, resulting in various issues due to lack of available task slots.
- Cloud Connect Replication fails with the “Cannot find an available target” error in vCloud Director environments with multiple clusters due to not searching all available vDC pools for the required vOrg pool.
- Using the UseCachedSshConnections registry value may result in jobs to stop running due to already closed connection erroneously cached. This issue may result in various errors, typically “The session is not open” error.
- Opening the Tenants view takes a long time.
- High CPU consumption on the SQL Server hosting the configuration database caused by the AggregateSqlPointsInfo stored procedure during transaction log backup.
- Mounting a restore point with the dynamic disk fails with the “Invalid secondary GPT partition entry array checksum” error.
- In some environments, mounting a restore point for file-level recovery may fail with the “Invalid secondary GPT header signature” error.
- VSS snapshot fails to be created with the “Access is denied” error for SMB file shares hosted on some NAS devices due to lack of impersonation.
- Backup of different files shares from the same server or NAS may fail with the “Failed to create a VSS snapshot” whenever VSS snapshot creation calls overlap.
- Resource scheduler may experience significant delays issuing the backup infrastructure resources in environments with a large number of agent-based, application plug-in based or host-based backups (with per-VM backup file chains disabled) stored in a scale-out backup repository.
- High backup server CPU consumption by the Veeam Backup Service in large environments while the user interface is open and no jobs are active.
- High backup server RAM consumption by the UI Service process and slow performance of historical sessions view in environments with very large number of sessions.
- Opening an existing VMware backup job’s settings takes a long time for jobs using a scale-out backup repository with a large number of extents as the target.
- Invalid tenant workloads count is returned by the backup server’s WMI API, resulting in Veeam Service Provider Console to issue false warnings.
- WAN accelerator may deadlock while transferring an increment with large contiguous set of zeroed segments, making the data transfer appear to slow down dramatically.
More Information
This update has been superseded by Veeam Backup & Replication 10a.
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.
Oops! Something went wrong.
Please, try again later.