Release Information for Veeam Backup & Replication 11a Cumulative Patches

Before installing this Cumulative Patch using the Patch Installer, please confirm that you are running Veeam Backup & Replication 11a (build 11.0.1.1261) with or without earlier patches. You can check the build number under Help | About in the backup console. After the upgrade, your build number will be 11.0.1.1261 P20220302.

If you are running any Veeam Backup & Replication version between 9.5 U4b (9.5.4.2866) and 11 (11.0.0.837 P20210525), you must use the ISO below to upgrade to version 11a P20220302.

P20220302

• Vulnerabilities (CVE-2022-26500, CVE-2022-26501) in Veeam Distribution Service were fixed.
  These vulnerabilities were reported by Nikita Petrov (Positive Technologies).
  
• Vulnerability (CVE-2022-26504) in Veeam.Backup.PSManager was fixed.
• Vulnerability (CVE-2022-26503) in Veeam Agent for Microsoft Windows was fixed.
  This vulnerability was reported by Nikita Petrov (Positive Technologies).

P20211211

• Microsoft Windows 11 and Microsoft Windows 10 21H2 support as guest OS, Hyper-V hosts (as a target for Instant Recovery and SureBackup), for installation of Veeam Backup & Replication components, and for agent-based backup with Veeam Agent for Microsoft Windows 5.0.2 (included in P20211211).
• RHEL/CentOS/Oracle Linux 8.5, Ubuntu 21.10, Fedora 35 distributions are now supported as the guest OS for the installation of Veeam Backup & Replication components and for agent-based backup with Veeam Agent for Linux 5.0.2 (included in  P20211211). The latter also supports Linux kernel up to version 5.16 and no longer requires installing the linux-image-<version>-dbg package on Debian 11.
• Oracle Database 21c support by application-aware processing of image-level backup including redo log backup, by Veeam Plug-in for Oracle RMAN 11.0.101.1264 (included in P20211211) and by Veeam Explorer for Oracle.
• RHEL 8.4 for SAP Solutions and SLES 15 SP3 for SAP Applications support by Veeam Plug-in for SAP HANA.
• VMware Carbon Black compatibility for vSphere VMs processing.
• LTO-9 support. Tape jobs will now identify and display the media calibration process in the Action log and will no longer time out should this process takes longer than 15 minutes.
• Platform: added API extensions enabling Kasten K10 integration and configuration backup/restore for upcoming versions of Veeam Backup for AWS/Azure/GCP; deleting cloud-native backup appliance will no longer delete the corresponding external repositories to facilitate configuration backup restore.
• SOBR Capacity Tier: increased timeout for certain long-running object storage operations (like clean up) to 25 hours; fixed the root causes behind offload failures with “Block not found”, “The INSERT statement conflicted with the FOREIGN KEY constraint” and “No recovery record was found for storage key” errors.
• Tape: fixed NDMP performance regression introduced in 11a; added support for Kasten K10 backups and backup copies to Backup to Tape jobs as well as support for restoring such backups from tape.
• Microsoft Azure: region settings have been moved into the configuration file to allow for enabling Archive Tier functionality there as Microsoft rolls out the Archive Storage class to additional regions.
• Microsoft Hyper-V: the presence of an empty SCVMM tag should no longer cause various issues in the related functionality; VMs from nested HostGroups should no longer be skipped from processing; application-aware processing failures on VMs with a very large number of network adapters.
• VMware Cloud Director: the new plug-in version 11.1.7 adds support for: deployment with a very large number of organizations; LDAP-integrated users with multiple roles; installation side by side with other data protection plug-ins; browsers with the locale set to a language not present in the language picker.
• Veeam Cloud Connect: evacuating backups of a particular tenant should no longer lock the entire SOBR extent preventing other tenants from accessing their backups; encrypted tenant backups should now be correctly unpublished following the restore from Archive Tier; tenants should again be presented with a choice of keeping or removing their replicas when removing cloud hosts.