Release Information for Veeam Backup for Microsoft 365 7a Cumulative Patches

P20240418 (7.1.0.2031)

New Features and Enhancements

• Exchange data restore with Veeam Explorer for Microsoft Exchange now uses modern certificate-based authentication.
• Improved the performance of the Move-VBOEntityData PowerShell cmdlet when transferring a large number of restore points to an object storage repository.
• Backup job performance improved when writing to a jet-based repository through the use of multiple simultaneous write threads.
• Up to 25% faster loading of the list of sites backed up to a Jet-based repository when exploring backups in Veeam Explorer for Microsoft SharePoint.
• Improved speed of loading backup copies retrieved from an archive-tier object storage repository in Veeam Explorer for Microsoft SharePoint. This improvement applies to larger sites containing numerous list attachments.
  
• Product logs now include information on potential issues during personal SharePoint site resolution, such as the deletion of a corresponding user account from the Microsoft 365 organization or the absence of the SharePoint license plan.

Resolved Issues

General

• A Global Administrator account is excessively required to configure email notifications using a Microsoft 365 mail server and modern authentication.
• Adding an immutable Amazon S3 object storage repository may fail with the error:

  "InvalidArgument", message: "The retain until date must be provided in ISO 8601 format", resource: "", requestId: "%ID%".
  

• When adding an organization, if the server is using an internet proxy, the connection to the EXO V3 PowerShell Module fails with:

  'Failed to download EXO module, no valid authentication token found’ 
  

• A temporary network connection interruption causes the remote backup proxy to switch to the Offline status for a few minutes.
• Mailbox Protection report generation fails with the error:

  Object reference not set to an instance of an object.
  

• When using the "Collect logs for the specified time period" option, the Support Information wizard collects logs based on their last modified date instead of the datestamp in the log files.
• The Support Information log collection tool does not include zip archives of the PowerShell logs.
• The log bundle created by the Support Information tool does not contain an HTML job report for the last day.

Backup

• Exchange backup fails with the error:

  Failed to get folder properties. Not allowed to access Non IPM folder.
  

  For more details, see KB4569.
• Exchange backup fails with the error:

  The value must be greater or equal to 104. Parameter name: array.Length.
  

• Exchange mailbox backup may fail with the error:

  Unable to process the Exchange Web Services item. Invalid serialized stream, unknown opcode found: 4.
  

• Under certain conditions, adding users to a backup job fails with the error:

  UnAuthorized in organizations configured to protect SharePoint Online workload only.
  

• OneDrive backup may fail when processing a OneNote file with the warning:

  Failed to backup item: %path%, Download request retry timeout exceeded.
  

• Backup to MinIO S3-compatible storage may fail with the error:

  Access Denied.
  

• Under certain conditions, a backup job targetting an object storage repository fails to start with the error:

  An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full %IP:port%.
  

Backup Copy

• The incremental run of a backup copy job to certain types of immutable S3-compatible repositories may fail with the error:

  An exception of type "Veeam.Engine.ObjectStorage.AccessDeniedException" was thrown.
  

• Under certain conditions, an incremental run of a backup copy job to an immutable S3-compatible object storage repository may fail with the error:

  "NoSuchObjectLockException", message: "The specified object does not have a ObjectLock configuration.", resource: "", requestId: "%ID%".
  

• The backup copy job ignores historical Exchange backup data that was created using Veeam Backup for Microsoft 365 builds 4.0.0.1345 through 4.0.1.625.
• A backup copy job may fail with the error:

  Unexpected XML attribute of Retention: xmlns:xsd. The remote server returned the error: (400) Bad request.
  

• A backup copy job transferring SharePoint data may run endlessly if it has been restarted after a stop or interruption.
• A backup copy job that transfers SharePoint data may take more time to complete than expected.
• A backup copy job to an immutable object storage repository takes more time to complete than expected. In the diagnostic logs, the following error repeats:

  Cleaning up cache to fit in the new resource (memory cache: BlobCache, current size: {size}...).
  

Restore

• If the default folder for storing temporary files required for restore operations initiated via REST APIs has been changed in the configuration file, exploring Exchange backups in Veeam Explorer for Microsoft Exchange may fail with the error:

  The system cannot find the file specified
  

• In Veeam Explorer for Microsoft Exchange, the mailbox export to PST operation may miscalculate the amount of exported data, causing the export status to display a completion value greater than 100%.
• In Veeam Explorer for Microsoft Teams, opening and restoring some Teams channel messages may fail with the error:

  There is an error in XML document (2, 20). This issue applies to system event messages.
  

  For more information, see KB4513.
• If a message has been backed up using paid Teams Export APIs, emoji (s) from a Teams channel message body is not displayed in the backed-up message preview within Veeam Explorer for Microsoft Teams.
• When restoring a SharePoint site, if the ‘Restore permissions’ option is not enabled, the restore may take more time than expected and complete with the warning:

  Failed to get user: i:0#.f|membership|%useraccount%. User cannot be found
  

