Release Information for Veeam Backup for Microsoft 365 6.0 Cumulative Patches

KB ID: 4285
Product: Veeam Backup for Microsoft 365 | 6.0
Published: 2022-05-05
Last Modified: 2022-08-10
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Requirements

This Cumulative Patch can be used to:

  • update manually from a previous Veeam Backup for Microsoft 365 6.0 release to the latest Cumulative Patch.
  • upgrade an existing pre-6.0 Veeam Backup for Microsoft 365 server to Veeam Backup for Microsoft 365 6.0 with the latest Cumulative Patch.
  • install a new deployment of Veeam Backup for Microsoft 365 6.0 with the latest Cumulative Patch included.

 

After installing the Cumulative Patch, the Veeam Backup for Microsoft 365 build number will be 6.0.0.400 (P20220718)

Release Information

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

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

P20220718 (6.0.0.400)

Improvements & Enhancements:

  • Faster processing of the (GET) v5/Organizations/{organizationId}/usedRepositories request

Resolved Issues:

General

  • Generating a Mailbox Protection report fails if the Veeam Backup for Microsoft 365  Console gets disconnected by the inactivity timeout during report generation. 
  • Retention applied to Microsoft Teams posts fails with the error:
    Unexpected history ID for download.
    
  • Under certain conditions, the retention job may fail with the error:
    JetError -1605, JET_errKeyDuplicate.
    
  • Email notification for backup job results is not sent for jobs that were running when the notifications were configured.
  • Some possible issues with retention of SharePoint, OneDrive items, or Team files in case of error 412 occurred during backup.

Backup and Backup Copy

  • In a Hybrid organization, if there is a “:” symbol in the SMTP address, the resolving objects stage of a job will fail with the error:
    Unexpected proxy address format.
    
  • In a Hybrid organization, an Exchange mailbox backup of an active user may fail with the error:
    Exchange account was not found.
    
  • After manual modification of the AmazonDefaultAMIImage and AmazonDefaultInstanceType parameters in the Veeam Backup for Microsoft 365 Proxy.xml configuration file, backup copy jobs fails with the error:
    The service returned an error with Error Code ParameterNotFound and HTTP Body: {"__type":"ParameterNotFound"}.
    
  • A Backup Copy job using an Amazon archiver appliance fails with the error:
    SSH service is not available at: %IP address%:%port%.
    
  • Backup jobs cannot run and are stuck in the Operation pending state with the following error in log files:
    Illegal characters in path.
    
  • The Backup of an entire organization may complete with the following warnings:
    Processing site %site URL% finished with warning:
    User %username% does not have a valid Microsoft 365 license with SharePoint plan enabled.
    

Restore

  • In Veeam Explorer for Microsoft Teams, team files from previous years are not displayed if a corresponding team site has been removed from the repository via PowerShell. The issue only applies to Jet-based backup repositories. 
  • When exploring a SharePoint backup, the latest item version may be displayed incorrectly if such an item has been moved between different site lists after the first backup.
  • Under certain conditions, exploring team posts backed up to an object storage repository may fail with the error:
    The specified blob doesn’t exist.
    

PowerShell and REST APIs

  • Responses from version 6 to requests from version 5 incorrectly display the "?" symbol.
  • Response links from version 6 to requests from version 5 inherit the “offset=&limit=” parameters set to v5 requests.
  • Exchange items restore via REST APIs using Basic authentication may fail with the error: The communication object System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state, when using an invalid credentials.
  • Setting the Queued or Disconnected status when using the Get-VBOJobSession cmdlet fails with the error:
    The underlying secure session has faulted before the reliable session fully completed. The reliable session was faulted.
    
  • To specify the PeriodicallyOffsetMinutes parameter, the PeriodicallyWindowSettings parameter is mandatory when you modify the backup job schedule settings.

P20220524 (6.0.0.385)

Improvements & Enhancements:

Resolved Issues:

General

  • Creating multiple auxiliary backup applications via the Backup Applications Manager may fail with the error:
    Unable to connect to the resource. The specified Azure AD application is missing required application permissions (Microsoft API: SharePoint, permissions: Sites.FullControl.All, User.Read.All)
    
  • In a Hybrid organization, all running activities may become stuck until a backup proxy is restarted.
  • The Internet Proxy settings in Veeam Backup for Microsoft 365 overwrites the pre-configured system bypass list.
  • Creating auxiliary backup applications for an organization belonging to the China region fails with the error:
    Failed to get Microsoft Graph resource ID
    
  • Installing a certificate from the Certificate Store may complete with the error:
    Failed to import certificate (%name%): Key not valid for use in specified state
    
  • A Repository database’s owned space may become miscalculated and logged incorrectly.
  • The Storage Consumption report for an object storage repository displays zero consumption if an upgrade of this repository has previously failed.

Backup and Backup Copy

  • An Organization’s backup copy restore points are not displayed after changing the organization type to Hybrid.
  • A Backup job targeted to an object storage repository fails with the following error after performing a repository synchronization:
    JetError -1605, JET_errKeyDuplicate, Illegal duplicate key
    
  • Copying the backup of a OneDrive account may fail with the error:
    The given key was not present in the dictionary
    
  • A group mailbox folder backup may become stuck in a loop and fail to exit.
  • Under certain conditions, mailbox backup may fail with the error:
    Folder is already added
    
  • A Backup job may mistakenly continue processing after failing to resolve the excluded objects list.
  • SharePoint items in a folder that have been deleted and restored in the production environment are mistakenly ignored during incremental backup job runs.
  • SharePoint incremental backup to an object storage repository may fail with the following error if the previous backup job runs have been stopped:
    Cannot find object %path%
    

