Veeam Backup for Microsoft 365 5b cumulative patch KB4158

General

• Backup data move job fails with the “Failed to allocate a managed memory buffer of 2147483647 bytes. The amount of available memory may be low” error.

Object storage repositories

• Moving backup data to an object storage repository may fail with the “Failed to complete the remote task because the connection with the server was lost” error.
• Retention type changes to item-level if a repository extended to object storage has been removed from Veeam Backup for Microsoft 365 console and then re-added back. This issue only affects repositories that were created with REST API or PowerShell, configured with the snapshot-based retention, and extended to object storage. For more details, see KB4176.
• Moving SharePoint backup data to an object storage repository may stall.

Backup

• Teams backup may fail with the “Resource does not exist” error.
• In hybrid organizations, resolving an Exchange Online mailbox may fail with the “Failed to synchronize item changes in folder. SOAP header Action was not understood” error.
• Backup job may fail to connect to an organization with “The remote server returned an error: (502) Bad Gateway” error received from Microsoft Graph.
• Backup job that includes multiple Teams objects may stall or run very slow.

Restore

• In Veeam Explorer for Microsoft Exchange, advanced search operation may fail with “The operation has timed out” error.
• Restoring a deleted Team may fail with the “Property classification has an invalid value” error.

RESTful API

• Saving a backed-up OneDrive account with REST API fails if the username contains the “|” character.
• Saving Teams posts as MSG files with REST API may fail if multiple such requests are running concurrently.
• Getting all items in a deleted list with the (GET) /v5/RestoreSessions/{restoreSessionId}/Organization/Sites/{siteId}/Items request fails with the “Object reference not set to an instance of an object” error.
• REST API calls may fail with “This request operation sent to net.tcp://127.0.0.1:9193/%EndpointName% did not receive a reply within the configured timeout (00:01:00)” error.

Reporting

• Generation of a Mailbox Protection report may fail with the “Object reference not set to an instance of an object” error if some of the mailboxes in the scope are missing the ExchangeGuid property.