Operational Defect Database
BugZero found this defect 1208 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb4092
Release Information for Veeam Backup for Microsoft 365 5b
Last update date:
10/13/2021
Affected products:
Veeam Backup for Microsoft 365
Affected releases:
5.0
Fixed releases:
No fixed releases provided.
Description:
Requirements
Please confirm that you are running one of the following versions of Veeam Backup for Microsoft 365 before upgrading to 5b: 3.0 (build 3.0.0.422) 4.0 (build 4.0.0.1345) 4a (builds 4.0.0.1553, 4.0.0.1580) 4b (builds 4.0.0.2516, 4.0.0.2549) 4c (builds 4.0.1.519, 4.0.1.531, 4.0.1.545, 4.0.1.612, 4.0.1.625) 5.0 (builds 5.0.0.1061, 5.0.0.1063) 5a (build 5.0.0.1070) You can check this under Help and Support > About in the Veeam Backup for Microsoft 365 console. To upgrade from earlier versions, please contact our Customer Support. After upgrading, your build number will change to 5.0.1.179.
What’s New
Support to install on top of Veeam Backup & Replication v11 and Veeam Cloud Connect v11.
Enhancements
Guest users are automatically excluded from organization objects enumeration and backup. For backup jobs processing personal sites, email notifications on job results add a link to user’s backed up personal sites.
Resolved Issues
General Under certain conditions retention policy mistakenly cleans actual Exchange backup data from Jet-based repositories set with snapshot-based retention of less than 2 years. This issue applies to Veeam Backup for Microsoft Office versions 3.0 – 4c. Backup SharePoint and OneDrive backup may fail with “(500) Internal Server error” or “(400) Bad Request” error. Under certain conditions, Teams backup may fail with the “Object reference not set to an instance of an object” error. OneDrive backup may fail with the “Index (zero-based) must be greater than or equal to zero and less than the size of the argument list” error. SharePoint backup may fail with the following warning: “Failed to request item versions for list: %name% (list ID: %ID%). The operation has timed out”. SharePoint backup may fail with the “Invalid MIME content-length header encountered on read” error. Archive mailbox backup may fail with the “Failed to access archived message folder root. SOAP header Action was not understood” error. Restore Teams restore with an application and app certificate fails with the “Error in validating credentials: Account does not have a valid Microsoft Teams license”. OneDrive restores may fail with the “The attempted operation is prohibited because it exceeds the list view threshold enforced by the administrator" error. Under certain conditions, some of the site folders may not be displayed when browsing SharePoint or OneDrive for Business backups. RESTful API In the (GET) /v5/JobSessions/{jobSessionsId}/LogItems and (GET) /v5/JobSessions/{jobSessionsId}/LogItems/{logItemId} REST API calls responses, the “creationTime” and “endTime” values are provided in the backup server local time instead of the UTC.General. The “Last backup” parameter is displayed in the job sessions history while should be hidden from the job results.
More information
This update has been superseded by Veeam Backup for Microsoft 365 5d.
