Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Veeam Backup for Microsoft 365 v2 cumulative patch KB2809.
Please confirm you are running Veeam Backup for Microsoft 365 version 2.0.0.567 or 2.0.0.594 (see KB2765 for more details) prior to installing this cumulative patch KB2809. You can check the product version under Help > About in the Veeam Backup for Microsoft 365 console. After upgrading, your build version will change to 2.0.0.814. As a result of ongoing R&D effort and in response to customer feedback, cumulative patch KB2809 delivers optimizations to SharePoint Online and OneDrive for Business interactions, and includes a set of bug fixes, the most significant of which are listed below: New Features Veeam Backup & Replication 9.5 Update 4 along with the corresponding Veeam Explorer for Microsoft Exchange, Veeam Explorer for Microsoft SharePoint compatibility support. Veeam Cloud Connect 9.5 Update 4 compatibility support. NOTE: Cumulative patch KB2809 is applicable to standalone installations of Veeam Backup for Microsoft 365 v2 and installations on top of Veeam Backup & Replication 9.5 Update 4 and Veeam Cloud Connect 9.5 Update 4. Cumulative patch KB2809 is NOT applicable to installations on top of Veeam Backup & Replication 9.5 Update 3 or 3a and Veeam Cloud Connect 9.5 Update 3 or 3a. Resolved Issues SharePoint Online and OneDrive for Business processing Slow backup processing which may finally be affected by throttling and may fail with the error 429. Backup of default system lists with versioning enabled may fail with the “Failed to request item versions for list: User Information List (list ID: {}). Access denied. You do not have permission to perform this action or access this resource” warning. Backup of an item with an attachment containing non-ASCII symbols in its file name may fail with the “File Not Found” error. Backup job runs for a long time with seemingly no progress and may fail with the “The underlying connection was closed” error. Backup of an item which content type is not defined (ContentTypeId is null) may fail on saving item’s version with the “JetError -1504, JET_errNullInvalid” error. Exchange Online processing Adding group mailboxes to on-premises Microsoft Exchange 2010 backup jobs may fail with the following error: “Exception occurred while executing a task. Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "GroupMailbox" could not be converted to type Microsoft.Exchange.Data.Directory.Recipient.RecipientTypeDetails.” . Restore A successfully backed up mailbox may not be visible during a restore session under certain conditions. SharePoint Online lists’ and libraries’ fields may not be restored for certain content types (i.e. “Comments” for “Document Sets”) SharePoint Online items with shared links may restore successfully, but the following error is shown upon completion in the restore session summary: “Object reference not set to an instance of an object on server. The object is associated with property File.” Adding Microsoft Exchange database manually to the Veeam Explorer for Microsoft Exchange scope may fail with the “Value does not fall within the expected range” error. Server Some restore points are not synced properly between a management server and a backup proxy after recreating/moving a corresponding repository.
To install the cumulative patch KB2809: Download VBO2.0-KB2809.msp. Execute VBO2.0-KB2809.msp as administrator on the Veeam Backup for Microsoft 365 server. Execute VeeamExplorerForExchange.msi as administrator on the on each machine where Veeam Explorer for Exchange is installed. Execute VeeamExplorerForSharePoint.msi as administrator on the on each machine where Veeam Explorer for SharePoint is installed. If there are any remote proxies in your environment please update those as described here. NOTE: Veeam Backup for Microsoft 365 RESTful API Service will not be started automatically after the update. Please start it manually to continue using REST API.