#1 Global Leader in Data Resilience

Backup or Backup Copy Job for SharePoint, OneDrive, or Teams Data Fails With: "Cannot find object"

KB ID: 4678
Product: Veeam Backup for Microsoft 365 | 8
Published: 2025-01-23
Last Modified: 2025-01-28
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.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.

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.

Challenge

After upgrading Veeam Backup for Microsoft 365 to v8 (builds 8.0.2.159 or 8.0.2.200), an incremental backup or a backup copy job protecting SharePoint, OneDrive, or Teams data fails with the error:

Cannot find object ...

Cause

In Object Storage Repositories, the metadata saved for the protected SharePoint lists and webs has been mistakenly overwritten.

This issue only occurs under the following very specific conditions:

  • An Object Storage Repository was created in Veeam Backup for Microsoft Office 365 while running version 4.x or 5.x.

    and
  • That Object Storage Repository contains backup data for SharePoint, OneDrive, or Teams files.

    and
  • That Veeam Backup for Microsoft 365 deployment was upgraded from any version 7 build to either 8.0.2.159Released 2024-09-03 or 8.0.2.200Released 2024-09-11.
    Note: Upgrades from version 7.x to build 8.0.3.1044Released 2024-10-08 and higher were not affected by this issue.

Solution

Version Requirement
The procedure below requires that Veeam Backup for Microsoft 365 version 8.1.0.305 or later be installed, and that all managed proxies and repositories are upgraded after the upgrade of Veeam Backup for Microsoft 365.
  1. Identify potentially impacted repositories according to the conditions in the Cause section.
  2. Open an Administrative PowerShell terminal and use the following command to produce a list of impacted sites:
    Replace <repo_name> with the name of the potentially impacted Object Storage Repository.
$rep = Get-VBORepository -Name "<repo_name>"
Test-VBORepository -Repository $rep
  1. For each site listed in the output of the script from Step 2:
    1. Identify the backup job associated with the site.
    2. Run a full synchronization cycle for each job containing impacted objects.
      Use the following PowerShell cmdlet:
      Replace JobName with the name of the affected job.
Get-VBOJob -Name "JobName" | Start-VBOJob -RunAsync -Full
During the full backup run, Veeam Backup for Microsoft 365 will automatically repair the missing metadata for impacted site lists that are still present within the production Microsoft 365 environment.
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.