#1 Global Leader in Data Resilience

Release Information for Veeam Backup for Microsoft 365 6a

KB ID: 4344
Product: Veeam Backup for Microsoft 365 | 6.0
Published: 2022-08-11
Last Modified: 2023-01-11
mailbox
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.

Cumulative Patches are available for this version: Veeam Backup for Microsoft 365 6a Cumulative Patches

Requirements

Before upgrading to Veeam Backup for Microsoft 365 6.0, Please confirm that you are running one of the following versions of Veeam Backup for Microsoft 365:

  • 4.0 (build 4.0.0.1345)
    • 4a (builds 4.0.0.1553, 4.0.0.1580)
    • 4b (builds 4.0.0.2516, 4.0.0.2549)
    • 4c (builds 4.0.1.519, 4.0.1.531, 4.0.1.545, 4.0.1.612, 4.0.1.625)
  • 5.0 (builds 5.0.0.1061, 5.0.0.1063)
    • 5a (build 5.0.0.1070)
    • 5b (builds 5.0.1.179, 5.0.1.207, 5.0.1.225, 5.0.1.252)
    • 5c (builds 5.0.2.22, 5.0.2.42)
    • 5d (builds 5.0.3.1033, 5.0.3.1035, 5.0.3.1051, 5.0.3.1060, 5.0.3.1063)
  • 6.0 (builds 6.0.0.367, 6.0.0.379, 6.0.0.385, 6.0.0.400) 

You can check this under Help and Support > About in the Veeam Backup for Microsoft 365 console. To upgrade from earlier versions, please contact our Customer Support. After upgrading, your build number will change to 6.1.0.222.

Important Upgrade Information
  • Before you apply this update, be sure to review the ‘Upgrading Veeam Backup for Microsoft 365’ section of the Release Notes document.
  • For detailed information about this release, please refer to the Release Notes document.

What's New

  • Support for backing up Microsoft Teams  using the new Teams Export APIs
    With this support, Veeam Backup for Microsoft 365 becomes one of the first backup vendors to achieve Microsoft Teams Backup and Restore Certification.
  • Built-in User protection report
    The new report provides statistical information on the protected and unprotected user accounts.
  • Meeting the GDPR requirements with the ability to remove backup data from archive tier repositories.
    Backup copies can be removed from low-cost storage on-demand via PowerShell.
  • SharePoint personal sites data restore is now available for end users via the Restore Portal
  • Search by object name in the Retrieve Backup Copy wizard

Performance Enhancements

  • Up to 3x better compression of backup data stored in object storage repositories
  • Up to 4.7x faster SharePoint and OneDrive incremental backups
  • Up to 4x faster backup of SharePoint and OneDrive items with thousands of versions
  • Up to 3.3x faster backup copy
  • Up to 10x higher saving rate for SharePoint sites backed up to Jet-based repositories
  • Up to 3.3x lower egress costs during backup copy
  • Up to 2x faster restore of SharePoint sites with a large number of lists and items
  • Up to 15% faster resolving of Teams objects during a backup job
  • Up to 10x faster restoring data retrieved from an archive tier repository
  • Up to 15x faster export of an Exchange mailbox data retrieved from an archive tier repository

Resolved Issues

  • The amount of transferred data is missing in the backup copy job summary.
  • A Backup job targeted at a backup repository located on an SMB share is stuck in the ‘Operation pending…’ state if the repository is inaccessible.
  • Backed up users exceeding the license count in a rental license remain with the ‘New’ status in all subsequent periods.
  • The limit/offset parameters are ignored when used in search requests on v5 REST endpoints.
  • Login attempts via REST APIs using the /token endpoint are missing in the REST service logs.
  • Unable to configure the Restore Portal application in the China and the US Government regions.
  • Hyperlink reference syntax in REST API v6 is different from REST API v5.
  • A folder is not displayed in Veeam Explorer when browsing intermediate restore points if the location of this folder within a source SharePoint site, OneDrive, or Microsoft Teams files has been changed between the backup job runs.
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

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

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

Veeam Backup & Replication
Veeam Data Cloud for Microsoft 365
Veeam Data Cloud for Microsoft Entra ID
Veeam Data Cloud for Salesforce
Veeam Data Cloud for Microsoft Azure
Veeam Data Cloud Vault
Veeam Backup for Microsoft 365
Veeam Backup for Microsoft Entra ID
Veeam Backup for Salesforce
Veeam ONE
Veeam Service Provider Console
Veeam Agent for Microsoft Windows
Veeam Agent for Linux
Veeam Backup for Nutanix AHV
Veeam Backup for AWS
Veeam Backup for Microsoft Azure
Veeam Backup for Google Cloud
Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization
Veeam Management Pack for Microsoft System Center
Veeam Recovery Orchestrator
Veeam Agent for Mac
Veeam Agent for IBM AIX
Veeam Agent for Oracle Solaris
Veeam Cloud Connect
Veeam Kasten for Kubernetes
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
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.