BugZero found this defect 1194 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
2/16/2021
Veeam Backup for Microsoft 365
4.0
No fixed releases provided.
Please confirm you are running Veeam Backup for Microsoft 365 version 4c (builds 4.0.1.531, 4.0.1.545, 4.0.1.612) prior to installing this cumulative patch KB4099. You can check this under Help and Support > About in Veeam Backup for Microsoft 365 console. After upgrading, your build version will change to 4.0.1.625. Cumulative patch KB4099 addresses the data loss issue described in the KB4103 and includes a set of other fixes, the most significant of which are listed below:
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. For SharePoint backup, creation of the new 2021 repository database triggers full synchronization instead of incremental backup on the next backup job run. SharePoint and OneDrive backup may fail with “(500) Internal Server error” or “(400) Bad Request” error. Archive mailbox backup may fail with “Failed to access archived message folder root. SOAP header Action was not understood” error. SharePoint backup may fail with “Invalid MIME content-length header encountered on read” error. List items restore may fail with “Cannot find corresponding Content-Type for: %version%. Original ContentTypeID” error. Executing the Export-VEXItem cmdlet may fail with “Method not found” error.
To install the cumulative patch KB4099: Download VeeamBackupOffice365_4.0.1.625_KB4099.zip Execute VeeamBackupOffice365_4.0.1.625_KB4099.msp as administrator on the Veeam Backup for Microsoft 365 server. Execute VeeamExplorerForExchange_4.0.1.625_KB4099.msp as administrator on each machine where Veeam Explorer for Microsoft Exchange is installed. Execute VeeamExplorerForSharePoint_4.0.1.625_KB4099.msp as administrator on each machine where Veeam Explorer for Microsoft SharePoint is installed. If there are any remote proxies in your environment, please update those as described here.