Maintain control of your Microsoft 365 data
Post Reply
deniz.oezdemir
Novice
Posts: 5
Liked: never
Joined: Feb 20, 2026 8:11 pm
Contact:

Cannot find blob containing item data when exporting mailbox (Veeam Backup for Microsoft 365, S3 repository)

Post by deniz.oezdemir »

Hi everyone,

I am running Veeam Backup for Microsoft 365, and I created an S3-compatible, Item-Level repository with a 7-day retention period.

The backup job completes successfully, but when I try to export some mailboxes, I get the following error:

Code: Select all

Cannot find a blob containing item data:
Veeam/Backup365/test-incremental-backup/Organizations/<org-id>/Mailboxes/<mailbox-id>/ItemsData/492E870E08DE7AC9000005D7.0002
Observations:
  • Some mailbox exports work, but others fail with this error.
  • Older restore points also fail.
What would cause this error, and how can I fix it?

Any advice would be appreciated.

Thanks!
Mildur
Product Manager
Posts: 11554
Liked: 3247 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Cannot find blob containing item data when exporting mailbox (Veeam Backup for Microsoft 365, S3 repository)

Post by Mildur »

Hello,

We had a similar issue once, but it was fixed in v8.1.2.180.

Since this is a technical issue, please contact our Customer Support team — we can’t investigate these cases via a forum topic. Also, please provide a support case ID for this issue (as requested when you click New Topic). Without a case number, the topic will eventually be deleted by moderators.

Thank you,
Fabian
Product Management Analyst @ Veeam Software
t7MevELx0
Service Provider
Posts: 108
Liked: 19 times
Joined: Feb 06, 2024 6:55 pm
Contact:

Re: Cannot find blob containing item data when exporting mailbox (Veeam Backup for Microsoft 365, S3 repository)

Post by t7MevELx0 »

Hello Fabian,

Thank you for the response.

A support case has already been opened with Veeam for this issue. The case number is #07991655, and logs have been provided to the support team for investigation.

I posted here mainly to check whether anyone else in the community had encountered a similar issue or observed related behavior while the case is being reviewed by support.

Thanks again.
Post Reply

Who is online

Users browsing this forum: Google [Bot] and 22 guests