Operational Defect Database
BugZero found this defect 1153 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb4135
Veeam Backup for Microsoft 365 5b cumulative patch KB4135
Last update date:
5/31/2021
Affected products:
Veeam Backup for Microsoft 365
Affected releases:
5.0
Fixed releases:
No fixed releases provided.
Description:
Requirements
Please confirm you are running Veeam Backup for Microsoft 365 build 5.0.1.179 or 5.0.1.207 prior to installing this cumulative patch KB4135. You can check this under Help and Support > About in Veeam Backup for Microsoft 365 console. After upgrading, your build version will change to 5.0.1.225. As a result of on-going R&D effort and in response to customer feedback, cumulative patch KB4135 provides a set of enhancements and bug fixes, the most significant of which are listed below:
Enhancements
Optimized operations for faster execution of the (GET) /v5/Organizations REST API request. Optimized operations for faster execution of the Get-VBOEntityData PowerShell cmdlet. Optimized operations for faster execution of the following REST API requests in infrastructures where some of the remote proxies are offline: o (GET) /v5/BackupRepositories/{backupRepoId}/backedupOrganizations o (GET) /v5/BackupRepositories/{backupRepoId}/OrganizationData o (GET) /v5/BackupRepositories/{backupRepoId}/UserData o (GET) /v5/Organizations/{organizationId}/usedRepositories o (GET) /v5/Reports/action for generating a Mailbox Protection report Ability to quickly get basic properties of backup proxies, including offline remote proxies, via REST API and PowerShell: o using the “extendedView = false” with the (GET) /v5/Proxies or (GET) /v5/Proxies/{proxyId} requests o using the “ExtendedView” parameter with the Get-VBOProxy cmdlet.
Resolved Issues
General Adding a new backup repository via the UI may fail with “The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error”. Under certain conditions after upgrading to cumulative patch KB4124 (build 5.0.1.207), a Workgroup proxy becomes offline and unavailable. Adding an Office 365 organization that belongs to the China region may fail with “Invalid filter clause” error. Object storage repositories Synchronization of a repository extended to object storage may fail with “Sequence contains no elements” error. Synchronization of a repository extended to object storage may fail with “Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)” error. Upgrading a repository extended to object storage may fail with “JetError -1605, JET_errKeyDuplicate, Illegal duplicate key error”. Backup SharePoint sites are skipped from processing if both Microsoft Teams and SharePoint site objects are explicitly added to the backup job. When multiple backup jobs are running simultaneously, some of them may hang in the “Operation pending” or “Connecting to organization” state. Restore Under certain conditions, SharePoint library restore may fail with “The collection has not been initialized. It has not been requested or the request has not been executed” error. In BaaS scenarios, restore sessions initiated on the tenant side continue to be displayed as active in Veeam Backup for Microsoft 365 console after the tenant machine has been turned off. Restore of a SharePoint list with a multilevel folder hierarchy may fail with the timeout error. When exploring standalone backup databases in Veeam Explorer for Microsoft Exchange, some mailbox folders may not be displayed. Exchange restore using Basic authentication can be initiated with an empty password field. Reporting Generation of the Mailbox Protection report may fail with “Object reference not set to an instance of an object” error.
Solution
To install the cumulative patch KB4135: Make sure all backup jobs are stopped and disabled. Download VeeamBackupOffice365_5.0.1.225_KB4135.zip. Execute VeeamBackupOffice365_5.0.1.225_KB4135.msp as administrator on the Veeam Backup for Microsoft 365 server. Execute VeeamExplorerForExchange_5.0.1.225_KB4135.msp as administrator on each machine where Veeam Explorer for Microsoft Exchange is installed. Execute VeeamExplorerForSharePoint_5.0.1.225_KB4135.msp as administrator on each machine where Veeam Explorer for Microsoft SharePoint is installed. Execute VeeamExplorerForTeams_5.0.1.225_KB4135.msp as administrator on each machine where Veeam Explorer for Microsoft Teams is installed. If there are any remote proxies in your environment, please update those as described here. Enable all jobs back.
