#1 Global Leader in Data Resilience

Release Information for Veeam Backup for Microsoft 365 8 Cumulative Patches

KB ID: 4656
Product: Veeam Backup for Microsoft 365 | 8
Published: 2024-09-11
Last Modified: 2024-09-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.

Requirements

This Cumulative Patch can be used to:

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

After installing the Cumulative Patch, the Veeam Backup for Microsoft 365 build number will be 8.0.2.200 P20240910.

Release Information

Below are details about each of the Cumulative Patches that have been released for Veeam Backup for Microsoft 365 version 8 (8.0.2.x).

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

P20240910 (8.0.2.200)

Resolved Issues
  • Under certain circumstances related to retrospective issues of Veeam Backup for Microsoft 6 and 7, there could be an issue with an in-place upgrade when some repositories could not be upgraded. The following errors are related:
    • 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"
      

Manual Updating

To manually update an existing Veeam Backup for Microsoft 365 version 8 (8.0.2.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.
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 hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
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

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 hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
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.