Release Information for Veeam Backup for Microsoft 365 8.2 and Cumulative Patches

Bug Fixes

Backup

• A backup job may fail when processing Archive Mailbox objects with the following error:

  Processing archive mailbox: username@organization.com failed with error: Mailbox is not fully configured.
  

  After updating Veeam Backup for Microsoft 365 to 8.2.0.2202, remember to upgrade all proxies.
  
  For more details, see KB4787.

New Features and Enhancements

• Added support for RHEL 9.6 as an operating system for a backup proxy server.
• Added support for Windows Server 2025.
• Added support for the Amazon S3 Asia Pacific (Taipei) region (ap-east-2).
• Collect product logs for a specific tenant or backup job.
• Up to 6X times faster log collection.
• Improved logging for operations initiated through REST APIs, such as mailbox export, SharePoint backup, and organization-wide backups.
• Improved action logs for the data move job now offer better insights into the operations performed while the job is running.
• The Microsoft Entra application you used to add your Microsoft 365 organization is now included by default in a pool of backup auxiliary applications for SharePoint.
• Faster retention runs on object storage repositories.
• Improved query handling enables faster connections from remote Veeam Explorers to the Veeam Backup for Microsoft 365 server.
• Improved memory usage on the Veeam Backup for Microsoft 365 controller.
• SharePoint processing performance improvements to reduce throttling in specific situations.
• Improved processing logic for multiple simultaneous tasks running on a proxy pool, such as restores and backups.

Bug Fixes

General

• Email notifications for job completion are not sent if the target repository is in an "Invalid" state.
• Increased memory consumption occurs on the host running Veeam Backup for Microsoft 365 server.
• Upgrading Veeam Backup for Microsoft 365 to v8 fails with the error:

  23505: duplicate key value violates unique constraint "pk_operator_role_scope_teams".
  

• Retention task for an object storage repository fails with the error:

  Cannot find object.
  

• Retention applied to SharePoint backups in an object storage repository fails with the error:

  File cache context will be invalidated due to an unhandled exception.
  

• Applying retention to an object storage repository fails with the error:

  duplicate key value violates unique constraint "pk_exchange_items_previews_uploads"
  

• Generating a User Protection report fails with:

  An item with the same key has already been added.
  

• Adding an Amazon Archiver Appliance using AWS EC2 fails with the error:

  One or more errors occurred. (Cannot find an internet gateway route.)
  

Backup and Backup Copy

• Adding Public Folder mailboxes to a backup job via REST APIs fails with a 500 status error code.
• SharePoint backup fails with the following warning in the product logs:

  Cannot access a disposed object.
  

• Backup jobs with SharePoint or Teams data seem stuck and show no activity.
• SharePoint backup job to an object storage repository fails with the error:

  Failed to apply immutability to object {value} because the object is already immutable. Access denied. Could not perform the operation because of missing permissions or wrong data center region.
  

• SharePoint backup job fails with the error:

  Failed to backup list: {value}. Cannot find object: {value}. Total count of failed items: {value}.
  

• SharePoint backup job fails with the error:

  Timeout has expired: 900000 milliseconds.
  

• OneDrive or SharePoint backup fails with the error:

  Item has been changed during the backup.
  

• A backup job with a large OneNote file can get stuck if changes are made to the file during the backup.
• The increased number of objects in OneDrive backup jobs is failing due to unexpected throttling and download failures.
• Teams backup fails with the error:

  Provided hosted content identifier is invalid.
  

• Under certain conditions, Teams backup fails with the error:

  Invalid URI: The hostname could not be parsed.
  

Restore

• Exploring backups fails with the error:

  An item with the same key has already been added. Key: gl-ES.
  

• Retrieving backups from an archive tier repository fails with an error:

  Failed to get task result because the task is running (ID: {value}).
  

• If a restore session cannot start within the default timeout, it fails with the error:

  Backup data is not available because the following proxies are offline: {value}.
  

• Opening a file protected with Microsoft Purview Sensitivity Label after restoring or exporting from a backup fails with an error indicating that the file is corrupted. For more details, see KB4754.
• Some restore points may be missing in the Restore Portal if backup data has been transferred from a Jet-based repository to an S3-compatible object storage using the Move-VBOEntityData cmdlet.
• The mailbox folder structure after exporting differs from that of the original production mailbox. This issue affects Veeam Backup for Microsoft 365 installations upgraded to v8 from earlier versions.
• Mailbox export to PST fails with the error: Failed to get task result because the task is running.
• Exporting a mailbox or parts of it fails with the error:

  Timeout has expired: 300000 milliseconds.
  

• Restoring a mailbox folder fails with the error:

  An item with the same key has already been added. Key: 0.
  

• Exploring Exchange backups initiated via REST APIs takes longer than expected with larger object volumes (approximately tens of thousands).
• SharePoint restore fails with the error:

  Error=Value=StoreBusyRetryLater, Tag=0x2022288b, Message=GetBlobsFromReaderAsync SQL command.RetunValue == 1150 Type: Microsoft.SharePoint.Client.ServerException.
  

• SharePoint restore fails with the error:

  {value} hexadecimal value {value}, is an invalid character.
  

• SharePoint restore fails with the error:

  Cannot change moderation status.
  

• SharePoint restore fails with the error:

  A URL field contains invalid data. Please check the value and try again.
  

• The restore of SharePoint data completes with a misleading ‘Cancelled’ status and the following error:

  List restore is canceled by user. Restoring of item {value} was canceled (type: {value}; source: {value}; target: {value}).
  

• Exporting a backed-up SharePoint folder with approximately 1 million items or more results in high memory consumption on the Veeam Backup for Microsoft 365 server.
• Restoring a large OneDrive file fails with the error:

  Error=Value=StoreBusyRetryLater, Tag=0x2022288b, Message=GetBlobsFromReaderAsync SQL command.RetunValue == 1150.
  

• Restoring a OneDrive with multiple folders initiated via REST APIs fails with an error:

  Unexpected error occurred.
  

• Saving OneDrive backup data to a ZIP file fails with an error:

  Parent of the item not found.
  

• A backed-up OneDrive containing a OneNote file is saved as an empty ZIP file.
• Restoring a OneDrive via REST APIs shows a Success status, but no data is restored.
• An attempt to explore the Files tab in a Teams channel fails with the error:

  Object Reference Not Set to An Instance of An Object.
  

• Search across backed-up Teams initiated via REST APIs fails with the error:

  Failed to get task result because the task was canceled (ID: {value}).
  

• Team channel messages are not available for restore if a backup job was reconfigured from "Back up entire organization" to "Back up the following objects."

REST APIs

• The (GET) /v8/Events request does not return the "RestorePointObjectsChange" event for objects previously migrated from a Jet-based repository to an object storage repository.
• The (GET) /v8/ProtectedSites request does not return a personal site if the user's OneDrive is not backed up.

Data Management

• Moving a team between Jet-based repositories using the Move-VBOEntityData cmdlet fails with the error:

  List was not found in repository.
  

• Data move from a Jet-based repository to an object storage repository fails with the error:

  Exception of type 'System.OutOfMemoryException' was thrown.
  

• A data move job initiated using the Move-VBOEntityData cmdlet gets stuck if the source repository runs out of space.
• A data move job transferring a SharePoint site with subsites to an object storage repository gets stuck.