...
BugZero found this defect 796 days ago.
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.
Support for backing up Microsoft Teams chatsVeeam Backup for Microsoft 365 backs up Teams channel messages. For more information on the limitations of Teams chat backup, click here. using the new Teams Export APIsWith 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 reportThe 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
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
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.
Installing Veeam Backup for Microsoft 365 and Veeam Explorers Upgrading to Veeam Backup for Microsoft 365 6.0 Veeam Backup for Microsoft 365 6a: Release Notes Upgrade Requirements New Install Requirements