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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IzMTYxIiwiaGFzaCI6IjM5NWU5YmM2LTA4NmQtNGRhOS1hYjJlLTgyYjNjZTEyODViMyJ9
1-800-691-1991 | 9am - 8pm ET
EN

Veeam Backup & Replication 10 Cumulative Patch 2

Challenge

Release notes for Veeam Backup & Replication 10 Cumulative Patch 2.

Cause

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
  • 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.
Amazon AWS
  • Added support for Cape Town and Milan data center regions in all related functionality.
Backup Copy
  • 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.
Backup from Storage Snapshots
  • Under certain circumstances, backup jobs may fail with the “Cannot retrieve physical extents for connecting iSCSI target IQN {0} on proxy IQN {1}” error.
Cloud Connect Infrastructure
  • 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.
Configuration Database
  • High CPU consumption on the SQL Server hosting the configuration database caused by the AggregateSqlPointsInfo stored procedure during transaction log backup.
File Level Recovery
  • 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.
NAS Backup
  • 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
  • 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.
User Interface
  • 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.
Veeam Service Provider Console 
  • Invalid tenant workloads count is returned by the backup server’s WMI API, resulting in Veeam Service Provider Console to issue false warnings.
WAN Acceleration
  • WAN accelerator may deadlock while transferring an increment with large contiguous set of zeroed segments, making the data transfer appear to slow down dramatically.
This patch also includes all hotfixes from the Cumulative Patch 1 and supersedes it.

More information

If you have v10 installed (GA build 10.0.0.4461), you can apply Cumulative Patch 2 using the following update package:

DOWNLOAD PATCH


MD5: 79ae1105e38df9c14907284db6590565
SHA-1: 06db5b97330726d1386ba5e68e7dc2ea13c603de

For new installations and upgrades from the previous versions, use the updated v10 ISO image version 20200527, which has the Cumulative Patch 2 included:

DOWNLOAD ISO


MD5: eb71118b8ac6b05b9cb02dc0a4279f44
SHA-1: 63911a2d143af78e483c5decc2eff212ceae00bb
 
KB ID:
3161
Product:
Veeam Backup & Replication
Version:
10.0.0.4461
Published:
2020-05-27
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later