Veeam Backup & Repliation 10 Cumulative Patch 2 released

Veeam has released Cumulative Patch 2, that gives support for vSphere 7, and also have som fixes included.

Fixes included:

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) are 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.

See the Veeam KB here.