Release Information for Veeam Backup for Microsoft 365 8.4

New Features and Enhancements

• Introduced the ability to specify the number of SharePoint file versions to protect. You can choose to protect only the latest versions or the entire file version history when backing up SharePoint sites, OneDrive data, and Teams files. Limiting protection to the latest version reduces throttling risks and improves backup performance. This feature is available via PowerShell and REST APIs. For more details, see KB4816.
• The Restore Portal now has an updated look and feel. The interface is cleaner and easier to navigate, with improved visual hierarchy and a more consistent layout throughout. Additionally, the Restore Portal now offers an improved experience for browsing protected user data. Restore operators select the user data to browse and restore—emails, OneDrive, or SharePoint—and choose a restore point to display the data. This flow resolves visibility issues caused by storing different user data types in separate repositories, ensuring a consistent, clear experience.
• New built-in data protection reports provide insights into your backed-up OneDrive, SharePoint, and Teams data. All three reports are accessible via REST APIs and available in CSV format.
• TLS connections are supported between the Veeam Backup for Microsoft 365 controller, its remote proxies, and PostgreSQL. TLS is enabled by default when you install the product with default settings.
• Introduced the ability to specify data locations to protect, addressing legal and compliance requirements of enterprises operating across regions. This functionality is available in the REST APIs at the (GET) and (PUT) /v8/organization/{organizationId}/tenantInformation endpoints.
• The ability to add auxiliary backup applications for SharePoint processing is deprecated. For more details, see KB4567 and KB4821.
• The (POST) /v8/Organizations/{organizationId}/explore endpoint now accepts the repositoryId parameter to select the repository to read data from.
• Log export has been enhanced for improved performance and stability.
• Optimized load balancing on proxy pools during restore and export operations.
• SharePoint backup performance improved, and throttling risks reduced:
  • by optimizing requests to retrieve list properties;
  • by fewer requests to SharePoint Online during incremental backups;
  • by optimized list processing that improves error handling, affecting change token usage and incremental backups.
• Improved SharePoint backup and object storage repository performance by extending asynchronous processing to list content retrieval and file cache operations.
• Up to 22% faster saving of Exchange data to object storage during backup.
• Introduced a retention retry mechanism to automatically restart retention tasks interrupted by operations such as backup or restore.
• Improved performance of the following REST API endpoints:

  • (GET) v8/RestoreSessions/{sessionId}/organization/sites/{siteId}/lists
    

  • (GET) v8/RestoreSessions/{sessionId}/organization/sites/{siteId}/libraries
    

• The "JobCheckItems" parameter has been added to the following REST API endpoints to enable forced skipping of item validation and accelerate execution:

  • (POST) v8/Jobs
    

  • (PUT) v8/Jobs/{jobId}
    

  • (POST) v8/Jobs/{jobId}/SelectedItems
    

  • (PUT) v8/Jobs/{jobId}/SelectedItems/{itemId}
    

  • (POST) v8/Jobs/{jobId}/ExcludedItems
    

  • (PUT) v8/Jobs/{jobId}/ExcludedItems/{itemId}
    

• Added host rollback detection for proxies in a proxy pool to enforce repository synchronization and maintain consistent repository states.

Bug Fixes

General

• Some SharePoint, OneDrive, or Teams files or list attachments restored from backups may not open correctly in their associated applications (e.g., Microsoft Word, Excel, PowerPoint, Adobe Acrobat) and display the following common errors:

  The file is either not a supported file type or has been damaged.
  

  Word found unreadable content…
  

  Excel cannot open the file ... because the file format or file extension is not valid.
  

  Sorry, this document can't be opened for editing.
  

  For more details, see KB4835
• The Veeam Backup for Microsoft 365 console freezes when the user attempts to run the “Support Information” wizard.
• Re-attaching an encrypted repository with an incorrect password fails with the error, instead of a clear error message:

  Sequence contains no elements
  

• A proxy service processing SharePoint data with numerous metadata fields can exhaust all CPU and RAM resources and crash.
• An object storage repository linked to a proxy pool may unexpectedly enter an Out of sync or Invalid state.
• Object storage repository synchronization fails under certain conditions with the error:

  SqlState: 21000. ON CONFLICT DO UPDATE command cannot affect row a second time.
  

• After restarting the Veeam Backup for Microsoft 365 services or upgrading Veeam Backup for Microsoft 365, some proxies may enter an error state with:

  Padding is invalid and cannot be removed
  

