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

Below are details about each of the Cumulative Patches that have been released for Veeam Backup for Microsoft 365 6a.

Each subsequent Cumulative Patch also includes all fixes present in the previous Cumulative Patches.

P20230322 (6.1.0.1015)

Enhancements

• Reconnection attempts have been added for active restore sessions initiated with Veeam Explorer for Microsoft SharePoint and Veeam Explorer for OneDrive to maintain connections to remote backup proxies if they become unavailable.
• Up to 60x faster exploring of organization’s backups via Veeam Cloud Connect and Veeam Explorer for Microsoft Exchange in infrastructures where backups are distributed between multiple Jet-based repositories associated with multiple backup proxies.
• Additional parameters such as request timestamp, client request ID, and API URL are now included in logs for backup jobs that contain Microsoft Teams objects and use Teams Export APIs.

Resolved Issues

Backup

• In larger infrastructures, massive SharePoint backup jobs may remain pending to start.
• The entire backup job fails when the backup of a specific item from a OneDrive account fails with the error:

  SharePoint Foundation is not the owner of this file. Type: Microsoft.SharePoint.Client.ServerException” and cause the entire backup job failure.
  

• Under certain conditions, Microsoft Teams backup using Teams Export APIs may fail with the error:

  An item with the same key has already been added.
  

• The following warning may be displayed in the action log of a backup job configured to process an entire organization:

  Mailbox does not have a valid Microsoft 365 license.
  

  This warning was suppressed in Veeam Backup for Microsoft 365 v6a P20221215 (build 6.1.0.438). However, upon additional observation and testing following the release of that cumulative patch, we have identified some edge cases where the fix may not help. Starting with Veeam Backup for Microsoft 365 v6a build 6.1.0.1015, the suppression of that warning was rolled back.
• After upgrading Veeam Backup for Microsoft 365 from v5 to v6a, editing an organization or a backup job that contains Microsoft Teams objects fails with the error:

  Invalid backup configuration: Team chats backup using protected APIs must the enabled to protect Team chats.
  

