#1 Global Leader in Data Resilience
#1 Global Leader in Data Resilience
TRY NOW
book meeting
BACK TO KB LIST

SharePoint and OneDrive Items May Not Be Displayed

KB ID: 4704
Product: Veeam Backup for Microsoft 365 | 8
Published: 2025-01-23
Last Modified: 2025-03-19
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.

Article Applicability
  • The solution provided in this article requires Veeam Backup for Microsoft 365 8.1 or higher.
  • The issue discussed in this article only occurs under particular circumstances. Review the Cause section closely.
  • This article is marked as related to Veeam Backup for Microsoft 365 8 because that is the version that caused the issue.

Challenge

When using Veeam Explorer for Microsoft SharePoint or Veeam Explorer for Microsoft OneDrive for Business with backups stored in a Jet-based repository, some items are not displayed. 

Cause

Retention applied to a Jet-based backup repository containing SharePoint and OneDrive data may mistakenly remove the parent folders from all historical backup databases, leaving their child items orphaned. The issue may only occur under the following conditions:

  • The initial backup was created in 2023 or earlier and continued in 2024.

    and
  • The Veeam Backup for Microsoft 365 deployment was at some point running version 7 or 7a (builds 7.x) and subsequently upgraded to one of the following version 8 builds:
    • 8.0.2.159
      (released 2024-09-03)
    • 8.0.2.200
      (released 2024-09-11)
    • 8.0.3.1044
      (released 2024-10-08)
    • 8.0.3.1073
      (released 2024-10-16)
    Note: If at any point during the Veeam Backup for Microsoft 365 deployment history it was running version 7 or 7a (builds 7.x) and subsequently upgraded to 8.0.2.159, 8.0.2.200, 8.0.3.1044, or 8.0.3.1073, it is affected, even if later upgraded to 8.0.4.29 or higher. The issue was resolved starting with build 8.0.4.29, so any upgrades directly from version 7 or 7a to build 8.0.4.29 or higher are unaffected. This means an affected deployment would have had to occur using a Veeam Backup for Microsoft 365 installer ISO downloaded between September 3, 2024, and October 29, 2024 (a 56-day window).

Solution

Version Requirement
The documented procedure requires Veeam Backup for Microsoft 365 8.1 or higher.
  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 get a list of impacted sites and OneDrive accounts in each of the impacted repositories:
$rep = Get-VBORepository -Name "<repo_name>"
Test-VBORepository -Repository $rep
  1. For each site and OneDrive listed in the output of the script from the Step 2:
    1. Identify the backup jobs associated with the impacted sites and OneDrives.
    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 issue in the latest and subsequent restore points for impacted objects that are still present within the production Microsoft 365 environment.

  1. To enable exploring of the individual items without parent folders on older restore points (created before the latest full backup), perform the following steps on the proxy associated with the impacted backup repository:
    1. Stop all backup jobs on the proxy and the Veeam Backup for Microsoft 365 Proxy Service service.
    2. On the machine where your backup proxy is installed, navigate to: C:\ProgramData\Veeam\Backup365\
    3. Make a copy of the Proxy.xml file, just in case changes need to be reverted or a misconfiguration occurs.
    4. Open the Proxy.xml file, and within the <Archiver> section, add the following line under the RepositoryConfig node: 
      <RepositoryConfig SPJetMissingParentItemsInRoot="true" />
      Example end of the Proxy.xml file: 
      ...
    <RepositoryConfig SPJetMissingParentItemsInRoot="true" />
  </Archiver>
</Veeam> 
    5. Save the updated Proxy.xml file.
    6. Start the Veeam Backup for Microsoft 365 Proxy Service service.

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

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

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.
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
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.