Release Information for Veeam Backup for Microsoft 365 7 Cumulative Patches

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

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

P20230512 (7.0.0.3604)

Resolved Issues

General

• Repository upgrades take additional time after upgrading to Veeam Backup for Microsoft 365 7.
• After the Veeam.Archiver.Proxy service process fails or is terminated manually, the Veeam Proxy service fails to restart automatically with the error:

   Write lock may not be acquired with read lock held. This pattern is prone to deadlocks.
  

• When applying retention on Object Storage Repositories, the Retention Job downloads an excessive amount of metadata.

Backup

• If there were zero new messages written to a Teams Channel on the last run, the Teams channel posts are requested again after a full sync has been initiated for a Teams backup job. 

• On incremental OneDrive and SharePoint backup job runs, new items may be skipped from a backup if, between backup job runs, a large number of items or folders were added/created in the source and then deleted in bulk.

  For more information, review: KB4447
• Team tabs added with the + button in the Teams app and linked to Word, Excel, PowerPoint, or Visio applications may be skipped from a backup.
  
  For more information, review: KB4448

 REST APIs

• The (GET) v7/Jobs request returns an incorrect value for the "lastRun" parameter.

• The (GET) v7/Jobs request doesn’t return the "lastBackup" parameter for backup jobs that have finished with warnings.

P20230421 (7.0.0.3007)

Resolved Issues

General

• Veeam Backup for Microsoft 365 7 writes successful authorization attempts to the Microsoft Windows event log every second, flooding the log with 4904/4905 security events.

Backup

• A SharePoint backup job may fail with the error:

  Failed to process site: %name% (%site URL%). The remote server returned an error: (429).
  

  For more information, review KB4442.
• Backup to object storage may fail on synchronizing metadata to the local cache with the error:

  JetError -1605 pattern cannot be determined
  

• Job session average ‘Read rate’ and ‘Write rate’ metrics are displayed incorrectly after the completion of a backup job targeted to an object storage repository.

• A Microsoft Teams backup job may fail on processing team tabs with the error:

  Object reference not set to an instance of an object.
  

  For more information, review: KB4201
• A SharePoint backup job that includes sites created by the Loop app fails with the following:

  The remote server returned an error: (401) Unauthorized. SharePoint Loop app is currently available in Preview, and sites that it creates are unsupported and will be skipped from processing.
  

  This cumulative patch does not add support for sites created by Loop; it allows Veeam Backup for Microsoft 365 jobs to skip such sites silently.
  For more information, review: KB4440
   

REST APIs

• The (GET) /v7/DataRetrievalSessions may fail with the error:

  Object reference not set to an instance of an object.
  

• The (GET) /v5/JobSessions request may fail with the error:

  Object reference not set to an instance of an object.
  

P20230302 (7.0.0.2914)

Resolved Issues

• 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
  

  These warnings were suppressed in Veeam Backup for Microsoft 365 v6a P20221215 (build 6.1.0.438). However, upon additional observation and testing after 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 v7 (build 7.0.0.2911), the suppression of the warning was rolled back.

To manually update an existing Veeam Backup for Microsoft 365 7.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 Backup for Microsoft 365 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.