Veeam Backup for Microsoft Office 365 version 5b provides compatibility with Veeam Backup & Replication version 11

Reading Time: 3 minutes
Veeam Backup for Microsoft Office 365

Late last month, we saw the release of version 5b of Veeam Backup for Microsoft Office 365. Version 5b with build number 5.0.1.179 provides new functionality beyond the functionality provided by version 5a of Veeam Backup for Microsoft Office 365 (build number 5.0.0.1070).

What’s New

Here’s what’s new and enhanced in version 5b of Veeam Backup for Microsoft Office 365:

Support for Veeam Backup & Replication v11 and Veeam Cloud Connect v11

Version 5b of Veeam Backup for Microsoft Office 365 now supports installation on top of Veeam Backup & Replication v11 and Veeam Cloud Connect v11.

Enhanced guest user enumeration

Guest users are automatically excluded from organization objects enumeration and backup.

Enhanced email notifications

For backup jobs processing personal sites, email notifications on job results add a link to user’s backed up personal sites.

What’s Fixed

There are a lot of issues that have been resolved in version 5b of Veeam Backup for Microsoft Office 365:

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 365 versions 3.0 through 4c.

Backup

SharePoint and OneDrive backup may fail with one of the following errors:

(500) Internal Server error

(400) Bad Request

Under certain conditions, Teams backup may fail with the following error:

Object reference not set to an instance of an object

OneDrive backup may fail with the following error:

Index (zero based) must be greater than or equal to zero and less than the size of the argument list

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 following error

Invalid MIME content-length header encountered on read

Archive mailbox backup may fail with the following error:

Failed to access archived message folder root. SOAP header Action was not understood

Restore

Teams restore with an application and app certificate fails with the following error:

Error in validating credentials: Account does not have a valid Microsoft Teams license

OneDrive restore may fail with the following error:

The attempted operation is prohibited because it exceeds the list view threshold enforced by the administrator

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.

Upgrading to version 5b

If you're running a previous version of Veeam Backup for Microsoft Office 365 and want to be prepared for the release of Veeam Backup & Replication v11 and Veeam Cloud Connect v11, now is a great time to upgrade to the updated version. You can simply upgrade to version 5b from versions 3.0 (build 3.0.0.422) and upwards.

However, upgrade from the beta version of Veeam Backup for Microsoft Office 365 5.0 are not supported. Additionally, Veeam Backup for Microsoft Office 365 5b is not applicable to installations of Veeam Backup for Microsoft Office 365 on top of Veeam Backup & Replication 9.5 Update 4, 4a, or 4b and Veeam Cloud Connect 9.5 Update 4, 4a, or 4b.

Further reading

KB4092: Release Information for Veeam Backup for Microsoft Office 365 5b
Veeam Backup for Microsoft Office 365 5b Release Notes
Quick Post – New Patch for Backup for Microsoft Office 365… v11 is Coming!

leave your comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.