• Restore points from a repository may remain available after the repository is deleted.

Backup and Backup Copy

• A long-running backup job remains in the "Pending operation" state longer than expected after being stopped.
• Teams backup job fails when processing channel posts with errors such as:

  Object reference not set to an instance of an object
  

  or

  Exception of type 'System.OutOfMemoryException'
  

• A backup copy job fails with the error:

  The given key '{value}' was not present in the dictionary.
  

• Exchange backup job runs longer than expected, displaying the following warning in the product logs:

  Message was not published due to deduplication
  

• Incremental SharePoint backup job runs longer than expected, with these errors in product logs:

  Failed to backup list: {value}. Cannot access a disposed object.
  

• Backup jobs may stay in the Running state without processing objects, displaying the error:

  Failed executing DbCommand
  

• Backup job fails to start with the error:

  Unable to cancel retention session
  

• Some SharePoint, OneDrive, and Teams files back up with empty content, even though their content exists in production, and the backup status shows success.

Restore

• SharePoint restore completes with a warning:

  Cannot update field MediaServiceDateTaken
  

  and an error:

  The attempted operation is not allowed because it exceeds the list view threshold
  

• Restoring a SharePoint site does not preserve the list's hierarchy.
• The list version history is restored incorrectly after restoring a SharePoint site.
• Under certain conditions, some subfolders in a public folder mailbox do not appear when exploring a mailbox backup.
• ‘Notebook’ and ‘Site contents’ page links are not updated after restoring a SharePoint site to a different location.
• SharePoint restore fails with the error:

  The item does not exist. It may have been deleted by another user.
  

• File and folder structure is not preserved after extracting a saved ZIP file with OneDrive on macOS.
• Restoring a SharePoint site to a different location triggers the following warning, even when the URL is unique:

  The site was restored with a unique suffix in its URL because the specified alias was already assigned to another site
  

• SharePoint library restore appears successful despite an error occurring during the process:

  Target list {value} type mismatch
  

• Browsing individual folders within a backed-up OneDrive fails with the error:

  Request failed with status code 400.
  

• Some mailboxes may not be available for browsing in Veeam Explorer for Microsoft Exchange.
• Restoring many large SharePoint files fails with the error:

  Exception of type 'System.OutOfMemoryException'
  

• Restoring multiple large SharePoint lists may fail with the proxy error:

  Exception of type 'System.OutOfMemoryException' was thrown.
  

• OneDrive restore automatically cancels after some processing time.
• When a restore operator role manages specific Microsoft 365 groups, changing the scope in the Restore Portal fails with the error:

  Exception was thrown on the remote side due to serialize method return value: Type
  

• When adding a restore operator for an entire organization scope, the user selection dialog shows users and groups from the incorrect organization rather than the one being configured.
• OneDrive save operation fails with error:

  Database does not exist or was forcibly closed by server.
  

• Restarting the Veeam Backup for Microsoft 365 controller during a restore operation initiated via REST APIs causes the restore session to appear as failed in the UI.

REST APIs

• REST API requests to restore session opening exceed expected durations, causing the error:

  I/O error occurred.
  

• The REST API response header lacks the content-length for mailbox folder and item export and save operations.
• The (GET) v8/Organizations/{organizationId}/usedRepositories endpoint does not return the used space amount in the repository.
• No data restores when using the (POST) v8/RestoreSessions/{sessionId}/organization/mailboxes/restore REST API endpoint with the "recentItemRestorePeriod" parameter.
• The "changeditems" and "deleteditems" parameters are ignored when restoring a OneDrive to another location using the following REST API endpoints:

  • (POST) v8/RestoreSessions/{sessionId}/organization/onedrives/{odId}/copyTo
    

  • (POST) v8/RestoreSessions/{sessionId}/organization/onedrives/{odId}/folders/copyTo
    

  • (POST) v8/RestoreSessions/{sessionId}/organization/onedrives/{odId}/folders/{odfoldId}/copyTo
    

• Deleted OneDrive items are restored when the "showdeleted" parameter is set to "false" in the (POST) v8/organizations/{orgId}/explore endpoint.

PowerShell and Data Management

• Executing the Get-VBOEntityData request fails with the error:

  An item with the same key has already been added.
  

• If the .NET 8 module is missing, running the Export-VboJobLog cmdlet fails with the error:

  The term 'Export-VboJobLog' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again
  

• Moving SharePoint backup data to an object storage repository may get stuck.