Restore

  • Restoring a SharePoint Online site to a SharePoint Subscription Edition site completes with the warning:
    Cannot complete this action. Please try again
    
  • Teams file restore fails with the following error if there are any files sharing the same name among the files being restored:
    An item with the same key has already been added
    
  • Browsing SharePoint, OneDrive, and Microsoft Teams backups from an object storage repository fails with the error:
    Cannot find object for get WebPreview request
    
    Note: This issue only occurs to backups created with Veeam Backup for Microsoft 365 v5 and earlier.
  • The order of item versions may be displayed incorrectly when exploring SharePoint, OneDrive, and Microsoft Teams backups when the backups are stored in an object storage repository configured with item-level retention and the repository retention period has been increased.
  • Browsing Teams posts retrieved from an archive tier repository may fail with the following error if some of the backed-up Teams posts have been deleted in the production environment:
    Buffer cannot be null
    
  • Under certain conditions, when browsing SharePoint, OneDrive, and Microsoft Teams backups retrieved from an archive tier repository, some items and item versions are not displayed.

PowerShell and REST APIs

  • The successful creation of a restore operator role with the Add-VBORbacRole cmdlet erroneously completes with the error:
    Specified cast is not valid
    
  • In v5 REST API endpoints for search requests, the “limit” and “offset” parameters are ignored.
  • The following get commands do not display the “groupSite” property in their responses:
    • (GET) /v6/Jobs/{jobid}/SelectedItems 
    • GET) /v6/Jobs/{jobid}/ExcludedItems 
  • Pagination is missing in the response to the following request:
    GET)/v6/RestoreSessions/{restoreSessionId}/organization/mailboxes/{mailboxId}/folders?parentId=<string>&name=<string>
    

P20220413 (6.0.0.379)

Improvements & Enhancements:

  • SharePoint restore session initiated from the Backup Job context menu now establishes a connection to the Backup Server faster.
  • Veeam Explorer for OneDrive now loads the list of protected OneDrive Accounts faster.
  • Veeam Explorer for SharePoint now explores backups stored in an Object Storage Repository faster.
  • Retrieve Backup Copy Wizard now populates the list of available SharePoint sites faster.
  • The request: (GET) /v6/BackupRepositories/{repositoryId}/SiteData now executes faster.

Resolved Issues:

Upgrade

  • Attempt to upgrade a Backup Repository that is extended to Object Storage may fail with the error:
    JetError -1504, JET_errNullInvalid, Null not valid
    
  • Under certain conditions, upgrading to Veeam Backup for Microsoft 365 6.0.0.367 may fail with the error:
    Failed to install the product. An error occurred. See log for details.
    
    This error may still occur, but the primary bug causing this has been resolved.
  • Attempting to upgrade to Veeam Backup for Microsoft 365 6.0.0.367 via the Upgrade wizard may fail with the error:
    Certificate verification failed: Certificate is not valid.
    

General

  • High CPU usage by the Veeam.Archiver.Service after upgrading to Veeam Backup for Microsoft 365 6.0.0.367.
  • When the Snapshot-Based Retention is set for far less than the time since the last backup, and there was only a restore point in the previous year, retention may mistakenly delete that old SharePoint and OneDrive backup point from a Jet-based repository when the next year comes.
    (This specific configuration scenario is exceedingly rare.)
  • The creation of the log folder for a data migration job fails if migrated object name includes special characters.
  • In rare situations, if a mailbox backed up to a Jet-based repository included some data with a modification timestamp in the future (a pretty rare issue for Exchange items), when the snapshot-level retention starts on 01/01/ХХХХ at 00:00 UTC, it may mistakenly delete Exchange data.
  • After upgrading to Veeam Backup for Microsoft 365 6.0.0.367, when the “Suppress notifications until the last retry” option is enabled, the email notifications only include information about the final backup job retry. Now the information from all retries is included.
  • Attempt to add or edit an organization belonging to the China region and using Modern App-Only Authentication fails with the error:
    Configure Azure AD application: Failed to get Microsoft Graph resource ID. Application is missing required permissions: Sites.Read.All
    

Backup and backup copy

  • In Hybrid organizations, the on-premises Exchange mailboxes are skipped from processing after upgrade to Veeam Backup for Microsoft 365 6.0.0.367.
  • SharePoint backup to an Object Storage Repository may fail with the error:
    Blob synchronization failed: Unspecified error.
    
  • Teams backup for organizations within the GCC High region fail with the error:
    Failed to process team: {%name%}. Invalid $select properties. The remote server returned an error: (400) Bad Request.
    
  • Backup Copy job transfers partially backed up SharePoint item’s attachments.
  • After Object Storage Repository synchronization, a Full backup is performed of Teams posts even though the posts already exist in a repository.

Restore

  • In Veeam Explorer for Microsoft Exchange, advanced search on Object Storage Repositories may fail with the error:
    Object reference not set to an instance of an object
    
  • Exploring older OneDrive backups from an Object Storage Repository may fail with the error:
    Object reference not set to an instance of an object
    
  • Opening an attachment from the SharePoint item history within backups stored in an archive tier repository fails with the error:
    Non-negative number required.
    
  • After completing a Teams restore that involved exporting Teams files, temporary folders with files are not cleaned from the default location.
  • Exploring SharePoint data retrieved from an archive tier repository may fail with the error:
    Operation timeout exceeded
    

REST APIs

  • In organizations using Modern App-Only Authentication, parsing of REST request parameters is incorrect when resource and equipment mailboxes have special characters in their display names.

PowerShell

Manual Updating

To manually update an existing Veeam Backup for Microsoft 365 6.0.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.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.