https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IzMDY1IiwiaGFzaCI6IjRiNDViZGRmLTA1N2EtNDQ2YS1hNjE2LTQzOWQ5MzI2ZTE4MiJ9
1-800-691-1991 | 9am - 8pm ET
EN

Release notes for Veeam Backup for Microsoft Office 365 4b

Challenge

Release Notes for Veeam Backup for Microsoft Office 365 4b.

Please note that Veeam Backup for Microsoft Office 365 4с is now available and contains all the resolved issues from Veeam Backup for Microsoft Office 365 4b.

Cause

Please confirm you are running Veeam Backup for Microsoft Office 365 version 2.0 (builds 2.0.0.567, 2.0.0.594 and 2.0.0.814), version 3.0 (builds 3.0.0.422 — 3.0.0.480), version 4.0 (build 4.0.0.1345) or version 4a (build 4.0.0.1553) prior to installing version 4b (build 4.0.0.2516). You can check the product version under Help > About in the Veeam Backup for Microsoft Office 365 console. After upgrading, your build version will change to 4.0.0.2516

Version 4.0.0.2516 delivers compatibility support for Veeam Backup & Replication v10 and its applicable components and includes a set of bug fixes listed below.


What’s New 

 
  • Support for Veeam Backup & Replication v10 compatibility.
  • Support for Veeam Cloud Connect v10 compatibility. 
IMPORTANT NOTE:
  • Veeam Backup for Microsoft Office 365 version 4.0.0.2516 is applicable to:
    • standalone installations of Veeam Backup for Microsoft Office 365
      • version 2.0 (builds 2.0.0.567, 2.0.0.594 and 2.0.0.814)
      • version 3.0 (builds 3.0.0.422 — 3.0.0.480)
      • version 4.0 (build 4.0.0.1345)
      • version 4a (build 4.0.0.1553; see KB3035 for more details)
    • installations on top of Veeam Backup & Replication v10 and Veeam Cloud Connect v10.
  • Version 4.0.0.2516 is NOT applicable to installations on top of
    • Veeam Backup & Replication 9.5 Update 4, 4a or 4b
    • Veeam Cloud Connect 9.5 Update 4, 4a or 4b
  • Upgrading backup repositories from version 3.0 to 4b may take significant time to complete and the upgrade duration highly depends on the amount and type of backup data in a repository. According to the test results, it may take up to 8 hours in the setup with 1 TB of data in a backup repository. Plan for an appropriate maintenance window when your backup repository that is been upgraded is not available for use. Note that upgrading version 2.0 repositories to 4b requires a bigger maintenance window due to many underlying changes to backup repositories. The upgrade process requires an additional 15% of free space of the current 2.0 repository size and may take up to 17 hours per 1 TB of data in a backup repository. 


Resolved Issues


General
  • Retention jobs do not fully purge the outdated service data, which causes product configuration database growth and impacts product upgrade duration. 
SharePoint Online and OneDrive for Business backup and restore 
  • Adding users with empty Display Names to a backup job fails with the “Value cannot be null” error. 
  • Backup of user’s OneDrive fails if the user name has been changed.  
  • Backup job containing excluded SharePoint sites with changed URLs fails with the following warning: “Failed to get site collection: {url}. Access denied. You do not have permission to perform this action or access this resource.” 
Object storage repositories 
  • Backing up public folders to a repository extended with object storage may fail with the following error: “This id is of the wrong type for this conversion operation (mailbox id vs. public folder id).”
  • Adding OpenStack Swift (Stein) S3 Compatible object storage repository with the s3api middleware for S3 REST fails with the “Unable to create folder (name: {0})” error.
  • Backup and retention jobs targeted at repositories extended with Amazon S3 object storage may fail with the “Specified argument was out of the range of valid values. Parameter name: count” error.
  • If an Azure storage container that is in use with an object storage repository has been deleted, the corresponding backup repository is put into the Invalid state and the backup proxy disk usage is at 100%.
  • A repository extended with Azure Blob Storage is still available for use (i.e. it’s not put to an Invalid state) when Azure storage account credentials become invalid. 
  • After changing retention period for a repository extended with object storage, backup jobs targeted to this repository stop processing.

Solution

To install Veeam Backup for Microsoft Office 365 4b: 
  1. Download the ZIP archive: VeeamBackupOffice365_4.0.0.2516.zip.
  2. Run the Veeam.Backup365_4.0.0.2516.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Backup for Microsoft Office 365.
  3. Run the VeeamExplorerForExchange_10.0.0.443.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Explorer for Microsoft Exchange. 
  4. Run the VeeamExplorerForSharePoint_10.0.0.443.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Explorer for Microsoft SharePoint. Note that Veeam Explorer for Microsoft OneDrive for Business is distributed in one package with Veeam Explorer for Microsoft SharePoint and will be installed automatically.   
After Veeam Backup for Microsoft Office 365 4b is installed, all backup repositories, backup proxies, and backup jobs will be marked as Out of Date. You need to upgrade these components manually from the Veeam Backup for Microsoft Office 365 UI as described here

More information

DOWNLOAD


MD5: 4aeed25923d877cf1fc556b0b54e4d5d
SHA-1: d131bd2a94aebc2721b2331e1ff9e27bc3349575
 
KB ID:
3065
Product:
Veeam Backup for Microsoft Office 365
Version:
2.0 or later
Published:
2020-01-31
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.