Release Information for Veeam Backup & Replication 12 Cumulative Patches

You can check the installed build number in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.

This article has two download links:

• Patch — Use this if you are running at least Veeam Backup & Replication 12 GA (build 12.0.0.1420). After updating, the build number will be 12.0.0.1420 P20230412.
• ISO — Use this if you are running any Veeam Backup & Replication version between 10a (10.0.1.4854) and 11a (11.0.1.1261 P20230227), to upgrade to version 12 P20230412. Remember to review the Upgrade Checklist as part of your upgrade process.
  

Below are details about the Cumulative Patches that have been released for Veeam Backup & Replication 12.

Each subsequent Cumulative Patch also includes all fixes present in the previous Cumulative Patches.

P20230412

Enhancements

• P20230412 adds VMware vSphere 8.0 U1 readiness based on the pre-release build. The official support will require full regression testing of the GA build when it becomes available. This article will be updated with a support statement afterward.
  
  Update: vSphere 8.0 U1 is officially supported with P20230412

Resolved Issues

General

• Backup and restore tasks using a repository with Automatic gateway selection mode remain in the “Resource not ready: gateway server” stage for a long time if one or more gateway servers are unavailable.
  
• OpenSSL Library updated to the newest version (1.0.2zg).
• The synthetic full backup file creation for an extremely long backup chain on an ReFS-based repository fails with the following error :

  A file system block being referenced has already reached the maximum reference count
  

• The support logs export task fails with the error:

  Destination path too long
  

Agent Management

• Windows cluster backup jobs with the deduplication option disabled fail with the error:

  Failed to clone clustered disks
  

Backup Copy

• Storage-level corruption guard scans of per-machine backups of legacy Backup Copy jobs stored in a scale-out repository fail with the  error:

  Cannot find previous full backup to calculate incremental backups estimate
  

• Legacy Backup Copy job targeting a cloud repository start failing with the following error if the previous processing interval was interrupted:

  Sequence contains more than one element
  

Cloud Connect

• Upgrading metadata of backup chains stored in a cloud repository fails with the following error if the service provider has the EncryptedTenantBackupsOnly option enabled:

  Unable to backup to cloud repository: your service provider accepts encrypted backups only
  

• Backup Copy jobs to a cloud repository fail with the following error if backup encryption is enabled and the service provider has the EncryptedTenantBackupsOnly option enabled:

  Unable to backup to cloud repository: your service provider accepts encrypted backups only
  

Cloud Director

• SQL Server transaction log backup fails with the following error if network-less application-aware processing is used (via VIX):

  The object has already been deleted or has not been completely created
  

• Used space information resets for all Self-Service Portal tenants after the backup chain metadata upgrade.

CDP

• The CDP policies ignore preferred network settings.

NAS Backup

• NAS backup job fails to apply the retention policy with the error:

  Run retention on extent
  

Object Storage

• Poor retention policy processing and backup deletion performance due to the loss of multi-threading in the backup removal process.
• Capacity Tier offload fails with the following errors due to a lack of full S3 protocol compatibility on some S3-compatible object storage systems:

  Impossible to start a new log because there are other logs
  

  or

  Invalid log sequence
  

  or

  S3 error: Access Denied
  

• Upgrading the metadata of backup chains with immutable copies stored in the Capacity Tier takes an extremely long time.

Storage Integration

• Backup copy jobs with HPE Catalyst Copy enabled fail with the error:

  A key with the same value has already been added
  

• Rescanning system volumes on DataONTAP-based storage fails on certain MetroCluster configurations (such as ones with inactive SVM present).
• Snapshotting IBM compressed volumes located in the primary storage pool fails with the error:

  Some parameters are mutually exclusive
  

SureBackup

• SureBackup job fails with the following error if Virtual Lab has 2 or more IPv4 virtual NICs:

  Failed to start virtual lab proxy appliance VM. Proxy appliance VM network initialization failed. Check proxy appliance IP settings
  

Tape

• Ejecting a tape from a standalone drive fails with the error:

  Automated library not found
  

• Under certain circumstances, tape jobs may fail with the error:

  Stopped by job
  

• File to Tape job mistakenly consumes a license when processing backups created by Veeam Backup for Microsoft 365.

UI

• Enterprise Manager multiple daily email notification improvements: added missing information, fixed incorrect job status and duration issues.
• In some cases, after migrating the Veeam Backup & Replication configuration database from Microsoft SQL to PostgreSQL, the Backups > Disk section may appear empty or take an unusually long time to load.
• Opening the Veeam Backup & Replication Console displays the following error when the configuration database contains certain tape backups:

  Object reference not set to an instance of an object
  

P20230223

Resolved Issues

• Vulnerability (CVE-2023-27532) in Veeam Backup Service was fixed.
  This vulnerability was reported by Shanigen.