• Backup of a team with a name containing unsupported characters (e.g., ~, #, %, &, *, {, }, +, /, :, <, >, ?, |, ’ ) fails with the error:

  Failed to execute MsGraph backend request GetSharepointUrlForChannelS2SRequest.
  

• In an organization using Modern authentication with legacy protocols allowed, backup of a public folder mailbox fails with the error:

  JetError -1605.
  

• SharePoint backup may fail with the error:

  Cannot contact site at the specified URL %URL%. Exception from HRESULT: 0x80131904.
  

• Microsoft Teams backup using Teams Export APIs may fail with the error:

  Object reference not set to an instance of an object.
  

• A SharePoint backup job that targets a local block-based repository and contains a list with a huge number of items may run with unreasonably low Saving Rates.
• Microsoft Teams backup using Teams Export APIs may fail with the error:

  Failed to process team: %team name%. UnknownError. The remote server returned an error: (403) Forbidden.
  

• Under certain conditions, a backup copy using an archiver appliance may fail with the error:

  SSH service is not available at: %IP%.
  

• Backup copy using an archiver appliance may not transfer Teams channel messages that were backed up with Teams Export APIs. To address this issue, a new -Full PowerShell parameter is added for Teams Data to initiate a full sync for team chats backup copy. For more information, review KB4436.
   

Restore

• Restoring a OneDrive to another location using the “Copy to” option may fail on the permissions validation step with the error:

  The remote server returned an error: (404) Not Found.
  

• A SharePoint or OneDrive restore initiated via REST APIs may fail with the error:

  User does not have sufficient permissions to perform restore operation.
  

• Restoring SharePoint items to a specific list may fail with the error:

  Failed to convert field: Service (value: %value%, type: LookupMulti). The field was skipped.
  

• Restore operations initiated with Veeam Explorers via Veeam Cloud Connect stop after 9 hours.
• A OneDrive restore to another location using the “Copy to” option that is initiated via v5/v6 REST APIs mistakenly restores items to the original location.
• Customized email subject and body are ignored when sending Exchange mailbox items as an attachment using the POST https://<hostname>:4443/v6/RestoreSessions/{restoreSessionId}/organization/mailboxes/{mailboxId}/items/sendToDifferentAddress REST API request.

P20221215 (6.1.0.438)

Enhancements

• Optimized requests for backup operations and management of organizations using the new protected Teams Export APIs.
  
  

Resolved Issues

General

• Under certain conditions, the Veeam.Archiver.Service may lose connection to existing remote backup proxies in the infrastructure.
• In the Edit Object Storage Repository wizard, the ‘Use archiver appliance’ checkbox remains unchecked for Azure Archive Storage repositories initially configured for using archiver appliances.
• After upgrading to Veeam Backup for Microsoft 365 6a, a SharePoint backup job configured to an object storage repository may fail with the error:

  Unable to access repository (%path%) JetError -1504, JET_errNullInvalid.
  

• A backup repository extended with an archive tier object storage that has encryption enabled may go to the "Invalid" state after the encryption key has been changed and display the error:

  Object reference not set to an instance of an object.
  

• Synchronization of an object storage repository containing SharePoint data may fail with the error:

  There are multiple versions of the same page.
  

• Backup job session statistics may not get updated during the job run if multiple backup jobs are running simultaneously on the same backup proxy.
• The VMC logs may not be updated after upgrading to Veeam Backup for Microsoft 365 6a.
• The Veeam Backup for Microsoft 365 Console freezes when opening a restore session action log with a large number of entries.
• Under certain conditions, synchronization of an object storage repository containing the user’s Exchange Online mailbox data may fail with the error:

  An item with the same key has already been added.
  

  
  

Backup and Backup copy

• The backup copy job does not preserve the Deleted state of SharePoint items when transferring the data to an archive tier repository.
• Under certain conditions, a SharePoint backup job may mistakenly complete with a warning when no other jobs containing this object are running:

  %object name% is already processed by another job (ID: %job ID%)
  

• A Microsoft Teams backup job doesn't create a restore point if it is completed with the warning:

  %object name% is already processed by another job (ID: %job ID%).
  

• A Microsoft Teams backup job processing Team chats using Teams Export APIs may fail with the error:

  Value cannot be null. Parameter name: HTML.
  

• A Teams backup job processing Team chats using Teams Export APIs fails to start with the error:

  Illegal characters in path.
  

• A SharePoint backup job performs a full sync for specific lists instead of an incremental run if the previous run was completed with errors during the processing of lists.
• SharePoint backup job may complete with the error:

  Microsoft.SharePoint.SPException occurred: (-2147467259) Cannot complete this action.
  

• Under certain conditions, a SharePoint backup job may fail with the error:

  JetError -1302, JET_errTableLocked, Table is exclusively locked.
  

• Under certain conditions, a SharePoint backup to an object storage repository may fail with the error:

  File version 257 has already been committed.
  

• The following excessive warnings are displayed in the action log of a backup job configured to process an entire organization:

  Mailbox does not have a valid Microsoft 365 license.
  

• An attempt to use auxiliary backup applications is performed during the processing of SharePoint or OneDrive objects after all such applications have been removed from the Veeam Backup for Microsoft 365 configuration.
• If an archiver appliance was used for copying backup data, a backup copy job containing a team with team chats excluded from processing fails with the error:

  Unable to find mailbox account (mailbox ID: %ID%)
  

  
  

Restore

• Under certain conditions, in Veeam Explorer for Microsoft SharePoint, browsing subsites may fail with the error:

  Value cannot be null. Parameter name: buffer.
  

• When browsing backups, an empty organization is displayed in the tree of objects if all backed-up objects belonging to this organization have been deleted from backups or moved to a different repository.
• Browsing a user’s mailbox backups in Veeam Explorers may fail if the user has been deleted and recreated with the same name and mailbox at a certain point during backup. The following error will be shown:

  JetError -1605, JET_errKeyDuplicate, Illegal duplicate key
  

• When restoring a SharePoint Online site to SharePoint Subscription Edition, some of the site pages are not restored.
• After successfully restoring SharePoint Online items to an on-premises organization, the following error may be displayed:

  Item is not checked out.
  

• Lookup columns may not be added to views after restoring a backed-up SharePoint site to a new location, despite the state of the restore session being displayed as a Success.
• When browsing an Exchange Online mailbox backup, some backup data is not displayed if an ID of the backed-up mailbox was changed during the backup.
  
  

Licensing

• Under certain conditions, in Veeam Backup for Microsoft 365 servers with a Rental license installed, the license status of a backed-up user is not updated from New to Licensed.
• Under certain conditions, in Veeam Backup for Microsoft 365 installations with rental licenses, a Monthly usage report is not generated after upgrading to v6.
  
  

PowerShell

• Excluding a team from processing via the Add-VBOExcludedBackupItem cmdlet fails with the error:

  Invalid backup configuration: Cannot exclude Team chats from the backup.
  

• In hybrid organizations, the Get-VBORestorePoint cmdlet may return duplicates of restore points.
  
  

REST API

• One of the identical concurrently sent GET requests fails with the error:

  An item with the same key has already been added.
  

P20220926 (6.1.0.423)

Enhancements

• OneDrive restores initiated via the Restore Portal will now start immediately, thanks to eliminating excessive requests to resolve users.
• Up to 30% faster SharePoint backup to Jet-based repositories that contain a large number of databases.
   

Resolved Issues

General

• Under certain conditions, applying retention on list states within SharePoint backup data stored in an object storage repository may fail with the error:

  JetError -1013, JET_errOutOfCursors, Out of table cursors.
  

• The Veeam license cannot be revoked for a user if copies of that user’s backup data are stored in an archive-tier object storage repository.
  
• The retention may incorrectly skip SharePoint websites from cleaning.
  
• The Amazon Archiver Appliance may fail to start with the error:

  Incorrect parameter
  

• Retention applied to a Microsoft Teams backup copy can mistakenly remove a corresponding group mailbox and its data if stored in the same archive-tier object storage repository.
• Initiating new operations on a backup proxy, including creating new repositories and starting new jobs, is not possible if any of the object storage repositories associated with such a proxy are in an Out-of-Date state.
   

Backup and Backup copy

• A Backup Copy job transfers more data than expected if the error “(412) Precondition Failed” occurs during the backup.
• A Backup Copy job is not terminated when exceeding the configured allowed backup window.
• Under certain conditions, a Microsoft Teams backup job targeted to a Jet-based backup repository may fail with the error:

  Failed to resolve team (ID: <team-guid>, name: <name>): Organization (ID: <org-guid>) which the team (ID: <team-guid>) belongs to not found.
  

• Backup of an auto-expanded archive mailbox may fail with the error:

  Failed to synchronize item changes in folder: <folder-name>. Synchronization state data is corrupt or otherwise invalid.
  

• Teams files and posts are skipped from processing during a backup copy if the previous backup copy job run has completed with the error:

  Exception of type ‘System.OutOfMemoryException’ was thrown.
  

• The Backup Copy job displays the incorrect item count if a new version of a backed-up file has been added in the production environment between the next backup and the backup copy job runs.
• A Backup Copy job containing Teams objects fails with the error:

  An item with the same key has already been added if those teams are using the same SharePoint site.
  

• Under certain conditions, in hybrid organizations, the backup of a security group may fail with the error:

  Cannot process argument transformation on parameter ‘Identity’. Cannot convert value "00000000-0000-0000-0000-000000000000".
  

• A full sync may be triggered for SharePoint lists after upgrading to Veeam Backup for Microsoft 365 6a.
• A Backup job containing SharePoint sites with blocked access fails with the warning:

  Some objects were not enumerated.
  

• Under certain conditions, a backup job targeted to a Jet-based repository may fail with the error:

  List was not found in repository.
  

• A Backup Copy job skips files from a SharePoint site if the processing of those files failed on the previous job run.
   

Restore

• In the action log of Veeam Explorer for Microsoft SharePoint and Veeam Explorer for Microsoft OneDrive, a restore session for saving an item is mistakenly displayed in a running state after successfully completing the operation.
• In the session history, a restore session initiated via PowerShell and started for a specific retrieved SharePoint, OneDrive, or Microsoft Teams item is incorrectly displayed with the ‘Entire organization’ flag.
• When browsing a backup stored in object storage, Veeam Explorer for Microsoft Teams may not display the reply to a post that has been deleted in the production environment.
• Veeam Explorer for Microsoft Teams doesn’t display @mentions added to team posts backed up via Teams Export APIs.
• The ‘Modified by’ field of a SharePoint item is changed after restore, if this item was restored from a backed-up list created using a certain template.
• Restoring a team that has been created via PowerShell with the HiddenGroupMembershipEnabled parameter set to ‘true’, fails with the error:

  Visibility of a group with hidden membership cannot be updated.
  

  
  

PowerShell

• The Set-VBOEmailSettings cmdlet does not support the configuration of connecting using SSL without authentication.
   

REST API

• In v6 and v5, the (GET) /Organization REST API endpoint incorrectly returns the “useApplicationOnlyAuth”: true for organizations using Basic authentication.
• Bulk mailbox restore initiated with the (POST) /v6/RestoreSessions/{restoreSessionId}/organization/mailboxes/restore request may fail with the error:

  The given key was not present in the dictionary.
  

• The Content-Length parameter is missing from the response header in the v5 and v6 /RestoreSessions/{restoreSessionId}/organization/mailboxes/{mailboxId}/exportToPst requests.
• The (GET) /v6/JobSessions request with the jobType: Copy parameter returns an incorrect link with a job ID.
   

Restore Portal

• In the Restore Portal, a restore operator exploring backups from an object storage repository cannot change the scope to another user if the organization that user belongs to doesn’t have any Exchange restore points.
   

P20220825 (6.1.0.254)

Resolved Issues:

• A backup of Security groups, Distribution groups, M365 groups, and specific users may complete with the warning:
  

  Nothing to process
  

  When this occurs no restore point is created for such objects.
  
  Note: Depending on the job configuration, the job may complete with a Success status, and the problem may occur unseen

• Under certain conditions, a backup job that includes SharePoint, OneDrive, or Microsoft Teams objects may run longer than expected, and the processing of lists may complete with the warning:
  

  Failed to analyze list changes. Value does not fall within the expected range.
  

To manually update an existing Veeam Backup for Microsoft 365 6.1.x deployment to the latest Cumulative Patch listed on this page, follow the same steps as upgrading Veeam Backup for Microsoft 365.

1. Ensure that there are no active Backup or Restore sessions running.
2. Close all Veeam and PowerShell consoles.
3. Mount the ISO on the Veeam Backup for Microsoft 365 server.
4. Run Veeam.Setup from the ISO
5. Click Update and follow the prompts to update the software.