CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
NONE
Availability Impact
NONE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
AI Score
Confidence
High
This update has been superseded by Veeam Backup & Replication 12.1.
You can check the installed build number in the Veeam Backup & Replication Console’s Main Menu (≡) underHelp > About.
This article has two download links:
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.
For Cloud Connect Service Providers updating CDP infrastructure, it's recommended to disable all tenant accounts before running the I/O Filter upgrade. Otherwise, a backup service restart will be required afterward.
This update fixes over 160 issues reported by early V12 adopters, the most significant of which are documented below:
Application plug-ins
Restoring databases from backups created with Veeam Plug-in for Microsoft SQL Server fails with the error:
Source and target database versions do not match
Veeam Plug-in for Microsoft SQL Server fails to display restore points on SQL Server installations with certain regional settings.
Veeam Plug-in for Microsoft SQL Server fails to connect to an instance running on a failover cluster with the error:
Failed to create ODBC connection
Backup
Backup Copy
CDP
NAS Backup
Setting immutability flags on backup objects takes a long time due to the absence of multi-threading.
Despite no actual hash collisions present in backup data, NAS backup jobs may incorrectly fail with the error:
MD5 collision found
If a previously protected file or folder is removed from processing, NAS backup jobs targeting an object storage repository fail with the error:
Unable to find cache settings for server
NAS backup jobs targeting an EMC Data Domain repository take a long time to finish.
Restore
Direct restore to Microsoft Azure may fail with one of the following errors:
Unable to resize the VM since changing from resource disk to non-resource disk VM size is not allowed
or
Cannot create a VM because this VM size only supports a CPU Architecture of 'Arm64', but an image or disk with CPU Architecture 'x64' was given
Object Storage
Scale-out Backup Repository
Initiating a restore from the Capacity Tier sub-node of the Backups node of the management tree may fail with the following errors:
This operation takes longer than expected
or
Timeout during reading attempt
Removing backups from a Capacity Tier may take an extremely long time due to the unintentional loss of multi-threading in the object deletion process.
Capacity Tier offload takes longer due to a lack of optimizations in checkpoint management operations (enumeration and removal) which are used much more extensively with the new object storage backup format in version 12.
Upgrading backups stored in a Capacity Tier may fail with the following error:
Capacity Tier storage index is out of sync
Tiering jobs to a SOBR Archive Tier may fail with the error:
The wait operation timed out
Storage Snapshot Integration
Cloud Connect
Provider-side Network Extension Appliance with a static IP address assigned loses connectivity.
Despite sufficient disk space in the cloud repository, Veeam Agent for Microsoft Windows fails to perform the backup chain transformation operation with the error:
Backup repository quota has been exceeded
Update: vSphere 8.0 U1 is officially supported withP20230412
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
Backup copy jobs with HPE Catalyst Copy enabled fail with the error:
A key with the same value has already been added
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
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
Storage Snapshot Integration
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
This update has been superseded by Veeam Backup & Replication 12.1.
If at least version 12 GA (build 12.0.0.1420) is already installed, download and run the following patch on the Veeam Backup Server to**update **to the latest Cumulative Patch:
**Filename:**VeeamBackup&Replication_12.0.0.1420_20230718.zip
MD5:1A89F6CD6E4D64F546E773548FA0FD63
SHA1:B08F58A9A2E51BCE2C5F7876C57B4E33AADEB9B0
Note: Before initiating the update, please ensure that there is at least twice the size of the patch_ (excluding the size of the patch itself) _available on disk. During the installation of the cumulative patch, the contents of the patch file are decompressed to a temporary folder. Additionally, as a precautionary measure to facilitate a seamless rollback in case of a failed installation, each original file that would be replaced is copied to a temporary location.
The cumulative patch update executable listed in this article requires, at a minimum, the GA release of Veeam Backup & Replication 12. Any Veeam Backup Server / Veeam Cloud Connect server still running Veeam Backup & Replication 12 RTM mustfirst be updated to GA using the patch on KB4415 before the cumulative patch can be applied.
Vendor | Product | Version | CPE |
---|---|---|---|
veeam | veeam_backup_\&_replication | 12 | cpe:2.3:a:veeam:veeam_backup_\&_replication:12:*:*:*:*:*:*:* |
veeam | veeam_backup_for_google_cloud | 12 | cpe:2.3:a:veeam:veeam_backup_for_google_cloud:12:*:*:*:*:*:*:* |