Veeam Backup for Microsoft Office 365 4c cumulative patch KB4083

Please confirm you are running Veeam Backup for Microsoft Office 365 builds 4.0.1.531 or 4.0.1.545 prior to installing this cumulative patch KB4083. You can check this under Help and Support > About in Veeam Backup for Microsoft Office 365 console. After upgrading, your build version will change to 4.0.1.612.

As a result of on-going R&D effort and in response to customer feedback, cumulative patch KB4083 provides a set of enhancements and bug fixes, the most significant of which are listed below.

• Faster browsing of SharePoint backups achieved by optimized enumeration of restore points in Veeam Explorer for Microsoft SharePoint.
• Faster start of Exchange restore session initiated with RESTful API.

• Faster listing of backed up OneDrive for Business accounts with the (GET) v4/RestoreSessions/{restoreSessionId}/Organization/OneDrives resource.

• Faster mailbox export to PST with Veeam Explorer for Microsoft Exchange.
• Faster response from the Get-VBOJob cmdlet.

General

• Loading backup jobs history in the product GUI may take a long time in larger environments.
• SMTP report for a backup job displays %OrgName% variable blank if the job fails to establish a connection to Office 365.
• Memory leaks occur on a proxy when multiple restore sessions are opened simultaneously.
• Applying retention policy may fail with the “JET_errOutOfCursors, Out of table cursors” error.
• Proxy stops responding to the backup server calls when VSS timeout occurs.
• Under certain conditions, a scheduled periodic backup job does not start as expected due to the time reference to UTC.
• In the console, backup job history may display incorrect proxy.

Backup

• Backup job does not start until retention cleanup is completed on the corresponding target repository.
• When using modern app-only authentication, backing up a mailbox with an ampersand (&) in its name fails.
• Public folder mailbox backup fails with the “Mailbox must be accessed as owner” error. For more details on this issue, see KB4033.
• Public folder mailbox backup fails with the “Too many concurrent connections" error.
• On incremental backup job runs, new mailbox items may be skipped from processing.
• SharePoint site backup may fail with the “File not found in the database” error if some of the site folders have attachments.
• SharePoint site backup may fail with the “Object reference not set to an instance of an object” error if a version of an item in this site has been changed during the backup.
• SharePoint site backup may fail with the “Failed to backup list: File not found in the database” error if any of the site attachments have been changed during the backup.
• SharePoint site backup to an Azure Blob repository may fail with the “Stream Was too Long” error.
• SharePoint site backup may fail with the “Connection is not established” error.
• SharePoint site backup may fail with the “Failed to request web part manager for file %path%. (Exception User cannot be found.)” error.
• SharePoint site backup may fail with the “The file is not checked out. You must first check out this document before making changes” error.
• SharePoint backup may fail with the “File %name% version %number% has already been committed” error after moving the site backup data to an object storage repository and re-targeting a backup job containing this site to this repository.
• Backup of a personal site may fail with the “Access to this Web site has been blocked. Please contact the administrator to resolve this problem” error, if the user has been deleted in Office 365.
• Backup of a SharePoint site with several thousands of lists fails with the timeout error.

Data management

• SharePoint site migration to an object storage repository may fail with the “An item with the same key has already been added” error.
• Under certain conditions, during backup data move between repositories multiple “Unable to find deleted item in repository” errors occur.
• Backup data move from a local to an object storage repository fails with the “The maximum number of Exchange items per batch (65534) has been exceeded” error.
• OneDrive backup data move between repositories may fail with the “Failed to move OneDrive %name% . Connection is not established” error.
• SharePoint and OneDrive backup data move between repositories may fail with the “Failed to allocate a managed memory buffer of %number% bytes. The amount of available memory may be low”.

Restore

• SharePoint list restore fails with the “Field or property "ContentTypeId" does not exist” error if this list contains more than 5000 items.
• Browsing a backed-up mailbox in Veeam Explorer for Microsoft Exchange may fail with the “Object reference not set to an instance of an object” error.
• In Veeam Explorer for Microsoft SharePoint, the list of sites fails to load when opening a restore point from a backup job that has personal sites excluded.
• Under certain conditions, coping a OneDrive for Business item fails with the “Error: Specified location doesn't exist. Please, select another location” error.
• Data in some SharePoint document library columns may not be preserved after restore.

Reporting

• Monthly usage report includes users in a trial state.
• Generation of Mailbox Protection report fails with the “The operation has timed out” error.

Licensing

• Mailboxes of the Scheduling type consume a license.
• Revoking user license with the Remove-VBOLicensedUser cmdlet fails with the “Object reference not set to an instance of an object” error.

PowerShell

• Under certain conditions, the Get-VBOEntityData -Type User request may return an empty user’s display name while the user’s personal site or OneDrive account would be present in the repository.

RESTful APIs

• The “Credentials not found for key” error may occur on various requests after the RESTful API Service restart if an old refresh token is used.
• Getting SharePoint items via RESTful APIs may fail with the “Object reference not set to an instance of an object” error.