• Despite a restored SharePoint list attachment reportedly being restored successfully by Veeam Explorer for SharePoint, it fails to open in production.
• Restoring a SharePoint list to a new location within the initial site may complete with the error: "There is no file with URL in this Web," or may result in an empty list being restored if the target site URL has been altered in production.
• Restore of a SharePoint item attachment may fail with the error:

  Save Conflict. Your changes conflict with those made concurrently by another user.
  

• In Veeam Explorer for Microsoft SharePoint, restoring a SharePoint site to a new site alias fails with the error:

  Failed to restore web: %web%. Parent of the item not found (item ID: %ID%).
  

• Restore of a site item in Veeam Explorer for Microsoft SharePoint may fail with the error:

  Server error of type Microsoft.SharePoint.SPException occurred: (-2146232060) Web %URL% is busy.
  

REST APIs

• Under certain conditions, management operations requests initiated via REST APIs may take more time to complete than expected.
• In the Restore Portal, loading a point selected by a Restore Operator (using the (POST) /v7/Organization/OperatorExplore request) may take more time than expected on installations running Veeam Backup for Microsoft 365 version 7 P20231015 (build 7.0.0.4388) and higher.
• Adding an immutable Wasabi object storage repository using the (POST) /v7/objectstoragerepositories REST API request fails with the error:

  The selected object storage does not support immutability.
  

• Getting a list of backed-up SharePoint sites with the (GET) /v7/RestoreSessions/{id}/organization/sites request takes more time compared to a similar operation performed using Veeam Explorer for Microsoft SharePoint.
• Creating or editing a backup job that contains objects that have not been synchronized to a local cache with the (POST) /v7/Organizations/{organizationId}/Jobs fails with the error:

  The %object% was not found in the organization (ID: %ID%, onPremisesSid: %ID%), 
  

• On product builds 7.0.0.3604 and higher, processing REST API requests to retrieve the organization’s objects takes more time than expected.
  • (GET) v7/Organizations/{organizationId}/Users
  • (GET) /v7/Organizations/{organizationId}/Teams
  • (GET) /v7/Organizations/{organizationId}/Sites, 
• Export to .PST via the (POST) /v7/RestoreSessions/{restoreSessionId}/organization/exportToPst request takes more time compared to the save operation performed on the same mailbox backup data.
• If one of the requested repositories is in the Invalid state, the (GET) /v7/Organizations/{organizationId}/usedRepositories request mistakenly returns the same error for all repositories from the scope.
• The (GET) /v7/RestorePoints/Changes request may never receive a response from the Veeam Backup for Microsoft 365 REST API service in case of frequent calls of this request.
• The (GET) /v7/RestorePoints/{restorePointId}/protectedUsers and (GET) /v7/RestorePoints/{restorePointId}/protectedGroups requests may never receive a response from the Veeam Backup for Microsoft 365 REST API service in case of frequent calls of these requests.

PowerShell

• Attempting to remove a team backup from an object storage repository using the Remove-VBOEntityData cmdlet while a retention job is occurring may fail with the error:

  Failed to open FilesIndexPages table (organization ID: %ID%)
  

• Transferring SharePoint site backup data from a Jet-based repository to an object storage repository with the Move-VBOEntityData cmdlet may fail with the error:

  OutOfMemoryException.
  

• Adding an Amazon S3 object storage repository with the Add-VBOAmazonS3ObjectStorageRepository PowerShell cmdlet and using the EnableIAStorageClass parameter fails with the error:

  Parameter set cannot be resolved using the specified named parameters.
  

• If a SharePoint site's name exceeds 255 characters, attempting to transfer that site from a Jet-based repository to an object storage repository using the Move-VBOEntityData cmdlet will fail with the error:

  This request operation sent to net.tpc://%IP:port%/%% did not receive a reply within the configured timeout (%time%)
  

In recognition of the potential impact of the issue documented in KB4569 on customers deploying new Veeam Backup for Microsoft 365 servers, the ISO from 7.1.0.1501 was rebuilt to include the hotfix from KB4569. This newly rebuilt ISO had its build number incremented to 7.1.0.1502 to represent that singular change.

Critical: Unlike traditional cumulative patch releases, which include the hotfixes released since the last build, this release, 7.1.0.1502, only includes the hotfix from KB4569. Therefore, it's crucial that if 7.1.0.1501 is installed and any hotfixes (other than the one from KB4569) are installed, please do not install 7.1.0.1502. Please wait for the next Cumulative Patch, which will be released soon.

Resolved Issues

• Exchange backup fails with the following error:

  Failed to get folder properties. Not allowed to access Non IPM folder
  

  For more information, review: KB4569

P20240123 (7.1.0.1501)

Resolved Issues

• Exchange backup fails with the following error:

  Invalid serialized stream, unknown opcode found: 4
  

  For more information, review: KB4540
• OneDrive backup fails on processing OneNote files with the following error:

  Failed to backup item: %path%, Download request retry timeout exceeded.
  

  For more information, review: KB4529

P20231218 (7.1.0.1401)

Resolved Issues

• Exchange backup fails with the following errors:

  There is an error in XML document
  

  and

  The specified type was not recognized: name='SharingMessage'
  

  For more information, review: KB4527