Veeam backup and replication 11
may crash under heavy load if the Snapshot Hunter processing runs into an unexpected issue with the stuck snapshot processing.This is caused by certain sequence of storage snapshot management operations outside Veeam resulting in a LUN with duplicate internal ID appearing on the storage. Possible data loss with IBM storage snapshot integration due to a wrong LUN deleted during storage snapshot retention processing.After upgrading to V11 directly from version 9.5, incremental backup and replication runs take longer and produce larger increments than with previous versions for host-based processing of vSphere and Hyper-V VMs.Potentially, any process that interacts with a backup file may hang when trying to open a backup file. Backup jobs appear to hang at 0KB on the hard disk reading step due to a race condition that may trigger on a very slow backup storage (usually when Windows deduplication is enabled).Applicable to Cloud Connect service providers’ infrastructure servers only: fix for the quartertly backups retention issue.
#Veeam backup and replication 11 update#
There are 2 known issues with vSphere 7.0 Update 2, CDP and HotAdd on Linux Proxy. This is version 11.0.0.837, also known as patch P20210324, this also conatins P20210319, still no support for vSphere 7.0 Update 2, this will be in the next cumulative patch. Veeam has released Backup & Replication 11 Cumulative Patche 11.0.0.837_20210324, Availability Orchestrator 4.0 and Service Provider Console v5 Patch 2.