Release Information for Veeam Backup for Microsoft 365 8 Cumulative Patches

Resolved Issues

• Under certain conditions, a proxy pool may stop all processing operations.
• SharePoint and OneDrive items may not be available for restore from a backup copy if, prior to the backup, those items were deleted and then subsequently restored to production. This issue applies only to data transferred by backup copy jobs created and initiated on v8.
• Retention may mistakenly apply to an object storage repository in an Out-of-Sync state. As a result, some restore points might be incorrectly deleted by retention.
• During the first full backup, a backup job processing Exchange objects and running on a proxy pool may fail with the error:

  Processing archive mailbox {%email address%} failed with error: Exception of type ‘System.OutOfMemoryException’ was thrown
  

Resolved Issues

• When the Restore Portal is configured to use a remote REST API server, login fails with the error:

  The server has rejected the client credentials.
  

• Under the following conditions, retention applied to a Jet-based repository may mistakenly remove the parent folders from backed-up SharePoint data.
  
  • The initial backup was created in 2023 or earlier and then continued in 2024.
  • The backups are stored in a JET-based backup repository using snapshot-based retention.
  • Veeam Backup for Microsoft 365 was upgraded to version 8.
• A backup copy job via an Azure archiver appliance fails with the error:

  SSH service is not available at %IP:port%.
  

• Under certain conditions, installing a patch on an existing v8 installation fails with the error:

  Installation failed. The process cannot access the file 'C:\Program Files\Veeam\Backup365\License\%filename%.lic' because it is being used by another process.
  

Resolved Issues

• Upgrade of remote components of Veeam Backup for Microsoft 365, including remote Consoles and REST API servers, fails with the error:

  NATS Server connection string is missing.
  

• Login to a Restore Portal configured on top of a remotely installed REST API server fails with the error:

  The remote certificate was rejected by the provided RemoteCertificateValidationCallback.
  

P20241004 (8.0.3.1044)

Resolved Issues

• Syncing a repository fails with the error:

  Unrecognized Guid Format
  

• If a SharePoint site was protected by Veeam Backup for Microsoft 365 (VB365) version 4, and a list inside that SharePoint site was changed through the SharePoint administrator center, the next backup run fails with the error:

  Cannot find object ...
  

• After upgrading to VB365 v8, backup jobs fail with the error:

  A poisoned bucket index is detected. Trying to add entities to an already occupied bucket.
  

• After upgrading to VB365 v8, the cmdlet Get-VBOUsageData stopped working.
• Backing up the Veeam Backup for Microsoft 365 server with Veeam Backup and Replication with Guest Processing (Application-Aware Processing) enabled fails with a VSS timeout.
• The job report delivers the wrong amount of warning objects in the objects processed statistics.
• Under certain circumstances, the indexing and upgrading of repositories is frozen.
• The restore portal stopped working when the organization was renamed in Microsoft 365.
• After upgrading to VB365 v8, the restore portal stops working if you are using a wildcard certificate.
• Syncing the cache for a VB365 v8 repository appears to stall or move slowly.
• Under certain circumstances, a job will not stop, even after a reboot of the services or server.
• If you are using a repository that already existed in VB365 v5 or earlier, under certain circumstances, during a repository upgrade, you can receive the Error:

  Jet column Properties of table xxxx......_Lists is not mapped
  

• Under certain circumstances, it can appear that restore points are missing after an upgrade to VB365 v8.
  The restore point data is still present, and it just needs to be reindexed. To manually trigger reindexing, use the Start-VBORepositoryIndexingSession cmdlet. For example:
  

  $repository = Get-VBORepository -Name "<repository_name>"
  Start-VBORepositoryIndexingSession -Repository $repository
  

• On rare occasions, the repository upgrade will fail with:

  Duplicated team info with different site Ids are found in the database
  

P20240910 (8.0.2.200)

Resolved Issues

• Under certain circumstances related to issues occurring in Veeam Backup for Microsoft 365 v6 and v7, issues may occur that prevent the in-place upgrade of some repositories after upgrading to Veeam Backup for Microsoft 365 v8. The following errors occur when the repository upgrade fails:

  • Repository database upgrade failed (repository ID: XXXXXXXX-XXXX-XXXX-XXXX-XXXX)
    Error: The given key 'XXXXXXXX-XXXX-XXXX-XXXX-XXXX' was not present in the dictionary.
    

  • Error: 23505: duplicate key value violates unique constraint "pk_account_personal_sites"
    

  • Error: 23505: duplicate key value violates unique constraint "pk_teams"
    

  • Error: 23505: duplicate key value violates unique constraint "pk_exchange_posts_batch_index"
    

  • Error: 23502: null value in column "organization_id" of relation "synchronization_infos" violates not-null constraint"